Towards Continuous Consistency Checking of DevOps Artefacts

Colantoni, Alessandro; Horváth, Benedek; Horváth, Ákos; Berardinelli, Luca; Wimmer, Manuel

doi:10.1109/models-c53483.2021.00069

Cited by 2 publications

(1 citation statement)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The storing can e.g., be handled directly by tools such as LieberLieber LemonTree, or the automated visualization of information from Git Artefacts is offered e.g., by Sonarqube 8 . Consistency between the versions of different models (Requirement 3) can also be ensured using Git, as e.g., shown by Colantoni et al (2021). In general, every push in Git indicates a new version of the repository contents.…”

Section: Requirement 3: Ensure Consistency Between the Versioning Of ...mentioning

confidence: 99%

Git‐based Model Management for Quality Monitoring of Systems Engineering Models

Lehner,

Vamberszky,

Wieland

et al. 2022

INCOSE International Symp

View full text Add to dashboard Cite

The management of Systems Engineering Models is becoming a crucial requirement when developing complex systems. Particularly with the advance of agile MBSE, Systems Engineering Models evolve constantly. Therefore, for managing Systems Engineering Models, this evolution has to be supported, including concurrent work on one model. Therefore, Git‐based solutions are emerging nowadays also in the Systems Engineering domain. Dedicated model differencing and conflict resolution approaches are provided by extensions of the base support of Git, which is mostly oriented to textual artefacts. However, the monitoring and management of the System Engineering Models hosted in Git repositories is still an open challenge. In this paper, we present a Git‐based model management approach for monitoring the quality of Systems Engineering Models. We outline the architecture of the approach as well as the proposed Git‐based model management approach and discuss the realization based on Enterprise Architect and LieberLieber LemonTree. In addition, we demonstrate the approach by a running example and outline future directives.

show abstract

Section: Requirement 3: Ensure Consistency Between the Versioning Of ...mentioning

confidence: 99%