Towards the Co-evolution of Models, Code, and Assurance Cases: The CAID Framework

Model-based software development is rarely performed with models only, and not everything is generated from the model(s). Handcrafted source code, documentation, simulation, data, tests, and assurance cases are the obvious (but not the only) examples. These artifacts, just like models, are version controlled, but kept in various, disjoint repositories. As they are often dependent on each other, the challenge is to maintain and manage the consistent co-evolution of such artifacts in the context of an agile development process. Some of the artifacts are related to software assurance - the construction of logical arguments, called assurance cases, that demonstrate why the software (or system) is safe and performant - which need to be continuously revised and updated in a deadline-driven development process. The Continuous Assurance-Integrated Development tool framework has been constructed to address the challenge stated above. The framework integrates and links together various software engineering artifacts: models, source code, documents, assurance cases, etc. and provides dependency tracking and change management functions. The framework is based on an open server-database/client-adapter architecture, where various repositories can be interwoven. A prototype of the framework has been created that integrates git repositories, a model database, and assurance case documents. The prototype has been published under an open source license.

Authors

Institutions

Publication Details

Published
2024-09-22
DOI
https://doi.org/10.1145/3652620.3688342
Primary Topic
Safety Systems Engineering in Autonomy
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

Towards the Co-evolution of Models, Code, and Assurance Cases: The CAID Framework

Patrik Meijer, Mark Wutka, Gábor Karsai, Nag Mahadevan
Safety Systems Engineering in Autonomy
article

Towards the Co-evolution of Models, Code, and Assurance Cases: The CAID Framework

Patrik Meijer, Mark Wutka, Gábor Karsai, Nag Mahadevan
article en

Abstract

Model-based software development is rarely performed with models only, and not everything is generated from the model(s). Handcrafted source code, documentation, simulation, data, tests, and assurance cases are the obvious (but not the only) examples. These artifacts, just like models, are version controlled, but kept in various, disjoint repositories. As they are often dependent on each other, the challenge is to maintain and manage the consistent co-evolution of such artifacts in the context of an agile development process. Some of the artifacts are related to software assurance - the construction of logical arguments, called assurance cases, that demonstrate why the software (or system) is safe and performant - which need to be continuously revised and updated in a deadline-driven development process. The Continuous Assurance-Integrated Development tool framework has been constructed to address the challenge stated above. The framework integrates and links together various software engineering artifacts: models, source code, documents, assurance cases, etc. and provides dependency tracking and change management functions. The framework is based on an open server-database/client-adapter architecture, where various repositories can be interwoven. A prototype of the framework has been created that integrates git repositories, a model database, and assurance case documents. The prototype has been published under an open source license.

Vanderbilt University (US), Integrated Software (United States) (US)
Openalex Percentile: Top 77%
Safety Systems Engineering in Autonomy
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.