System modeling with MBSE

The product definition is a phase in an integrated MBSE approach where the necessary assets are authored such as requirements, parameters, system architectures, interface diagrams, and domain architectures to produce 1D/3D models, along with software and test specifications. Your team uses these elements to build models that represent system and subsystem physics, and the connection of those systems through interfaces across all relevant development domains. Once available, these reusable digital models can be used in later development stages of simulation and product validation. This results in a fully specified and traceable product aligned to stakeholder requirements.

System modeling with MBSE allows you to govern domains and coordinate product development through an approach that connects the system models, their creators, and relevant development data. Therefore, software, mechanical, and electrical engineers can easily collaborate in a co-development environment.

The following table shows the high-level roles engaged with system modeling.

Role	Description
Administrator	Is familiar with configuring requirements management, system modeling, analysis requests, targets, and attributes.
System architect	Manages the overall product system model architecture that meets the requirements.
System designer	Manages specific domain areas (software, electrical, mechanical, and so on) of the system model.

Where do I go from here?

• Administrator — See Configuring system modeling.
• System architect, system designer — Learn more about how the MBSE features work together in Active Workspace. See What is Model-Based Systems Engineering (MBSE).
• Begin authoring model diagrams — See Overview of model diagramming.