Development of High-Integrity Software Product Lines Using Model Transformation

Hutchesson, Stuart; McDermid, John

doi:10.1007/978-3-642-15651-9_29

Cited by 9 publications

(7 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…(Gaining acceptance for the use of aspect-oriented language would be problematic. ) We have previously shown how model transformation techniques can be used to instantiate components and their associated design artefacts from model-based design representations [2]. This approach introduced the concept of decision contracts, which publish the required decisions regarding the variability of a component as part of the component's contract.…”

Section: A Component Instantiation By Model Transformationmentioning

confidence: 99%

“…The model transformation process we described in [2] has been used successfully on a large avionics product line to develop components including variability. However it has been difficult to reduce the project-specific verification effort using this approach.…”

Section: Case Studiesmentioning

confidence: 99%

“…This is due to the problems described earlier; the transformations cannot be trusted to preserve properties from product-line to instantiated components. In our approach we use UML to model the software component architecture [13,14] and the SPARK source code is autogenerated using specially developed model-to model and model-to-text transformations [2]. The transformation of the parts of the design that are not compliant to the UML metamodel is performed using a simple text pre-processor.…”

Section: Case Studiesmentioning

confidence: 99%

See 2 more Smart Citations

Towards Cost-Effective High-Assurance Software Product Lines: The Need for Property-Preserving Transformations

Hutchesson

McDermid

2011

2011 15th International Software Product Line Conference

Self Cite

View full text Add to dashboard Cite

Generative programming and model transformation techniques are becoming widely used for the development of software components for product lines. The ability to develop components with identified common and variable parts, and rapidly instantiate product-specific versions is key to many software product line approaches. However if this approach is to be truly cost effective for high assurance applications, the instantiation process must be property-preserving; any verification evidence acquired on the product-line component must be demonstrably applicable to the instantiated component. In this paper we outline an approach that uses static analysis techniques and the SPARK language that can potentially demonstrate the correctness of model transformations.

show abstract

Section: A Component Instantiation By Model Transformationmentioning

confidence: 99%

Section: Case Studiesmentioning

confidence: 99%

Section: Case Studiesmentioning

confidence: 99%

See 1 more Smart Citation

Towards Cost-Effective High-Assurance Software Product Lines: The Need for Property-Preserving Transformations

Hutchesson

McDermid

2011

2011 15th International Software Product Line Conference

Self Cite

View full text Add to dashboard Cite

show abstract

“…The second line of research [45,46,47] focuses on the aerospace domain, and considers pure software assurance. The method relies on a model-to-model transformation from a UML class-model of a software system, to SPARK Ada programs [9].…”

Section: Main Related Workmentioning

confidence: 99%

Product-line assurance cases from contract-based design

Nešić

Nyberg

Gallina

2021

Journal of Systems and Software

View full text Add to dashboard Cite

Assurance cases are used to argue in a structured, and evidence-supported way, that a property such as safety or security is satisfied by a system. In some domains however, instead of single systems, product lines with many system-variants are engineered, to satisfy the needs of different customers. In such context, singlesystem methods for assurance-case creation suffer from scalability issues because the underlying assumption is that the evidence and arguments can be created per system variant. This paper presents a novel method for product-line assurance-case creation where all the arguments and the evidence are created without analyzing each system variant. Consequently, the effort to create an assurance case scales with the complexity of system variants, instead with their number. The method is based on a contract-based design framework for cyber-physical systems, which is extended to define the conditions under which all system variants satisfy a particular property. These conditions are used to define an assurance-case pattern, which can be instantiated for arbitrary product lines. Moreover, the defined pat-PRODUCT-LINE ASSURANCE CASES tern is modular to enable step-wise assurance-case creation. Finally, an exploratory case study is performed on a real product-line from the heavy-vehicle manufacturer Scania to evaluate the applicability of the presented method.

show abstract

“…It is possible to develop products that are "robust" to accommodate a reasonable level of uncertainty. Rolls-Royce has used Product Line principles [7] to develop "configurable" functions. Configurable here means that one can easily change the behaviour of a function through the use of a switch or data change, without having to re-code the logic.…”

Section: B Mitigating the Uncertaintymentioning

confidence: 99%

Managing requirements uncertainty in engine control systems development

Nolan

Abrahão

Clements

et al. 2011

2011 IEEE 19th International Requirements Engineering Conference

View full text Add to dashboard Cite

In the development of complex systems the requirements for the system will almost always remain uncertain late into the software development. In gas turbine engine control systems at Rolls-Royce, typically 50% of requirements will change between Critical Design Review and Entry into Service. Ignoring or not planning for requirements uncertainty will cause scrap and rework that will manifest later in the project. This paper evaluates the impact of not managing these uncertainties and describes how Rolls-Royce uses Requirements Uncertainty Analysis to reduce this impact. The paper summarises the findings from an extensive Six Sigma study into requirements uncertainty and provides an overview of the technique now used to identify and monitor uncertainty through a project life. The return on investment of this technique has been between 100:1 and 500:1.

show abstract

Development of High-Integrity Software Product Lines Using Model Transformation

Cited by 9 publications

References 6 publications

Towards Cost-Effective High-Assurance Software Product Lines: The Need for Property-Preserving Transformations

Towards Cost-Effective High-Assurance Software Product Lines: The Need for Property-Preserving Transformations

Product-line assurance cases from contract-based design

Managing requirements uncertainty in engine control systems development

Contact Info

Product

Resources

About