In our previous article, ‘MBSE – Model-Based Systems Engineering’, we introduced the fundamentals of model-based systems engineering. In this technical article, we explore the topic in greater depth and demonstrate how MBSE can help to structure complex development processes, make interdependencies transparent and improve collaboration between different engineering disciplines.
When traditional development approaches reach their limits
Modern products are increasingly becoming complex, integrated systems. Mechanical, electronic, software and sensor components not only must function individually but also work together as an integrated system. At the same time, demands on quality, functionality and development speed are rising.
In document-based development approaches, information is often managed across various documents, spreadsheets and software solutions. If requirements or system components change, the relevant information has to be checked and updated in several places. This can lead to inconsistencies that only become apparent in later stages of development.
This is where Model-Based Systems Engineering (MBSE) comes in: Rather than considering individual documents in isolation, the focus is on digital system models. These models represent key properties, structures and interrelationships within a system, thereby supporting a consistent view throughout the development process.
What is MBSE?
MBSE refers to the formalized use of models to support system development. This includes, amongst other things, the capture and management of requirements, the design of the system architecture, as well as analysis, verification and validation.
A model provides an abstract representation of selected aspects of a real or planned system. It highlights interrelationships and creates a common basis whereupon different specialist disciplines can work.
It is crucial that the models are linked to one another. This makes it possible, for example, to trace which function a particular requirement fulfills and what components are responsible for implementing it. As a result, the impact of changes can be better assessed.
MBSE does not necessarily replace all documentation. Instead, the required documentation and different system views can stem from the existing models. The aim is to manage information more consistently and to ensure that interrelationships remain traceable throughout the entire development process.
From requirements to system architecture: RFLP and SysML
The RFLP approach is one of the methods used to structure system development. The acronym stands for four interrelated levels of analysis:
- Requirements: What requirements and expectations must the system fulfil?
- Functional: What functions are required to implement these requirements?
- Logical: How are the functions logically structured and interconnected?
- Physical: Which specific components and technical elements make up the system?
This framework helps to systematically link requirements with functions, logical structures and physical implementation. This makes it clear how individual development decisions stem from the original requirements.
For instance, SysML (Systems Modelling Language) can be used for modeling. This graphical modeling language offers standardized ways of representing the structures, behavior and interrelationships of technical systems.
It is important to note that MBSE is not the same as SysML: MBSE describes the overarching methodology for model-based systems engineering, while SysML is one possible language for creating the models required for this purpose. Which methods, languages and tools are suitable depends, among other things, on the requirements, system complexity, and the existing development processes.
What are the benefits of MBSE?
The model-based approach can offer several benefits, particularly in complex development projects.
Greater transparency and better collaboration: A shared system model makes it easier for different disciplines to understand the overall architecture and its interdependencies. It creates a common information base and facilitates coordination between those involved.
Traceable requirements and changes: Links between requirements, functions and components make it easier to trace those elements affected by a change. This promotes consistency in system information and simplifies assessing potential impacts.
Early fault detection: Analyses and simulations can help to identify problems as early as the initial development phases – before costly physical prototypes or integration steps become necessary. This may allow mistakes to be corrected at an earlier stage.
Consistency throughout the lifecycle: The system models can serve as a basis for testing, verification, validation, and subsequent changes even beyond the design and development phases. Thus, MBSE also forms an important building block for digital engineering and can support the development of digital twins.
However, the extent to which these benefits are actually realized depends on the specific implementation, the quality of the models and their integration into existing processes.
What needs to be taken into account during implementation?
MBSE is not merely an IT project. Its implementation requires a coordinated interplay of methods, processes, tools and qualified staff.
Companies should first clarify which challenges they wish to address using the model-based approach. A clearly defined pilot use case can help to test suitable modeling methods, define responsibilities, and assess the specific benefits.
Equally important are integration into existing engineering and PLM processes, consistent data management, and clear rules for maintaining and further developing the models. Without coordinated working practices and adequate training, there is a risk that new models will simply create additional data assets rather than bringing about sustainable improvements to existing development processes.
Conclusion: MBSE as a building block of digital engineering
The more complex technical systems become, the more important it is to have transparent interrelationships, consistent information, and close collaboration between the relevant disciplines. MBSE offers a structured approach to this by using digital system models to link requirements, architecture and development steps.
Success, however, does not depend solely on the software used: It is only the combination of suitable methods, clear processes, integrated tools and qualified staff that makes the model-based approach an effective component of an end-to-end engineering strategy.

Deutsch