Save interfaces to dictionary
saves all locally defined interfaces to a shared dictionary with additional options.
Save to Dictionary
Create a model, add an interface to the model's interface dictionary, and add an element. Save all interfaces defined in the model to a shared dictionary.
arch = systemcomposer.createModel('newModel',true); interface = addInterface(arch.InterfaceDictionary,'newSignal'); element = addElement(interface,'newElement','Type','double'); saveToDictionary(arch,'MyInterfaces')
model — Architecture model
Architecture model, specified as a
dictionary — Interface dictionary
Interface dictionary, specified as a
dictionaryName — Dictionary name
character vector | string
Dictionary name, specified as a character vector or string. If a dictionary with this name does not exist, one will be created.
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
CollisionResolutionOption — Option to resolve interface collisions using model or dictionary
systemcomposer.interface.CollisionResolution.USE_MODEL (default) |
Option to resolve collisions using model or dictionary, specified as the
comma-separated pair consisting of
one of the following:
systemcomposer.interface.CollisionResolution.USE_MODELto prioritize interface duplicates using the local interfaces defined in the model.
systemcomposer.interface.CollisionResolution.USE_DICTIONARYto prioritize interface duplicates using the interfaces defined in the saved dictionary.
|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 SLX files.
|Create an Architecture Model with Interfaces and Requirement Links|
|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|
|interface data dictionary||An interface data dictionary is a consolidated list of all the interfaces and value types in an architecture and where they are used.|
Local interfaces on a System Composer model can be saved in an interface data dictionary using the Interface Editor.
Interface dictionaries can be reused between models that need to use a given set of interfaces, elements, and value types. Data dictionaries are stored in separate SLDD files.
|data interface||A data interface defines the kind of information that flows through a port. The same interface can be assigned to multiple ports. A data interface can be composite, meaning that it can include data elements that describe the properties of an interface signal.||Data interfaces represent the information that is shared through a connector and enters or exits a component through a port. Use the Interface Editor to create and manage data interfaces and data elements and store them in an interface data dictionary for reuse between models.||Create an Architecture Model with Interfaces and Requirement Links|
|data element||A data element describes a portion of an interface, such as a communication message, a calculated or measured parameter, or other decomposition of that interface.|
Data interfaces are decomposed into data elements:
|value type||A value type can be used as a port interface to define the atomic piece of data that flows through that port and has a top-level type, dimension, unit, complexity, minimum, maximum, and description.||You can also assign the type of data elements in data interfaces to value types. Add value types to data dictionaries using the Interface Editor so that you can reuse the value types as interfaces or data elements.||Create Value Types as Interfaces|
|owned interface||An owned interface is a locally defined interface that is local to a specific port and not shared in a data dictionary or the model dictionary.||Create an owned interface to represent a value type or data interface that is local to a port.||Define Owned Interfaces Local to Ports|
|adapter||An adapter helps connect two components with incompatible port interfaces by mapping between the two interfaces. An adapter can also act as a unit delay or rate transition. Use the Adapter block to implement an adapter.|
With an adapter, you can perform functions on the Interface Adapter dialog: