Process for software requirements safety analysis

Ramin Mojdehbakhsh, Satish Subramanian, Ramakrishna Vishnuvajjala, Wei Tek Tsai, Lynn Elliott

Research output: Chapter in Book/Report/Conference proceedingConference contribution

9 Scopus citations


In this paper we introduce a detailed process for software requirements safety analysis. The approach for identification of safety faults in this process is based on fault tree analysis. This process consists of four main steps, 1) software requirements fault tree generation, 2) software requirements fault tree verification and validation, 3) software safety requirements generation and safety fault mitigation, and 4) software requirements safety verification and validation. We have defined a set of rules that can automatically generate the software requirements fault tree given the software requirements specified in Statemate, and the software fault tree top events identified in the system safety analysis. Statemate CASE tool is used in this process for specification of software requirements, and execution and analysis of the software requirements to verify and validate safety. Essential tree analysis is introduced as a method for dependency analysis of the software fault tree top event. The outcome of essential tree analysis is captured in an essential tree which we introduce as a graphical representation of the dependencies and their interrelations.

Original languageEnglish (US)
Title of host publicationProceedings of the International Symposium on Software Reliability Engineering, ISSRE
Number of pages10
StatePublished - 1994
Externally publishedYes
EventProceedings of the 4th International Symposium on Software Reliability Engineering - Monterey, CA, USA
Duration: Nov 6 1994Nov 9 1994


OtherProceedings of the 4th International Symposium on Software Reliability Engineering
CityMonterey, CA, USA

ASJC Scopus subject areas

  • Software


Dive into the research topics of 'Process for software requirements safety analysis'. Together they form a unique fingerprint.

Cite this