Name
Abstract | ||
|---|---|---|
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. |
Year | DOI | Venue |
|---|---|---|
2013 | 10.1016/j.infsof.2012.06.005 | Information & Software Technology |
Keywords | Field | DocType |
software product lines,potential approach,model transformation,argument framework,instantiated product,regulated domain,traditional single-system approach,trusted product lines,credible trusted product line,product line practice,software product line approach,spark | Product engineering,Domain analysis,Data mining,Domain engineering,Systems engineering,Software design description,Computer science,Software product line,Product design specification,Software development,New product development | Journal |
Volume | Issue | ISSN |
55 | 3 | 0950-5849 |
Citations | PageRank | References |
3 | 0.41 | 18 |
Authors | ||
2 | ||
Name | Order | Citations | PageRank |
|---|---|---|---|
| Stuart Hutchesson | 1 | 18 | 1.83 |
| John Mcdermid | 2 | 63 | 6.05 |