Skip to content

Glossary Modeling foundations

What is model-based systems engineering?

Model-based systems engineering (MBSE) keeps a system's parts, requirements, interfaces, behavior and verification in one connected model.

Also called MBSE.

Model-based systems engineering

Model-based systems engineering, or MBSE, is the practice of describing a system in a structured model rather than in a set of separate documents. The model holds the system's parts, its requirements, the interfaces between parts, its behavior and how each requirement will be verified, along with the relationships among them. Diagrams, tables and documents become views of that one model, so they agree with each other. INCOSE describes it as the formalized application of modeling to requirements, design, analysis, verification and validation, from conceptual design onward.

Why it matters

When the relationships live in the model, questions that are slow to answer from documents become lookups: which requirements a part carries, what a changed interface affects, which requirements have no plan to verify them. A change is made once, and every view that reads the model shows it.

How it goes wrong

  • Treating a diagram as the model, so the views drift apart
  • Keeping requirements, interfaces and test plans in separate files that are never reconciled
  • Starting to model only after the early decisions were made in meetings and slides

In Cairn

Cairn keeps one structured model per project: a system tree of nodes, with requirements, interfaces and their signals, state machines, use cases, verifications and trace links attached. Lenses such as Architecture, Requirements, Behavior and Verification are views of that model. Every change to it, by hand or proposed by AI, is a ChangeSet checked by the same guard. The model is Cairn's own, not SysML. A project lives in one person's browser, can back up to their account, and exports as a .cairn.zip.

Questions

Is MBSE only for large aerospace and defense programs?
No. It is most common there, but keeping a system's parts, requirements and interfaces in one connected model is useful on smaller hardware projects too, especially early, while the structure is still changing.
Is Cairn a formal MBSE tool?
No. Cairn applies MBSE ideas to forming a first model with AI. It does not use SysML or another standard modeling language, and a project lives in one person's browser.

See it on your own system.

Describe what you are building and Cairn interviews you, then builds the first model with you.