Capturing Variability in Model Based Systems Engineering

Abstract

Automotive model-based systems engineering needs to be adapted to the industry specific needs, in particular by implementing appropriate means of representing and operating with variability. We rely on existing modeling techniques as an opportunity to provide a description of variability adapted to a systems engineering model. However, we also need to take into account requirements related to backwards compatibility with current practices, given the industry experience in mass customization. We propose to adopt the product line paradigm in model-based systems engineering by extending the orthogonal variability model, and adapting it to our specific needs. This brings us to an expression closer to a description of constraints, related to both orthogonal variability, and to SysML system models. We introduce our approach through a discussion on the different aspects that need to be covered for expressing variability in systems engineering. We explore these aspects by observing an automotive case study, and relate them to a list of contextual requirements for variability management.

The High-Level Variability Language

“…In fact, if variability models are written in an intermediate language, such as HLVL, they could be integrated analyzed and configured into a single model in an integrated way. This research gives continuity to previous works [8,17,19,24] that exploit the idea of relying on a variability language that unifies existing notations to provide genericity to the methods, techniques, and tools used for modeling, analysis, and configuration. Section 2 the ontological approach used to design HLVL.…”

“…More particularly, the conceptualization included languages that (1) have been transformed to logic or constraint programming to automate analysis tasks; and (2) their semantics is formally defined, and were included in other conceptualization studies. Hence, this step included feature-oriented languages [5,13,14,26]; variation point oriented languages [8,12,20,22,23]; and decision-oriented languages [4,6,7,25]. Finally, the review included proposals introducing constructs for modeling complex variability relations, such as conditional and quantified constraints [8,14,21].…”

Model-based systems engineering with requirements variability for embedded real-time systems

“…Product Line Engineering can be applied to Embedded RTS development to reduce the costs and schedules [33]. Requirement engineering is critical for Embedded Real-Time Systems, as a good requirement plan leads to less changes and risks being identified during the implementation stage.…”

“…As the paper by C. Dumitrescu et al [33] suggests, variability should be compatible with legacy documents. Using the integrated variability documentation method requires changing the complexity of development artefacts by introducing both commonality and variability into existing models [9].…”

Modeling variability in the video domain: language and experience report

“…Dumitrescu et al [11,12] reported on their experience in an automotive model based systems engineering. Mussbacher et al [21] propose an extension of the Aspect-oriented User Requirements Notation (AoURN) to support variability modeling.…”