Describe Model Behaviors
Define behaviors for architecture models to determine the purpose of the system in early stages of design. Iterate on your design to meet requirements as the development process continues.
Use executable activity diagrams to assess system behavior through token flows.
Use sequence diagrams to simulate the exchange of messages and verify system behavior.
After building your system architecture, you can link components to behavior models and subsystems authored in Simulink, Simscape, and Stateflow. Then simulate the architecture model to verify your system design and test the functionality of each component to validate stakeholder needs.
Categories
- Describe Activity Diagrams
Author executable activities to visualize token flow using actions operating on objects
- Describe Sequence Diagrams
Author interactions between components in sequence of message exchanges to simulate and verify system design
- Describe Component Behaviors
Describe architectures with Simulink, Stateflow, and Simscape
You can also select a web site from the following list:
Americas
- América Latina (Español)
- Canada (English)
- United States (English)
Europe
- Belgium (English)
- Denmark (English)
- Deutschland (Deutsch)
- España (Español)
- Finland (English)
- France (Français)
- Ireland (English)
- Italia (Italiano)
- Luxembourg (English)
- Netherlands (English)
- Norway (English)
- Österreich (Deutsch)
- Portugal (English)
- Sweden (English)
- Switzerland
- United Kingdom (English)