Create Custom Views Using Architecture Views Gallery

You can use custom views integrated with System Composer™ to filter large models to display a custom subset of components. You can filter your views on criteria such as stereotypes, properties, and requirement links.

These concepts are relevant for authoring custom views:

• 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. Switch between a component diagram, component hierarchy, or architecture hierarchy. For software architectures, you can switch to a class diagram view. A viewpoint represents a stakeholder perspective that specifies the contents of the view.

• 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.

  System Composer has 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. A component diagram view can be optionally represented as a class diagram for a software architecture model.

Tip

To learn more about how System Composer concepts apply to systems engineering design, see System Composer Concepts.

Views are integrated with architecture models in System Composer. The table lists topics about using views.

Topic	Description
Author Architecture Models Through Component Diagram Views	Use component diagram views to author architecture models.
Create Architecture Views Interactively	View structural and functional model hierarchies interactively.
Create Architecture Views Programmatically	View structural and functional model hierarchies programmatically using queries.
Display Component Hierarchy and Architecture Hierarchy Using Views	Use hierarchy diagrams to view different aspects of architecture models.
Create Spotlight Views	View components in the context of the entire architecture.

Create a view in the Architecture Views Gallery by clicking New > View.