D. Raheja, Software system failure mode and effects analysis (SSFMEA) -- A tool for reliability growth, in: Proceedings of the Int'l Symp. on Reliability and Maintainability (ISRM'90), Tokyo, Japan (1990) pp. 271--277.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Figure 3. An Example of a Generic Process Taxonomy Annotated with Exceptions. Generic process templates are annotated, in our approach, with the ways in which they can fail, i.e. with their characteristic exception types (see Figure 3 above) which can be uncovered using failure mode analysis (Raheja 1990). Each process template in a taxonomy inherits all characteristic exceptions of its parent (generalization) and may contain additional exceptions which are specific to it. distribute shared design resources (by request) allocate design tasks (via subcontracting) consolidate sub designs ....

....Visser 1995) model based fault diagnosis (deKleer and Williams 1986; Krishnamurthi and Jr. 1989; Birnbaum, Collins et al. 1990; Friedrich, Gottlob et al. 1990) planning (Sussman 1973; Goldstein 1975; Broverman and Croft 1987; Birnbaum, Collins et al. 1990) and failure mode analysis research (Raheja 1990). Most workflow research has focused on languages for expressing correctness preserving transforms on workflow models, providing no guidance however concerning which transforms to use for a given situation. There has been some manufacturing and workflow research on providing guidance for how to ....

[Article contains additional citation context not shown here]

Raheja, D. (1990). Software system failure mode and effects analysis (SSFMEA)-a tool for reliability growth. Proceedings of the International Symposium on Reliability and Maintainability (ISRM-90), Tokyo, Japan, Union of Japanese Sci. & Eng; Tokyo, Japan.

....and so on. Exception Identification: Existing exception identification techniques, except for specialized circumstances such as deadlock properties in distributed protocols [46] 47] have left the identification of possible exception modes up to the software designers themselves [48] [49]. Our work differs in that it includes an approach for collecting abstract exception information that is applicable to a range of MAS coordination mechanisms, thereby offering the potential of greatly reducing the effort involved in exception analysis. Our approach can also be viewed, we believe, ....

Raheja, D. Software system failure mode and effects analysis (SSFMEA)-a tool for reliability growth. in Proceedings of the International Symposium on Reliability and Maintainability (ISRM-90). 1990. Tokyo, Japan: Union of Japanese Sci. & Eng; Tokyo, Japan.

....(team 3) perform design (team 2) Figure 2. An Example Ideal Process Model. 5 Process element templates are annotated with the ways in which they can fail, i.e. with their characteristic exception types. Failure modes for a given process template can be uncovered using failure mode analysis [11]. Each process element in a taxonomy inherits all characteristic failure modes of its parent (generalization) and may contain additional failure modes which are specific to it. Given an ideal process model, to identify failure modes we need only identify the generic process element templates ....

D. Raheja. Software system failure mode and effects analysis (SSFMEA)-a tool for reliability growth. Proceedings of the Int'l Symp. on Reliability and Maintainability (ISRM'90), Tokyo, Japan (1990) 271-277.

....Fig. 3. An Example of a Generic Activity Taxonomy Annotated with Failure Modes. Process element templates are annotated with the ways in which they can fail, i.e. with their characteristic exception types. Failure modes for a given process template can be uncovered using failure mode analysis [24]. Each process element in a taxonomy inherits all characteristic failure modes of its parent (generalization) and may contain additional failure modes which are specific to it. distribute shared design resources (by request) allocate design tasks (manager) consolidate sub designs build ....

.... we believe, a substantive and novel contribution to previous efforts on exception handling, which have been pursued in the context of workflow [1, 9, 13, 18, 22, 25] manufacturing control [14, 23, 26] model based fault diagnosis [3, 7, 19] planning [3, 4] and failure mode analysis research [24]. Most workflow research has focused on languages for expressing correctness preserving transforms on workflow models, providing no guidance however concerning which transforms to use for a given situation. There has been some manufacturing and workflow research on providing guidance for how to ....

[Article contains additional citation context not shown here]

D. Raheja. Software system failure mode and effects analysis (SSFMEA)-a tool for reliability growth. Proceedings of the Int'l Symp. on Reliability and Maintainability (ISRM'90), Tokyo, Japan, pp. 271-77, 1990.

....of the architectural model against a repository of generic architectural patterns, resource types and constraint types annotated with the ways in which they can fail, i.e. with their characteristic exception types. Failure modes for a given element can be uncovered using failure mode analysis [12]. In the case of software architecture, more specialized analysis techniques can uncover certain possible failures, such as deadlock and race conditions (for example [1,5,7] While systems can fail in many different ways, such failures have a relatively limited number of different manifestations, ....

D. Raheja. Software system failure mode and effects analysis (SSFMEA)-a tool for reliability growth. Proc. of Int'l Symp. On Reliability and Maintainability (ISRM'90), Tokyo, Japan, June 1990, pp. 271-277.

....design (team 3) perform design (team 2) Figure 2. An Example Ideal Process Model. Process element templates are annotated with the ways in which they can fail, i.e. with their characteristic exception types. Failure modes for a given process template can be uncovered using failure mode analysis [11]. Each process element in a taxonomy inherits all characteristic failure modes of its parent (generalization) and may contain additional failure modes which are specific to it. Given an ideal process model, to identify failure modes we need only identify the generic process element templates ....

D. Raheja. Software system failure mode and effects analysis (SSFMEA)-a tool for reliability growth. Proceedings of the Int'l Symp. on Reliability and Maintainability (ISRM'90), Tokyo, Japan, June 1990, pp. 271-277.

....provide tabular details of failure modes and probabilities to systems integrators) to unknown systemlevel effects; it is essentially a tabular, labour intensive process with a highly experiential focus. FMEA has had relatively few successful applications to software to date. For example, Raheja [29] has proposed a technique which is clearly a derivation of classical FMEA, but does not appear to capture the essence of a software component in a well defined way. We believe that our FTA structures (particularly the clich identification) will let us provide data which will integrate well ....

Raheja, D., "Software System Failure Mode And Effects Analysis (SSFMEA) --- A Tool For Reliability Growth," Proceedings of the International Symposium on Reliability and Maintainability (1990) pp.IX-1 - IX-7.

....the external effects of a piece of software misbehaving, or the interactions between software components in complex systems we see that there is in fact scope for FMECA to be performed on software. The traditionalist attitude has to date rather limited work on FMECA of software, although Raheja [Raheja90] has attempted to exploit it as an aid to the development of high integrity systems with partial success. It is our belief that the failings to date of attempts to apply FMECA to software are caused by the lack of an effective procedure for carrying out the actual analysis: it is easy to devise an ....

Raheja, Dev, "Software System Failure Mode And Effects Analysis (SSFMEA) --- A Tool For Reliability Growth," Proc. International Symposium on Reliability and Maintainability, Tokyo (1990), pp.IX-1 - IX-7.

No context found.

D. Raheja, Software system failure mode and effects analysis (SSFMEA) -- A tool for reliability growth, in: Proceedings of the Int'l Symp. on Reliability and Maintainability (ISRM'90), Tokyo, Japan (1990) pp. 271--277.

No context found.

Rah90. Raheja, Dev, "Software System Failure Mode And Effects Analysis (SSFMEA) --- A Tool For Reliability Growth", Proceedings of the International Symposium on Reliability and Maintainability, Tokyo, pp. IX-1 - IX-7 (1990).

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC