Move interface to another interface dictionary
Create a new model and get its architecture.
model = systemcomposer.createModel("archModel"); systemcomposer.openModel("archModel"); arch = model.Architecture;
Create a new dictionary,
Interfaces.sldd, and add a new data
dictionary = systemcomposer.createDictionary("Interfaces.sldd"); interface = dictionary.addInterface("GPSInterface");
Create a second dictionary,
InterfacesNew.sldd, and add a new
SSDInterface. Link the dictionary to your
newDict = systemcomposer.createDictionary("InterfacesNew.sldd"); newInterface = newDict.addInterface("SSDInterface"); linkDictionary(model,"InterfacesNew.sldd");
GPSInterface data interface to the second dictionary
View the Interface
Editor. Confirm that the
GPSInterface data interface is now
part of the
InterfacesNew.sldd interface data dictionary.
interface — Interface
value type object | data interface object | physical interface object | service interface object
dictionary — Data dictionary
Data dictionary, specified as a
systemcomposer.interface.Dictionary object. You can specify the default
data dictionary that defines local interfaces or an external data dictionary that
carries interface definitions. If the model links to multiple data dictionaries, then
dictionary must be the dictionary that carries interface
definitions. For information on how to create a dictionary, see
|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. You can reuse interface dictionaries between models that need to use a given set of interfaces, elements, and value types. Linked data dictionaries are stored in separate SLDD files.
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.
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:
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
An owned interface is an 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
An adapter helps connect two components with incompatible port interfaces by mapping between the two interfaces. An adapter can act as a unit delay or rate transition. You can also use an adapter for bus creation. Use the Adapter block to implement an adapter.
With an adapter, you can perform functions on the Interface Adapter dialog box:
A physical subsystem is a Simulink® subsystem with Simscape™ connections.
A physical subsystem with Simscape connections uses a physical network approach suited for simulating systems with real physical components and represents a mathematical model.
|Implement Component Behavior Using Simscape
A physical port represents a Simscape physical modeling connector port called a Connection Port (Simscape).
Use physical ports to connect components in an architecture model or to enable physical systems in a Simulink subsystem.
|Define Physical Ports on Component
A physical connector can represent a nondirectional conserving connection of a specific physical domain. Connectors can also represent physical signals.
Use physical connectors to connect physical components that represent features of a system to simulate mathematically.
|Architecture Model with Simscape Behavior for a DC Motor
A physical interface defines the kind of
information that flows through a physical port. The same interface can be assigned to multiple
ports. A physical interface is a composite interface equivalent to a
Use a physical interface to bundle physical elements to describe a physical model using at least one physical domain.
|Specify Physical Interfaces on Ports
A physical element describes the
decomposition of a physical interface. A physical element is equivalent to a
|Describe Component Behavior Using Simscape
A software architecture is a specialization of an architecture for software-based systems, including the description of software compositions, component functions, and their scheduling.
Use software architectures in System Composer to author software architecture models composed of software components, ports, and interfaces. Design your software architecture model, define the execution order of your component functions, simulate your design in the architecture level, and generate code.
A software component is a specialization of a component for software entities, including its functions (entry points) and interfaces.
Implement a Simulink export-function, rate-based, or JMAAB model as a software component, simulate the software architecture model, and generate code.
A software composition is a diagram of software components and connectors that represents a composite software entity, such as a module or application.
Encapsulate functionality by aggregating or nesting multiple software components or compositions.
|Modeling Software Architecture of Throttle Position Control System
A function is an entry point that can be defined in a software component.
You can apply stereotypes to functions in software architectures, edit sample times, and specify the function period using the Functions Editor.
|Author and Extend Functions for Software Architectures
A service interface defines the functional interface between client and server components. Each service interface consists of one or more function elements.
Once you have defined a service interface in the Interface Editor, you can assign it to client and server ports using the Property Inspector. You can also use the Property Inspector to assign stereotypes to service interfaces.
A function element describes the attributes of a function in a client-server interface.
Edit the function prototype on a function element to change the number and names of inputs and outputs of the function. Edit function element properties as you would edit other interface element properties. Function argument types can include built-in types as well as bus objects. You can specify function elements to support:
A function argument describes the attributes of an input or output argument in a function element.
You can set the properties of a function argument in the Interface Editor just as you would any value type:
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.
|Class Diagram View of Software Architectures
Introduced in R2023b