A case study using a protocol to derive safety functional requirements from Fault Tree Analysis
- 1 August 2014
- conference paper
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE) in 2014 IEEE 22nd International Requirements Engineering Conference (RE)
- p. 412-419
- https://doi.org/10.1109/re.2014.6912292
Abstract
State-of-the-art in Requirements Engineering offers many frameworks and techniques to enable requirements engineers in their work. However, for critical systems there are gaps in state-of-the-art, and these can result in dire consequences, potentially putting lives in danger and damage infrastructure and threaten the environment. A well known technique used to help requirements engineers to understand safety hazards situations in the context of safety-critical software is Fault Tree Analysis (FTA). This technique is a good one to decompose hazards identified in the system context into events that may put the system functionalities in risk. However, FTA does not offer a protocol of how to derive safety functional requirements from fault trees. In this paper we present a case study adopting a protocol to help requirements engineers to derive safety functional requirements from FTA. The proposed protocol was based on a study performed in a Brazilian company in the area of electronic medical devices. The development of prototype of a low cost insulin infusion pump, which is a critical system, offered the basis to propose and test a protocol to derive safety functional requirements from FTA. During the case study we collected evidences that help us to discuss if FTA is sufficient to guide software engineers to implement the corresponding control software and also if FTA offers enough information to help requirements engineers to derive safety functional requirements.Keywords
This publication has 16 references indexed in Scilit:
- Industry needs and research directions in requirements engineering for embedded systemsRequirements Engineering, 2011
- Independent validation of software safety requirements for systems of systemsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2010
- Engineering safety- and security-related requirements for software-intensive systemsPublished by Association for Computing Machinery (ACM) ,2010
- Trends in Embedded Software EngineeringIEEE Software, 2009
- Using obstacle analysis to identify contingency requirements on an unpiloted aerial vehicleRequirements Engineering, 2006
- A goal-oriented approach for safety requirements specificationPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2006
- Empirical analysis of safety-critical anomalies during operationsIEEE Transactions on Software Engineering, 2004
- Operational anomalies as a cause of safety-critical requirements evolutionJournal of Systems and Software, 2003
- Integrated safety analysis of requirements specificationsRequirements Engineering, 1997
- Safety assessment and the software requirements specificationReliability Engineering & System Safety, 1997