Acronym · Design & Architecture
MBSE (Model-Based Systems Engineering)
Model-based systems engineering (MBSE): developing a system from connected models of its requirements, architecture and behaviour, rather than from separate documents, so that changes and their effects can be traced and checked.
- Also known as
- Model-based systems engineering
- Type
- Acronym
- Domain
- Design & Architecture, Modelling and ESL
Overview
MBSE (model-based systems engineering) is an approach to systems engineering in which a system's requirements, structure, behaviour and verification are captured in formal, connected models rather than in separate documents, so that the models become the main record of the design. Because elements in the model are linked, a change to one requirement or interface can be traced to everything it affects. It is used mostly for complex systems such as aircraft, spacecraft and vehicles, and chip teams usually meet it when their silicon is part of such a system.
How it works
Engineers build a system model in a standardised modelling language, most often SysML, using a modelling tool. Requirements are captured as model elements and linked to the parts of the architecture that satisfy them and to the tests that verify them. Structure diagrams describe the system's parts and interfaces, behaviour diagrams describe what it does, and parametric constraints tie properties such as performance, reliability or mass to analyses. The model sits in a central repository that serves as a single source of truth and technical baseline, and documents for reviews or customers can be generated from it.
Models differ in scope, domain, formality and level of abstraction, and teams combine them: a high-level system model, discipline models for electrical or thermal behaviour, and executable models for simulation. With enough fidelity, system models can act as digital twins, letting teams test and analyse a design virtually before hardware exists. SysML v2.0, which the Object Management Group published as a formal specification in September 2025, is the current version of the language.
The main limits are effort and tooling. Building and maintaining models needs skills and discipline, stakeholders may still expect documents, and links from system models down into chip implementation flows remain weak: in chip design RTL is still the closest thing to an executable specification.
Examples
- An automotive tier 1 supplier modelling an electronic control unit in SysML and deriving the requirements for the microcontroller inside it.
- A requirements model that links each chip-level requirement to its parent system requirement and to the verification test that covers it.
- Generating SystemC structure for hardware architecture work from a UML or SysML system model, as some tool vendors have offered.
- A digital twin of a satellite subsystem used to analyse behaviour under conditions that would be impractical to test physically.
Why it matters
For chip companies, MBSE matters most at the boundary with customers' systems. Automotive, aerospace and defence customers increasingly hand down requirements and interfaces from system models, and chip architects, functional safety engineers and requirements managers must trace those requirements into the chip specification and back to verification evidence.
In the chip lifecycle, MBSE is used mainly at concept and architecture, to capture requirements and explore partitioning; its traceability links then carry through design and verification, and support the evidence needed for safety cases and qualification.
It matters most to: Automotive SoC Architect, Chip Architect, Functional Safety Architect (Silicon), SoC Architect, SystemC TLM Modeling Engineer
Common confusions
- Not the same as SysML
- SysML is a modelling language. MBSE is the overall approach and set of practices, which can use SysML or other languages and frameworks. MBSE vs SysML
- Not the same as model-based design
- Model-based design usually means building executable models of control algorithms and generating code or hardware from them. MBSE covers the whole system, from requirements and architecture to verification.
- Not the same as electronic system level (ESL) modelling
- ESL models such as SystemC transaction-level models simulate chip and system hardware behaviour for architecture and software work. MBSE models capture requirements and system architecture and may feed those simulations.
Related standards
- OMG SysML (systems modelling language)
- ISO/IEC/IEEE 15288 (system life cycle processes)
Sources
- Model-Based Systems Engineering (MBSE) (Caitlyn Singam and Jeffrey Carter, lead authors) (opens in a new tab), SEBoK, Systems Engineering Body of Knowledge, 2026-10-22
- About the OMG System Modeling Language Specification Version 2.0 (opens in a new tab), Object Management Group, 2026-10-22
- ISO/IEC/IEEE 15288:2023 Systems and software engineering, System life cycle processes (opens in a new tab), ISO, 2026-10-22
- ROI Not There Yet For SysML (Ann Mutschler, 24 September 2015) (opens in a new tab), Semiconductor Engineering, 2026-10-22
Related terms
Part of the Design & Architecture glossary, with every term in the topic and the lifecycles, tools and standards that use them.
Where it appears on the Hub
Used on 4 pages of the Hub. In each group, the pages that mention it most come first.
Suggest an improvement
Suggest an improvement to this entry
A clearer definition, an example, a correction or a source an editor can check. Editors review every suggestion before the entry changes.
Last reviewed . Written by The Semiconductor Hub editorial team. The full glossary