Model-based systems engineering

from Wikipedia, the free encyclopedia

Model-based systems engineering ( MBSE ) is a system engineering methodology in which information about a (to be developed) system is no longer based exclusively on documents, but on models.

These models are usually created on the basis of the UML or SysML specification.

definition

In 2007 the International Council on Systems Engineering (INCOSE) defined MBSE as “the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases.”

So something like this:

"[MBSE is] the use of formalized modeling [of a system] with the aim of assisting with the various aspects such as requirements, design, analysis, and testing and validation, from the very beginning to the later stages in the life cycle [ of the system]. "

In applications where the relevance of modeling the mere technical system exceeds Description considerably and is an integral part of the development process, the concept of model-driven systems engineering (sometimes Model Driven Systems Engineering , MDSE) is used.

advantages

Systems engineering models have several advantages over plain text documents:

  • "A picture is worth a thousand words"
  • In this way, content can be better visualized and recorded.
  • The approach allows different perspectives on the same model, so that, for example, information that is not relevant for a task can be hidden.
  • As a rule, natural language is ambiguous. Statements are interpreted differently depending on previous knowledge, understanding or culture. The semi-formal representation, on the other hand, is strict and clear. That avoids misunderstandings.
  • The strict and clear presentation supports automatic plausibility tests.
  • Software can also be created directly from models. See also model-driven software development .

According to Robert Cloutier , this should enable all those involved in the project to gain a better understanding of the problem and a comprehensive mastery of complexity .

literature

  • Claudio Zuccaro et al. (Ed.): GfSE SE manual. The bracket in technical development . Society for Systems Engineering, GfSE Verlag, 2019, ISBN 9783981880564 .
  • Tim Weilkiens: Systems engineering with SysML / UML: requirements, analysis, architecture . dpunkt.verlag, Heidelberg 2009, ISBN 978-3-89864-577-5 .
  • INCOSE / GfSE (Ed.): INCOSE Systems Engineering Handbook. A guide to system lifecycle processes and activities. Fourth edition . Society for Systems Engineering, GfSE Verlag, 2015, ISBN 978-3-9818805-0-2 .

Individual evidence

  1. ^ SE Vision 2020. In: INCOSE. INCOSE - International Council on Systems Engineering, February 23, 2009, accessed May 4, 2020 .
  2. ↑ Michael Jastram: Quite well driven. The difference between MBSE and MDSE. In: Systems Engineering Trends. Formal Mind GmbH, April 27, 2017, accessed on May 4, 2020 .
  3. ↑ Systems engineering. What is MBSE? In: two pillars. Two Pillars GmbH, September 12, 2018, accessed on May 4, 2020 .