Enabling Cross-Domain Reuse of Tool Qualification Certification Artefacts

Gallina, Barbara; Kashiyarandi, Shaghayegh; Zugsbratl, Karlheinz; Geven, Arjan

doi:10.1007/978-3-319-10557-4_28

Cited by 15 publications

(10 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The second line of research has focused on the creation of assurancecase arguments by analyzing various types of artifacts. In the context of product lines, besides the approaches described in the introduction [38,41,18,45,46,47], most notable contributions come from the latter group [31,74,73,16,32,50].…”

Section: Argumentation Reusementioning

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

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: Argumentation Reusementioning

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

“…As defined by Gallina et al [6], a safety-oriented process line is a process line focusing on processes for engineering safety-critical systems/product lines. In the framework of safety critical systems engineering, a process line might be introduced at several levels: to model intra-domain processes [24] that slightly vary due to different safety integrity levels (e.g., ASIL A, ASIL B, etc in the automotive domain); to model crossdomain processes [25] that vary due to different safety integrity level types (e.g., ASIL, DAL-Design Assurance Level, in the automotive and avionics domains). Desired single processes can be derived from the process line by selecting and composing appropriate reusable process elements.…”

Section: A Safety-critical Product Linesmentioning

confidence: 99%

Towards Enabling Reuse in the Context of Safety-Critical Product Lines

Gallina¹

2015

2015 IEEE/ACM 5th International Workshop on Product Line Approaches in Software Engineering

Self Cite

View full text Add to dashboard Cite

In the context of safety-critical product lines, industries have to face an urgent challenge: reduction of time and cost for the creation of a safety case. A safety case is a contextualized structured argument constituted of process and product-based sub-arguments to show that a system is acceptably safe. Its creation is an extremely time-consuming and costly activity. To reduce time and cost, reuse capabilities are being investigated from different perspectives however currently no satisfying approach is available. In this paper, we propose a new methodological framework called Anti-Sisyphus. Anti-Sisyphus is aimed at enabling reuse by combining process lines, product lines and safety case lines. The systematization of what varies and what remains in common with respect to process as well as product elements in turns enables the systematization of what varies and remains in common in terms of process-based as well as productbased arguments within a safety case line. Anti-Sisyphus thus has the potential to enable a 3D reuse.

show abstract

“…The first line of research has focused on capturing safety case patterns that have been successfully used to argue for different properties [10,15] while the second line of research has focused on generating safety case arguments from various types of artifacts [14,26,37]. In the area of PLE, most notable contributions [14,18,19,21,26,36,37] come from the latter group.…”

Section: Related Workmentioning

confidence: 99%

“…As argued in Section 1, the present paper considers development and assurance of arbitrary PLs and consequently relies on CBS paradigm where the constructed assurance case argues for system level properties instead of only SEooC. The line of research in [18,19,21] introduces approaches for constructing safety case fragments that target particular requirements from various domain-specific safety standards. A notable aspect of these approaches is the attention to processes and their assurance with respect to standardized practices.…”

Section: Related Workmentioning

confidence: 99%

Constructing product-line safety cases from contract-based specifications

Nešić

Nyberg

Gallina

2019

Proceedings of the 34th ACM/SIGAPP Symposium on Applied Computing

Self Cite

View full text Add to dashboard Cite

Safety cases are used to argue that safety-critical systems satisfy the properties determined to mitigate the potential hazards in the systems deployment environment. Although primarily a manual task, safety cases have been successfully created for single systems. However, when systems with a high number of configurations are considered, typically developed as a Product Line (PL), considering each possible configuration and constructing sound and complete safety-case argumentation is challenging. This paper presents a novel and general approach for the construction of a safety case for an arbitrary PL that is based on Contract-Based Specification (CBS) of the PL. Starting from a general CBS framework, a PL extension of the CBS framework is presented and it is shown that the extension preserves the properties of the original framework. Then, given a CBS specification of a PL, a set of transformation rules for the construction of the safety case argumentation-structure is defined. Finally, the approach is exemplified on a simplified, but real, and currently produced system by Scania CV AB.

show abstract

Enabling Cross-Domain Reuse of Tool Qualification Certification Artefacts

Cited by 15 publications

References 9 publications

Product-line assurance cases from contract-based design

Product-line assurance cases from contract-based design

Towards Enabling Reuse in the Context of Safety-Critical Product Lines

Constructing product-line safety cases from contract-based specifications

Contact Info

Product

Resources

About