Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
Generative programming: methods, tools, and applications
Generative programming: methods, tools, and applications
Breaking Through the V and V Bottleneck
Proceedings of the Second International Eurospace - Ada-Europe Symposium on Ada in Europe
On the Importance of Product Line Scope
PFE '01 Revised Papers from the 4th International Workshop on Software Product-Family Engineering
High Integrity Software: The SPARK Approach to Safety and Security
High Integrity Software: The SPARK Approach to Safety and Security
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Making embedded software reuse practical and safe
Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering
Software Product Line Engineering: Foundations, Principles and Techniques
Software Product Line Engineering: Foundations, Principles and Techniques
Feature-based survey of model transformation approaches
IBM Systems Journal - Model-driven software development
BigLever software gears and the 3-tiered SPL methodology
Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companion
Challenges of Establishing a Software Product Line for an Aerospace Engine Monitoring System
SPLC '07 Proceedings of the 11th International Software Product Line Conference
Product Line Implementation using Aspect-Oriented and Model-Driven Software Development
SPLC '07 Proceedings of the 11th International Software Product Line Conference
Using domain specific languages for product line engineering
Proceedings of the 13th International Software Product Line Conference
Development of high-integrity software product lines using model transformation
SAFECOMP'10 Proceedings of the 29th international conference on Computer safety, reliability, and security
SPLC '11 Proceedings of the 2011 15th International Software Product Line Conference
Hi-index | 0.00 |
Context: The paper addresses the use of a Software Product Line approach in the context of developing software for a high-integrity, regulated domain such as civil aerospace. The success of a Software Product Line approach must be judged on whether useful products can be developed more effectively (lower cost, reduced schedule) than with traditional single-system approaches. When developing products for regulated domains, the usefulness of the product is critically dependent on the ability of the development process to provide approval evidence for scrutiny by the regulating authority. Objective: The objective of the work described is to propose a framework for arguing that a product instantiated using a Software Product Line approach can be approved and used within a regulated domain, such that the development cost of that product would be less than if it had been developed in isolation. Method: The paper identifies and surveys the issues relating the adoption of Software Product Lines as currently understood (including related technologies such as feature modelling, component-based development and model transformation) when applied to high-integrity software development. We develop an argument framework using Goal Structuring Notation to structure the claims made and the evidence required to support the approval of an instantiated product in such domains. Any unsubstantiated claims or missing/sub-standard evidence is identified, and we propose potential approaches or pose research questions to help address this. Results: The paper provides an argument framework supporting the use of a Software Product Line approach within a high-integrity regulated domain. It shows how lifecycle evidence can be collected, managed and used to credibly support a regulatory approval process, and provides a detailed example showing how claims regarding model transformation may be supported. Any attempt to use a Software Product Line approach in a regulated domain will need to provide evidence to support their approach in accordance with the argument outlined in the paper. Conclusion: Product Line practices may complicate the generation of convincing evidence for approval of instantiated products, but it is possible to define a credible Trusted Product Line approach.