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:
Functional architecturedescribes the flow of data in a system.
Logical architecturedescribes the intended operation of a system.
Physical architecturedescribes the platform or hardware in a system.
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.
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:
Component portsare interaction points on the component to other components.
Architecture portsare ports on the boundary of the system, whether the boundary is within a component or the overall architecture model.
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.
一个接口定义的信息flows through a port. The same interface can be assigned to multiple ports. An interface can be composite, meaning that it can include elements that describe the properties of an interface signal.
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 interfaces and interface elements and store them in an interface data dictionary for reuse between models.
An interface element describes a portion of an interface, such as a communication message, a calculated or measured parameter, or other decomposition of that interface.
Interface elements describe the decompositions of an interface:
An interface data dictionary is a consolidated list of all the interfaces 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 and interface elements. Data dictionaries are stored in separate.slddfiles.
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.
With an adapter, you can perform three functions on the Interface Adapter dialog:
Create and edit mappings between input and output interfaces.
Apply an interface conversionUnitDelayto break an algebraic loop.
Apply an interface conversionRateTransitionto reconcile different sample time rates for reference models.
You can also select a web site from the following list:
How to Get Best Site Performance
Select the China site (in Chinese or English) for best site performance. Other MathWorks country sites are not optimized for visits from your location.