Reasoning about Safety during Software Architecture Design

Architects use a variety of techniques to evaluate designs to determine the degree to which a product produced from the architecture would possess the desired levels of specific quality attributes. Reasoning frameworks are used to guide architecture definition by predicting the extent to which a software architecture satisfies its quality requirements. There has been much research about such direct runtime attributes as performance and modifiability but much less work has been done concerning such indirect attributes as safety. We present a framework for reasoning about safety that is based on the observation that safety hazards sometimes lead to accidents when certain quality requirements of the system are not satisfied. This naturally leads to the use of reasoning frameworks for these other qualities as a means to indirectly reason about safety. We present our technique that utilizes standard safety engineering activities and a risk-based qualitative reasoning approach to make a judgment on the satisfaction of safety requirements by the architecture.

[1]  M. Meek,et al.  IT risk management , 2014 .

[2]  J. A. McDermid,et al.  Towards integrated safety analysis and design , 1994, SIAP.

[3]  John D. McGregor,et al.  Security in the Context of Dependability , 2007 .

[4]  Ivar Jacobson,et al.  Object Design: Roles, Responsibilities, and Collaborations , 2002 .

[5]  Robyn R. Lutz Targeting safety-related errors during software requirements analysis , 1993, SIGSOFT '93.

[6]  Tim Kelly,et al.  Functional hazard analysis for highly integrated aerospace systems , 1998 .

[7]  Clifton A. Ericson,et al.  Hazard Analysis Techniques for System Safety , 2005 .

[8]  Peter Neumann,et al.  Safeware: System Safety and Computers , 1995, SOEN.

[9]  Linda Rosenberg NASA Software Safety Standard , 1997 .

[10]  Birte Twisselmann Five Past Midnight in Bhopal , 2002, BMJ : British Medical Journal.

[11]  Leonard J. Bass,et al.  Scenario-Based Analysis of Software Architecture , 1996, IEEE Softw..

[12]  John D. McGregor,et al.  Debugging support for security properties of software architectures , 2009, CSIIRW '09.

[13]  Tim Kelly,et al.  Safety tactics for software architecture design , 2004, Proceedings of the 28th Annual International Computer Software and Applications Conference, 2004. COMPSAC 2004..

[14]  Peter Liggesmeyer,et al.  A New Component Concept for Fault Trees , 2003, SCS.

[15]  Lars Grunske,et al.  Early quality prediction of component-based systems - A generic framework , 2007, J. Syst. Softw..

[16]  Nicolas Dulac,et al.  Incorporating Safety in Early System Architecture Trade Studies , 2005 .

[17]  Nancy G. Leveson,et al.  Incorporating Safety Risk in Early System Architecture Trade Studies , 2009 .