Model-based systems engineering

Architecture in TraceUnified is model-based systems engineering (MBSE): your system is captured as a single, structured model, and diagrams are views onto that model. This is fundamentally different from drawing pictures, and it’s what lets architecture participate in the thread alongside requirements, tests, and risk.

The model is the source of truth

In a drawing tool, each diagram is its own artifact; the same component drawn on two diagrams is two unrelated shapes. In a model, a component exists once. Show it on several diagrams and they’re all views of the same element — change it in one place and every view reflects it. The model, not any single picture, is the truth.

Native SysML

The model is expressed in SysML, the standard modeling language for systems engineering. Blocks, ports, connectors, constraints, and the relationships between them are real, typed model elements — not free-form boxes and lines. Working in a recognized language means your architecture is precise, reviewable, and portable.

Part of the same database

Because the model lives in the same database as everything else, an architecture element can be linked directly to the requirement it realizes and the test that verifies it. The model isn’t a document attached to the project — it’s connected to the rest of the lifecycle, so impact and coverage flow through it like any other artifact.

Governed like the rest

The model is controlled the way controlled records are. Edits on the canvas capture a reason for change, the model is versioned through descriptive commits, and it can be captured in baselines — so you can see how the architecture evolved and prove what it looked like at any milestone. The rest of this section builds from here: the diagram types you’ll use, the canvas you’ll work in, and how the model connects to requirements.