The Parameterized Safety Requirements Templates

Despite imposing strict recommendations to be considered during the specification of safety requirements, standards and regulations do not provide guidance to be used throughout the creation of these artifacts. In practice, each safety requirement specification has heterogeneous structures, usually based on the experience of the engineers involved in the specification process. Consequently, it becomes difficult to ensure that the standards' recommendations were considered, such as the existence of evidences that the requirements are properly traceable to other development artifacts such as architecture and failure propagation models. To address this challenge, we defined the Parameterized Safety Requirements Templates, which is a controlled natural language based approach to support engineers in elaborating the content description of safety requirements specifications, ensuring that elements of the architectural design and of the failure propagation models are explicitly considered throughout the textual description of the safety requirements, and are therefore properly traced. The Parameterized Safety Requirements Templates have been used in different domains such as automotive, avionics, and medical devices, and have proven to be effective in improving artifact traceability. In this paper, we present their usage in the context of an industrial Automated External Defibrillator system.

[1]  Anne Marsden,et al.  International Organization for Standardization , 2014 .

[2]  David Garlan,et al.  Documenting software architectures: views and beyond , 2002, 25th International Conference on Software Engineering, 2003. Proceedings..

[3]  Alistair Mavin,et al.  Easy Approach to Requirements Syntax (EARS) , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[4]  Daniel Jackson,et al.  Lightweight Formal Methods , 2001, FME.

[5]  Mario Trapp,et al.  Component-Based Abstraction in Fault Tree Analysis , 2009, SAFECOMP.

[6]  Alistair Mavin,et al.  Big Ears (The Return of "Easy Approach to Requirements Engineering") , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[7]  Tim Lüth,et al.  Experimental evaluation of a novel ISO 14971 risk management software for medical devices , 2016, 2016 IEEE/SICE International Symposium on System Integration (SII).

[8]  Alistair Mavin,et al.  EARS (Easy Approach to Requirements Syntax) , 2009 .

[9]  Donald J. Reifer,et al.  Software Failure Modes and Effects Analysis , 1979, IEEE Transactions on Reliability.

[10]  Antti Pakonen,et al.  Controlled natural language requirements in the design and analysis of safety critical I & C systems , 2014 .

[11]  Yi Zhang,et al.  Strategic Traceability for Safety-Critical Projects , 2013, IEEE Software.

[12]  Tobias Kuhn,et al.  A Survey and Classification of Controlled Natural Languages , 2014, CL.

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

[14]  Gethin Norman,et al.  Model checking for probabilistic timed automata , 2012, Formal Methods in System Design.

[15]  Hoyt Lougee,et al.  SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEMS AND EQUIPMENT CERTIFICATION , 2001 .

[16]  A. Berztiss,et al.  Requirements Engineering , 2002, J. Object Technol..

[17]  Cyrille Comar,et al.  Certifiably safe software-dependent systems: challenges and directions , 2014, FOSE.

[18]  Alistair Mavin Listen, Then Use EARS , 2012, IEEE Software.

[19]  kim. bjerge Model-Driven Development for Embedded Systems , 2008 .

[20]  Marta Z. Kwiatkowska,et al.  Symbolic model checking for probabilistic timed automata , 2007, Inf. Comput..