Constructing product-line safety cases from contract-based specifications

Nešić, Damir; Nyberg, Mattias; Gallina, Barbara

doi:10.1145/3297280.3297479

Cited by 8 publications

(5 citation statements)

References 40 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The present paper extends the work in [65] by considering a more expressive contract-based design-framework in order to support a greater array of engineering scenarios. Consequently, the product-line extension of the contract-based framework is also refined.…”

Section: Paper Contributionmentioning

confidence: 85%

“…Consequently, the product-line extension of the contract-based framework is also refined. Furthermore, and unlike [65], an exploratory case study is performed on a part of a real product-line from the heavy vehicle manufacturer Scania, to evaluate the applicability of the extended contract-based framework. Finally, the assurance-case pattern is refined in order to match the refined extension of the contract-based framework, and the pattern is redefined to yield a modular assurance case.…”

Section: Paper Contributionmentioning

confidence: 99%

See 1 more Smart Citation

Product-line assurance cases from contract-based design

Nešić

Nyberg

Gallina

2021

Journal of Systems and Software

Self Cite

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

Section: Paper Contributionmentioning

confidence: 85%

Section: Paper Contributionmentioning

confidence: 99%

Product-line assurance cases from contract-based design

Nešić

Nyberg

Gallina

2021

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

show abstract

“…Besides, to optimize the level of reuse during the development of highly configurable automotive systems, the approach of product line engineering is adopted [53]. By integrating contract-based specifications within the product line, the safety assessment for safetycritical systems may be achieved in a more efficient way by increasing the reuse of components, as shown by Nesic in [54]. An overview of our suggested modeling environment is represented in Figure 8.…”

Section: A Backend 1) Modeling Environmentmentioning

confidence: 99%

Lifecycle Management of Automotive Safety-Critical Over the Air Updates: A Systems Approach

et al. 2022

View full text Add to dashboard Cite

With the increasing importance of Over The Air (OTA) updates in the automotive field, maintaining safety standards becomes more challenging as frequent incremental changes of embedded software are regularly integrated into a wide range of vehicle variants. This necessitates new processes and methodologies with a holistic view on the backend, where the updates are developed and released, and the frontend (vehicle), to which the updates are deployed. In this paper, we introduce an approach, including a process and a methodology, for continuous contract-based design, validation and deployment of modular updates for variant-rich automotive systems. The approach considers the vehicle as part of its connected environment enclosing a backend and concentrates on safety-critical applications. In addition, we present the UPDateable Automotive Test dEmonstratoR (UPDATER), which is a mock-up for modern Electric/Electronic architectures including a backend and a frontend part. It serves as a prototype for developing, deploying and monitoring automotive OTA updates. In a case study based on UPDATER, we apply the approach to three exemplary updates of a variable Advanced Driver Assistance System (ADAS). We show how the updates development and management may be achieved in an efficient and agile way.

show abstract

“…Therefore, typical reusable assets for this domain are software components, models and SIL (software‐in‐the‐loop) code used by MATLAB/Simulink tools for simulation and verification tasks and building control algorithms (eg,). Atypical but of increasing relevance is also the reuse of arguments to speed up compliance with ISO 26262, while arguing about safety in the context of safety‐critical product lines (eg,).…”

Section: Application Domainsmentioning

confidence: 99%

Opportunities for software reuse in an uncertain world: From past to emerging trends

Capilla

Gallina

Cetina

et al. 2019

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

Much has been investigated about software reuse since the software crisis. The development of software reuse methods, implementation techniques, and cost models has resulted in a significant amount of research over years. Nevertheless, the increasing adoption of reuse techniques, many of them subsumed under higher level software engineering processes, and advanced programming techniques that ease the way to reuse software assets, have hidden somehow in the recent years new research trends on the practice of reuse and caused the disappearance of several reuse conferences. Also, new forms of reuse like open data and feature models have brought new opportunities for reuse beyond the traditional software components.From past to present, we summarize in this research the recent history of software reuse, and we report new research areas and forms of reuse according to current needs in industry and application domains, as well as promising research trends for the upcoming years.

show abstract

Constructing product-line safety cases from contract-based specifications

Cited by 8 publications

References 40 publications

Product-line assurance cases from contract-based design

Product-line assurance cases from contract-based design

Lifecycle Management of Automotive Safety-Critical Over the Air Updates: A Systems Approach

Opportunities for software reuse in an uncertain world: From past to emerging trends

Contact Info

Product

Resources

About