A system refers to a composition of elements that interact to achieve a goal no single element could accomplish on its own. The constituent elements of a system can include mechanical parts, electrical circuits, computer hardware, and software. A system specification describes the system elements, their characteristics and properties, their interactions with each other, and the desired interaction (or interface) of the overall system with its environment.
System Composer™ enables you to describe systems in terms of architecture models as a combination of structural elements that are further elaborated by underlying behavioral descriptions. These descriptive models may sometimes be presented as distinct diagrams that are consistent with each other.
To perform a basic systems engineering workflow to design a mobile robotic arm using System Composer, see Create an Architecture Model with Interfaces and Requirement Links.
The model-based systems engineering (MBSE) workflow enabled by System Composer involves starting with stakeholder needs, identifying requirements and use cases, designing an architecture iteratively, and implementing functionality using behavior models. You can also use analyses and trade studies to optimize architectural design and communicate facets of the system using architecture views. This figure illustrates an MBSE workflow.
With System Composer, you can implement a systems engineering workflow:
Author Architecture Models and Define System Requirements
Create hierarchical models of system structure that represent functional, logical, or physical decompositions of the system using components, ports, and connectors.
Import models from MATLAB® tables and export them with System Composer changes.
Create and manage data interfaces between structural architecture elements.
Manage model-to-model allocations to establish relationships between software components and hardware components and to indicate deployment strategies.
Refine and elaborate requirements using Simulink® Requirements™. Link requirements to architectural model elements.
Define Metadata, Analyze Architectures, and Generate Views
Extend base architectural elements to create domain-specific conceptual representations.
Perform static analysis and trade studies to optimize system architectures.
Filter views of the system structure using a component diagram, hierarchy diagram, or class diagram.
Simulate System Behavior of Architecture Models and Verify Requirements
Specify component behavior using block diagrams in Simulink, state machines in Stateflow®, and physical interfaces in Simscape™ using subsystem component behaviors.
Represent the interaction between structural elements of an architecture as a sequence of message exchanges with a sequence diagram in the Architecture Views Gallery.
Design a software architecture model, define the execution order of the functions from the components, simulate the design at the architecture level, and generate code.
Verify and validate requirements with Simulink Test™.
For definitions and applications of common System Composer terms and concepts, see System Composer Concepts.