Create architecture view
Open the keyless entry system example and create a view. Specify the color as light blue and the query as all components, and group by the review status.
scKeylessEntrySystem import systemcomposer.query.*; model = systemcomposer.loadModel('KeylessEntryArchitecture'); view = model.createView('All Components Grouped by Review Status',... 'Color','lightblue','Select',AnyComponent(),... 'GroupBy','AutoProfile.BaseComponent.ReviewStatus');
Open the Architecture Views Gallery to see the new view named
Components Grouped by Review Status'.
viewName— Name of new view
Name of new view, specified as a character vector.
'All Components Grouped by Review Status'
comma-separated pairs of
the argument name and
Value is the corresponding value.
Name must appear inside quotes. You can specify several name and value
pair arguments in any order as
view = model.createView('All Components Grouped by Review Status','Color','lightblue','Select',AnyComponent(),'GroupBy','AutoProfile.BaseComponent.ReviewStatus')
'Select'— Selection query
Selection query to use to populate the view, specified as a comma-separating pair
'Select' and a
systemcomposer.query.Constraint object. A constraint can contain a
sub-constraint that can be joined with another constraint using
OR. A constraint can be negated using
Query Objects and Conditions for Constraints
|A non-evaluated value for the given property or stereotype property.|
|An evaluated property value from a System Composer object or a stereotype property.|
|A component has a port that satisfies the given sub-constraint.|
|A port has an interface that satisfies the given sub-constraint.|
|An interface has an interface element that satisfies the given sub-constraint.|
|An architecture element has a stereotype that satisfies the given sub-constraint.|
|A property value is within the given range.|
|An element is a component and not a port or connector.|
|A stereotype is derived from the given stereotype.|
'GroupBy'— Grouping criteria
Grouping criteria, specified as a comma-separating pair consisting of
'GroupBy' and a cell array of properties in the form
'<profile>.<stereotype>.<property>'. The order of the
cell array dictates the order of the grouping.
'IncludeReferenceModels'— Whether to search for reference architectures
trueor 1 (default) |
Whether to search for reference architectures, specified as the comma-separated
pair consisting of
'IncludeReferenceModels' and a logical 1
true) to search for referenced architectures or 0
false) to not include referenced architectures.
'Color'— Color of view
Color of view, specified as the comma-separated pair consisting of
'Color' and a character array that contains the name of the color
or an RGB hexadecimal value.
|architecture||A System Composer architecture represents a system of components and how they interface with each other structurally and behaviorally. You can represent specific architectures using alternate views.|
Different types of architectures describe different aspects of systems:
|Compose Architecture Visually|
|model||A System Composer model is the file that contains architectural information, including components, ports, connectors, interfaces, and behaviors.|
Perform operations on a model:
System Composer models are stored as
|Create an Architecture Model|
|component||A component is a nontrivial, nearly-independent, and replaceable part of a system that fulfills a clear function in the context of an architecture. A component defines an architecture element, such as a function, a system, hardware, software, or other conceptual entity. A component can also be a subsystem or subfunction.||Represented as a block, a component is a part of an architecture model that can be separated into reusable artifacts.||Components|
|port||A port is a node on a component or architecture that represents a point of interaction with its environment. A port permits the flow of information to and from other components or systems.|
There are different types of ports:
|connector||Connectors are lines that provide connections between ports. Connectors describe how information flows between components or architectures.||A connector allows two components to interact without defining the nature of the interaction. Set an interface on a port to define how the components interact.||Connections|
|view||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. Construct views by pulling in elements manually. Views create a simplified way to work with complex architectures by focusing on certain parts of the architecture design.|
You can use different types of views to represent the system:
A viewpoint represents a stakeholder perspective that specifies the contents of the view.
|element group||An element group is a grouping of components in a view.||Use element groups to programmatically populate a view.||Create Architectural Views Programmatically|
|query||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.||Find Elements in a Model Using Queries|