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

8 Citations (Scopus)

Abstract

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
PublisherIEEE
Pages45-54
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

Other

OtherProceedings of the 4th International Symposium on Software Reliability Engineering
CityMonterey, CA, USA
Period11/6/9411/9/94

Fingerprint

Fault tree analysis
Security systems
Specifications

ASJC Scopus subject areas

  • Software

Cite this

Mojdehbakhsh, R., Subramanian, S., Vishnuvajjala, R., Tsai, W. T., & Elliott, L. (1994). Process for software requirements safety analysis. In Proceedings of the International Symposium on Software Reliability Engineering, ISSRE (pp. 45-54). IEEE.

Process for software requirements safety analysis. / Mojdehbakhsh, Ramin; Subramanian, Satish; Vishnuvajjala, Ramakrishna; Tsai, Wei Tek; Elliott, Lynn.

Proceedings of the International Symposium on Software Reliability Engineering, ISSRE. IEEE, 1994. p. 45-54.

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

Mojdehbakhsh, R, Subramanian, S, Vishnuvajjala, R, Tsai, WT & Elliott, L 1994, Process for software requirements safety analysis. in Proceedings of the International Symposium on Software Reliability Engineering, ISSRE. IEEE, pp. 45-54, Proceedings of the 4th International Symposium on Software Reliability Engineering, Monterey, CA, USA, 11/6/94.
Mojdehbakhsh R, Subramanian S, Vishnuvajjala R, Tsai WT, Elliott L. Process for software requirements safety analysis. In Proceedings of the International Symposium on Software Reliability Engineering, ISSRE. IEEE. 1994. p. 45-54
Mojdehbakhsh, Ramin ; Subramanian, Satish ; Vishnuvajjala, Ramakrishna ; Tsai, Wei Tek ; Elliott, Lynn. / Process for software requirements safety analysis. Proceedings of the International Symposium on Software Reliability Engineering, ISSRE. IEEE, 1994. pp. 45-54
@inproceedings{d177fd729fbf45e78080e22007577715,
title = "Process for software requirements safety analysis",
abstract = "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.",
author = "Ramin Mojdehbakhsh and Satish Subramanian and Ramakrishna Vishnuvajjala and Tsai, {Wei Tek} and Lynn Elliott",
year = "1994",
language = "English (US)",
pages = "45--54",
booktitle = "Proceedings of the International Symposium on Software Reliability Engineering, ISSRE",
publisher = "IEEE",

}

TY - GEN

T1 - Process for software requirements safety analysis

AU - Mojdehbakhsh, Ramin

AU - Subramanian, Satish

AU - Vishnuvajjala, Ramakrishna

AU - Tsai, Wei Tek

AU - Elliott, Lynn

PY - 1994

Y1 - 1994

N2 - 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.

AB - 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.

UR - http://www.scopus.com/inward/record.url?scp=0028695124&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0028695124&partnerID=8YFLogxK

M3 - Conference contribution

AN - SCOPUS:0028695124

SP - 45

EP - 54

BT - Proceedings of the International Symposium on Software Reliability Engineering, ISSRE

PB - IEEE

ER -