Generic safety requirements description templates for the embedded software

It is generally believed that the correct description of safety requirements is the key of the whole safety work. However, there is not safety standard that is abided by in the requirements description now and the natural language with which there is no difference between the safety description and the function description is widely used in industry. Currently, the parameterized safety requirements templates are applicable in European industry but based on English. In order to find out appropriate safety requirements description templates, this paper represents safety requirements description templates for the embedded software based on the UML modeling mechanism and the content of GJB 438B-2009. The steps about how to put forward the safety requirements templates are shown following: Firstly, the structural elements of the static structure and dynamic operation are respectively found out according to the modeling mechanism of UML; Secondly, the failure modes on structural elements are presented; Thirdly, the safety requirements are obtained by presenting safety strategies in the view of failure avoidance, failure detection, failure tolerance and alarm and so on; Finally, The safety requirements description templates which include safety requirements structural elements description templates and safety requirements sentence pattern description templates are proposed based on obtained structural elements, failure modes, safety trategies and the content of GJB 438B-2009. The proposed safety requirements description templates which give criterions in requirements description are beneficial to promote the understanding and communication between engineering technicians and improve embedded software safety level.

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

[2]  Fan Xiao-ya.  Theories and methods of modeling for embedded system , 2009 .

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

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

[5]  Elena Troubitsyna,et al.  Elicitation and Specification of Safety Requirements , 2008, Third International Conference on Systems (icons 2008).

[6]  Nancy G. Leveson,et al.  A systems-theoretic approach to safety in software-intensive systems , 2004, IEEE Transactions on Dependable and Secure Computing.

[7]  Mario Trapp,et al.  The Parameterized Safety Requirements Templates , 2015, 2015 IEEE/ACM 8th International Symposium on Software and Systems Traceability.

[8]  Liu Bin,et al.  Modeling and verification of software safety requirement based on ontology , 2012 .

[9]  Poong-Hyun Seong,et al.  SMV model-based safety analysis of software requirements , 2009, Reliab. Eng. Syst. Saf..

[10]  Jianwen Zhu,et al.  Specification and Design of Embedded Systems , 1998, Informationstechnik Tech. Inform..

[11]  Jian Xie,et al.  Research on safety analysis for airborne system based on extended functional model , 2015 .

[12]  Chen Zhe,et al.  Survey on Embedded Software Safety Analysis Standards, Methods and Tools for Airborne System , 2014 .

[13]  Tony Gorschek,et al.  Requirements engineering for safety-critical systems: A systematic literature review , 2016, Inf. Softw. Technol..

[14]  Stefaan Callens,et al.  Medical Device Software to meet 2007/47/EC life cycle requirements: Practical Workshop on the legal challenges concerning telemedicine , 2011 .

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

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

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

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

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

[20]  Junbeom Yoo,et al.  A safety-focused verification using software fault trees , 2012, Future Gener. Comput. Syst..

[21]  Jang-Soo Lee,et al.  A formal software requirements specification method for digital nuclear plant protection systems , 2005, J. Syst. Softw..