Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Software product-line engineering: a family-based software development process
Software product-line engineering: a family-based software development process
Software product lines: practices and patterns
Software product lines: practices and patterns
Architectural Considerations in the Certification of Modular Systems
SAFECOMP '02 Proceedings of the 21st International Conference on Computer Safety, Reliability and Security
Fault Contribution Trees for Product Families
ISSRE '02 Proceedings of the 13th International Symposium on Software Reliability Engineering
Bi-directional safety analysis of product lines
Journal of Systems and Software
PLFaultCAT: A Product-Line Software Fault Tree Analysis Tool
Automated Software Engineering
DECIMAL and PLFaultCAT: From Product-Line Requirements to Product-Line Member Software Fault Trees
ICSE COMPANION '07 Companion to the proceedings of the 29th International Conference on Software Engineering
Safety analysis of software product lines using state-based modeling
Journal of Systems and Software
Software fault tree analysis for product lines
HASE'04 Proceedings of the Eighth IEEE international conference on High assurance systems engineering
Adapting a software product line engineering process for certifying safety critical embedded systems
SAFECOMP'12 Proceedings of the 31st international conference on Computer Safety, Reliability, and Security
Hi-index | 0.00 |
Companies are increasingly adopting a product-line approach to the development of safety-critical systems. A product line offers large-scale reuse by exploiting common features and assets shared by systems within a specific domain. In this paper, we discuss the challenges of justifying the safety of architectural configurations and variation when developing product-line safety cases. We then address these challenges by defining an approach to developing product-line safety cases using the patterns and modular extensions of the Goal Structuring Notation (GSN). In this approach, we use the GSN patterns extension for explicitly capturing safety case variations and tracing these variations to their extrinsic source in the architectural model. Further, we use the GSN modular extension to organise the safety case into core and variable argument modules which are loosely coupled by means of argument contracts. We demonstrate this approach in a case study based on a product line of aero-engine control systems.