Eliciting additional safety requirements from use cases using SFTA

Use case based approaches for software requirement analysis have been used extensively in software development industry to capture functional and behavioral requirements. But use-case based techniques for requirement analysis has not been found to be much effective and supportive enough for capturing non-functional requirements such as safety requirements. To overcome this problem, a systematic approach for eliciting additional and or missing safety requirements from textual description of use cases by the manual application of a well known software safety analysis (SSA) technique named Software Fault Tree Analysis (SFTA) has been proposed and presented in this paper. SFTA has been derived and applied in software from a similar hardware safety analysis technique named Fault Tree Analysis (FTA). The technique presented in this paper operates with the assumption that textual description of the use cases is correct. The effectiveness of the proposed approach has been demonstrated via an application of SFTA on the use case model (UCM) for an Elevator Control application.

[1]  Bonnie E. Melharlt.  Software Fault Tree Analysis for a Requirements System Model , 1995 .

[2]  Anders P. Ravn,et al.  From Safety Analysis to Software Requirements , 1998, IEEE Trans. Software Eng..

[3]  Robyn R. Lutz,et al.  Requirements analysis using forward and backward search , 1997, Ann. Softw. Eng..

[4]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[5]  Zhou Hai,et al.  Software for fault tree analysis , 2001 .

[6]  B. E. Malhart.  Software fault tree analysis for a requirements system model , 1995, Proceedings of the 1995 International Symposium and Workshop on Systems Engineering of Computer-Based Systems.

[7]  Jan Torin,et al.  Hazard analysis in object oriented design of dependable systems , 2001, 2001 International Conference on Dependable Systems and Networks.

[8]  Janusz Górski,et al.  Deriving real-time requirements for software from safety analysis , 1996, Proceedings of the Eighth Euromicro Workshop on Real-Time Systems.

[9]  Shinji Kusumoto,et al.  Derivation of safety requirements for safety analysis of object-oriented design documents , 1997, Proceedings Twenty-First Annual International Computer Software and Applications Conference (COMPSAC'97).

[10]  Vasant Honavar,et al.  A Software Fault Tree Approach to Requirements Analysis of an Intrusion Detection System , 2002, Requirements Engineering.

[11]  Tim Kelly,et al.  Deriving safety requirements using scenarios , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[12]  Ephraim Balz.  USE CASE-BASED FAULT TREE ANALYSIS OF SAFETY-RELATED EMBEDDED SYSTEMS , 2005 .

[13]  Hassan Gomaa,et al.  Designing concurrent, distributed, and real-time applications with UML , 2000, ICSE.

[14]  Wei-Tek Tsai,et al.  A process for software requirements safety analysis , 1994, Proceedings of 1994 IEEE International Symposium on Software Reliability Engineering.