Architecture Views Gallery
Create and manage architecture views and sequence diagrams
The Architecture Views Gallery allows you to create filtered and freeform architecture views and author sequence diagrams.
Use the View Configurations options to specify component and port filters for views, and to specify grouping criteria. Click and drag components from the Model Components browser to specify the contents of a freeform view. Select views from the View Browser and use the Component Properties options to specify a name, color, and description for a view.
Switch between these types of view diagrams:
Component Diagram — Display components, ports, and connectors based on how the model is structured.
Component Hierarchy — Display components in tree form with parents above children. In a component hierarchy view, each referenced model is represented as many times as it is used.
Architecture Hierarchy — Display unique component architecture types and their relationships using composition connections. In an architecture hierarchy view, each referenced model is represented only once.
Class Diagram — Display unique architecture types of the software components optionally with software methods and properties, only available for software architecture models.
You can also link and edit requirements for views through the Architecture Views Gallery.
To create a new sequence diagram, click New > Sequence Diagram. Select existing sequence diagrams from the View Browser and use the Sequence Diagram Properties options to specify a name for the sequence diagram. To add a lifeline, click and drag from the Model Components browser. Alternatively, select Component > Add Lifeline from the menu and click the down arrow to select a component to be represented by the lifeline. Click and drag from the vertical dotted lines coming down from one lifeline to another to author a message that represents a connection between two ports. To confirm the consistency of the sequence diagram, click Check Consistency. Then, either push changes to the architecture by clicking Create in Architecture, or pull changes in from the architecture to the sequence diagram by clicking Repair.
Open the Architecture Views Gallery
- Modeling System Architecture of Keyless Entry System
- Create Architectural Views Programmatically
- Create Architecture Views Interactively
- Display Component Hierarchy and Architecture Hierarchy Using Views
- Class Diagram View of Software Architectures
- Describe System Behavior Using Sequence Diagrams
- Simulate Sequence Diagrams for Traffic Light Example
New — Create new view or sequence diagram
Create a new view by default by clicking New, or click the drop-down arrow to choose New > View. Create a new sequence diagram by selecting New > Sequence Diagram.
Save — Save views, sequence diagrams, and model
Save all views, sequence diagrams, and the architecture model.
Delete — Delete currently selected diagram
Delete the currently selected view or sequence diagram.
Run Query — Refresh currently selected view
Refresh the currently selected view with changes in the composition and rerun the corresponding filter, if it exists.
Add — Add selected component to view
Add the selected component in the Model Components browser to the current view diagram.
If the view is a filtered view, a prompt appears to convert the filtered view to a freeform view.
Remove — Remove selected component from view
Remove a selected component in a view from the current view diagram.
If the view is a filtered view, a prompt appears to convert the filtered view to a freeform view.
Group — Group selected components in view
Group the selected components in a view.
Ungroup — Ungroup selected components in view
Ungroup the selected components in a view.
Pivot — Pivot to other view diagrams in which selected component appears
Pivot to other view diagrams in which selected component appears. Use the drop-down list to select the view diagram to which to pivot.
Display Depth — Modify number of levels of hierarchy to display
Deep (default) | Shallow
Modify the number of levels of hierarchy to display. Deep includes more levels and Shallow includes fewer levels.
Export — Export to image
Export the currently selected diagram as an image. View diagrams can be saved as PDF files. Sequence diagrams can be saved as PDF files or image files.
Add Lifeline — Insert new lifeline into sequence diagram
Create a new lifeline after the selected lifeline by default by clicking Add Lifeline, or click the drop-down arrow to choose Add Lifeline > Insert After. Create a new lifeline before the selected lifeline by selecting Add Lifeline > Insert Before. Create a new lifeline nested under the selected lifeline by selecting Add Lifeline > Add Child.
Add Operand — Insert new operand into sequence diagram
Create a new operand after the selected operand by default by clicking Add Operand, or click the drop-down arrow to choose Add Operand > Insert After. Create a new operand before the selected operand by selecting Add Operand > Insert Before.
Check Consistency — Check whether elements in sequence diagram are consistent with architecture model
Check that all the elements in the current sequence diagram are consistent with the architecture model. If any of the elements in the sequence diagram are inconsistent, clicking Check Consistency highlights those elements in yellow.
Architecture Element — Specify different associated element in architecture model for selected elements in sequence diagram
component | port
Specify a different associated element in the architecture model for the selected elements in the sequence diagram.
Create in Architecture — Create elements in architecture model
Create elements in the architecture model for each of the selected inconsistent elements in the sequence diagram.
Repair — Update selected elements so sequence diagram is consistent with architecture model
Update the selected inconsistent elements in the sequence diagram so the sequence diagram is consistent with the architecture model.
Run — Run simulation
Run model simulation and verify that the model simulation results match the interactions within the sequence diagrams.
Pause — Pause simulation
Pause model simulation and sequence diagram simulation.
Stop — Stop simulation
Stop model simulation and sequence diagram simulation.
Continue — Continue simulation
Continue model simulation until the end and verify that the model simulation results match the interactions within the sequence diagrams.
Next Message — Continue until next message is hit
Continue until next message is hit and verify that the model simulation results match the interactions within the sequence diagrams.
Clear Results — Clear simulation results
Clear simulation results and remove green check marks or red warning marks on the sequence diagram.
openViews(model) opens the Architecture Views Gallery
from the MATLAB Command Window.
A view shows a customizable subset of elements in a model. Views can be filtered based on stereotypes or names of components, ports, and interfaces, along with the name, type, or units of an interface element. Create views by adding elements manually. Views create a simplified way to work with complex architectures by focusing on certain parts of the architectural design.
You can use different types of views to represent the system:
Operational views demonstrate how a system will be used and should be integrated with requirements analysis.
Functional views focus on what the system must do to operate.
Physical views show how the system is constructed and configured.
An element group is a grouping of components in a view.
Use element groups to programmatically populate a view.
A query is a specification that describes certain constraints or criteria to be satisfied by model elements.
Use queries to search elements with constraint criteria and to filter views.
A component diagram represents a view with components, ports, and connectors based on how the model is structured.
Component diagrams allow you to programmatically or manually add and remove components from the view.
You can visualize a hierarchy diagram as a view with components, ports, reference types, component stereotypes, and stereotype properties.
There are two types of hierarchy diagrams:
Component hierarchy diagrams display components in tree form with parents above children. In a component hierarchy view, each referenced model is represented as many times as it is used.
Architecture hierarchy diagrams display unique component architecture types and their relationships using composition connections. In an architecture hierarchy view, each referenced model is represented only once.
A class diagram is a graphical representation of a static structural model that displays unique architecture types of the software components optionally with software methods and properties.
Class diagrams capture one instance of each referenced model and show relationships between them. Any component diagram view can be optionally represented as a class diagram for a software architecture model.
A sequence diagram represents the expected interaction between structural elements of an architecture as a sequence of message exchanges.
Use sequence diagrams to describe how the parts of a system interact.
A lifeline is represented by a head and a timeline that proceeds down a vertical dotted line.
The head of a lifeline represents a component in an architecture model.
A message sends information from one lifeline to another. Messages are specified with a message label.
A message label has a trigger and a constraint. A trigger determines whether the message occurs. A constraint determines whether the message is valid.
An annotation describes the elements of a sequence diagram.
Use annotations to provide detailed explanations of elements or workflows captured by sequence diagrams.
A fragment indicates how a group of messages within it execute or interact.
A fragment is used to model complex sequences, such as alternatives, in a sequence diagram.
An operand is a region in a fragment. Fragments have one or more operands depending on the kind of fragment. Operands can contain messages and additional fragments.
Each operand can include a constraint to specify whether the messages inside the operand execute. You can express the precondition of an operand as a MATLAB Boolean expression using the input signal of any lifeline.
Introduced in R2019b