createArchitectureModel

Create architecture model from component

Since R2021b

Syntax

createArchitectureModel(component,modelName)

createArchitectureModel(component,modelName,modelType)

Description

createArchitectureModel(component,modelName) creates an architecture model from the component component that references the model modelName.

Note

Components with physical ports cannot be saved as architecture models, model references, software architectures, or Stateflow^® chart behaviors. Components with physical ports can only be saved as subsystem references or subsystem component behaviors.

createArchitectureModel(component,modelName,modelType) creates an architecture model of type modelType from the component component that references the model modelName.

Examples

Create Architecture Model from Component

Save the component robotComp in the Robot.slx model and reference the model.

Create a model named archModel.slx.

model = systemcomposer.createModel("archModel",true);
arch = get(model,"Architecture");

Add two components named "electricComp" and "robotComp" to the model.

names = ["electricComp","robotComp"];
comp = addComponent(arch,names);

Save the robotComp component in an architecture model so the component references the model Robot.slx.

createArchitectureModel(comp(2),"Robot");

Create Software Architecture Model from Component

Save the component electricComp in the RobotSoftware.slx model and reference the model.

Create a model named archModel.slx.

model = systemcomposer.createModel("archModel",true);
arch = get(model,"Architecture");

Add two components named 'electricComp' and 'robotComp' to the model.

names = ["electricComp","robotComp"];
comp = addComponent(arch,names);

Save the electricComp component in a software architecture model so the component references the model RobotSoftware.slx.

createArchitectureModel(comp(1),"RobotSoftware","SoftwareArchitecture");

Create AUTOSAR Architecture Model from Component

Save the component throttlePositionControl in the autosarTpcSys.slx model and reference the model.

Create a model named archModel.slx.

model = systemcomposer.createModel("archModel",true);
arch = get(model,"Architecture");

Add two components named 'throttlePositionControl' and 'Sensor' to the model.

names = ["throttlePositionControl","Sensor"];
comp = addComponent(arch,names);

Save the throttlePositionControl component in a software architecture model so the component references the model autosarTpcSys.slx.

createArchitectureModel(comp(1),"autosarTpcSys","ClassicAUTOSARArchitecture");

Input Arguments

component — Component

component object

Component, specified as a systemcomposer.arch.Component object. The component must have an architecture with definition type composition. For other definition types, this function gives an error.

modelName — Name of model

character vector | string

Name of model, specified as a character vector or string.

Example: "exMobileRobot"

Data Types: char | string

modelType — Type of model

"Architecture" (default) | "SoftwareArchitecture" | "ClassicAUTOSARArchitecture" | "AdaptiveAUTOSARArchitecture"

Type of model, specified as one of these values:

• "Architecture" – An architecture model

• "SoftwareArchitecture" – A software architecture model

• "ClassicAUTOSARArchitecture" – A Classic AUTOSAR architecture model

• "AdaptiveAUTOSARArchitecture" – An Adaptive AUTOSAR architecture model

Data Types: char | string

More About

Definitions

Term	Definition	Application	More Information
architecture	A System Composer™ architecture represents a system of components and how they interface with each other structurally and behaviorally.	Different types of architectures describe different aspects of systems. You can use views to visualize a subset of components in an architecture. You can define parameters on the architecture level using the Parameter Editor.	Compose Architectures Visually Author Parameters in System Composer Using Parameter Editor
model	A System Composer model is the file that contains architectural information, including components, ports, connectors, interfaces, and behaviors.	Perform operations on a model: Extract the root-level architecture contained in the model. Apply profiles. Link interface data dictionaries. Generate instances from model architecture. A System Composer model is stored as an SLX file.	Create 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 architectural 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. Transfer information between components with: Port interfaces using the Interface Editor Parameters using the Parameter Editor	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: Component ports are interaction points on the component to other components. Architecture ports are ports on the boundary of the system, whether the boundary is within a component or the overall architecture model.	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

Term	Definition	Application	More Information
reference component	A reference component is a component whose definition is a separate architecture model, Simulink® behavior model, or Simulink subsystem behavior. A reference component represents a logical hierarchy of other compositions.	You can reuse compositions in the model using reference components. There are three types of reference components: Model references are Simulink models. Subsystem references are Simulink subsystems. Architecture references are System Composer architecture models or subsystems.	Implement Component Behavior Using Simulink Create Architecture Reference
parameter	A parameter is an instance-specific value of a value type.	Parameters are available for inlined architectures and components. Parameters are also available for components linked to model references or architecture references that specify model arguments. You can specify independent values for a parameter on each component.	Author Parameters in System Composer Using Parameter Editor Access Model Arguments as Parameters on Reference Components Use Parameters to Store Instance Values with Components
subsystem component	A subsystem component is a Simulink subsystem that is part of the parent System Composer architecture model.	Add Simulink subsystem behavior to a component to author a subsystem component in System Composer. You cannot synchronize and reuse subsystem components as Reference Component blocks because the component is part of the parent model.	Create Simulink Subsystem Behavior Using Subsystem Component Create Simulink Subsystem Component
state chart	A state chart diagram demonstrates the state-dependent behavior of a component throughout its state lifecycle and the events that can trigger a transition between states.	Add Stateflow chart behavior to describe a component using state machines. You cannot synchronize and reuse Stateflow chart behaviors as Reference Component blocks because the component is part of the parent model.	Implement Behaviors for Architecture Model Simulation Implement Component Behavior Using Stateflow Charts

Term	Definition	Application	More Information
software architecture	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.	Author Software Architectures Simulate and Deploy Software Architectures
software component	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.	Implement Behaviors for Architecture Model Simulation Create Software Architecture from Component
software composition	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
function	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
service interface	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.	Author Service Interfaces for Client-Server Communication systemcomposer.interface.ServiceInterface
function element	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: Synchronous execution — When the client calls the server, the function runs immediately and returns the output arguments to the client. Asynchronous execution — When the client makes a request to call the server, the function is executed asynchronously based on the priority order defined in the Functions Editor and Schedule Editor and returns the output arguments to the client.	systemcomposer.interface.FunctionElement
function argument	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: Type, Dimensions, Units, Complexity, Minimum, Maximum, and Description.	systemcomposer.interface.FunctionArgument
class diagram	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

Version History

Introduced in R2021b