3.1.1 Model Lifecycle Management for MBSE

Abstract

Model Based Systems Engineering (MBSE) is an evolving practice in the early stages of adoption similar to the mechanical, electrical and software domains 20 to 30 years ago. Today there is increasing recognition of the potential MBSE brings to system life cycle processes with the increasing complexity of systems and the demands of the global marketplace. In order for the practice to realize this potential, system modeling and MBSE must be part of the larger model based engineering effort, and integrate with other engineering discipline models and modeling activities across the life cycle of a system. This is placing increasing demands on the need for Model Lifecycle Management (MLM) as an essential part of an MBSE infrastructure. This paper establishes the motivation for MLM, as well as laying the foundation for addressing challenges that lay ahead. The paper is focused on describing key concepts, requirements, current practices, and future directions of MLM, and setting the basis for more in depth overview of MLM solutions and vendor offering that are beyond the scope of this paper. Motivation -Model Lifecycle Management as an Enabler of Model-Based Systems Engineering (MBSE)Smarter and more complex products enter our lives every day. The modern society in the 21th century is more dependent than ever on such systems that serve our basic needs for health, communication, transportation, financial management, education, entertainment and much, much more. These smarter products today are not independent. They usually consist of collections of other constituent systems, and often dependent on the behavior of external systems. Products are more and more autonomous, capable of optimizing their operation and perform goal-seeking behaviors. Moreover, we witness the growing importance of smarter, cyber-physical systems that combine software, hardware, mechanical and electrical components. Ever increasing demands on system performance is driving tighter integration of the engineering disciplines to provide this performance. This convergence of engineering disciplines, as well as growing business challenges such as shorter time to market, strict safety requirements, higher product quality and stricter regulatory compliance increase the need for new and holistic system approaches and methodologies that support system design. These factors have led to the the engineering domain innovators to modeling, abstraction and multi-disciplinary

A systematic literature review of cross-domain model consistency checking by model management tools

“…A model is a representation of reality, an abstraction of something relevant to the stakeholder described using welldefined and unambiguous languages [48].…”

An Mbse-Based Approach for the Definition and Evaluation of Engineering It Architectures

“…Since SE is an interdisciplinary approach, it inherently leads to cross-domain cutting, heterogeneous artefacts. Moreover, these artefacts need to be controlled by overarching, consistent lifecycle management processes such as configuration management (ISO, 2015;Fisher et al, 2014). In addition, traceability is required by normative aspects (ISO, 2010) or engineering methods (Friedenthal et al, 2012) implying the linkage of different artefacts.…”

“…SE is an interdisciplinary approach to successfully design complex systems (Gausemeier et al, 2013), generating -besides other engineering approaches -a rising number of heterogeneous artefacts (information carrier) (Alvarez-Rodríguez et al, 2019). The engineering approaches comprise new engineering processes and methods, which pose new challenges to the engineering IT such as traceability or end-to-end configuration management (Fisher et al, 2014). In addition, digitalization has a major impact on engineering.…”

Collaborative Model‐based Systems Engineering for Cyber‐Physical Systems, with a Building Automation Case Study

“…Traceable documentation is crucial to model-based systems engineering to record design rationale, and to help estimate the impact of change and evolution (Fisher et al, 2014). In a traditional document-centric approach, traceability matrices may be used to map external sources to system requirements, system requirements to software/physical requirements, and so on to detailed design, implementations, and test documentation.…”