Main Content

addFunction

Add functions to architecture of software component

Description

example

functions = addFunction(architecture,functionNames) adds a set of functions with the names specified, functionNames to the software architecture component architecture.

To remove a function, use the destroy function.

Examples

collapse all

Create a model named mySoftwareArchitecture and get the root architecture.

model = systemcomposer.createModel("mySoftwareArchitecture","SoftwareArchitecture");
rootArch = model.Architecture
Architecture with properties:
 
                   Name: 'mySoftwareArchitecture'
             Definition: Composition
                 ...
            ExternalUID: ''
              Functions: []
  

Create a software component and two functions.

newComp = rootArch.addComponent("C1");
newFuncs = newComp.Architecture.addFunction({'f1','f2'});
rootArch
rootArch =
 
  Architecture with properties:
 
                   Name: 'mySoftwareArchitecture'
             Definition: Composition
                ...
            ExternalUID: ''
              Functions: [1x2 systemcomposer.arch.Function]
  

Input Arguments

collapse all

Software architecture, specified as a systemcomposer.arch.Architecture object. The addfunction function adds functions to the software architecture of a component. Use <component>.Architecture to access the architecture of a component.

Names of functions, specified as a cell array of character vectors or an array of strings.

Data Types: char | string

Output Arguments

collapse all

Created functions, returned as an array of systemcomposer.arch.Function objects.

More About

collapse all

Definitions

TermDefinitionApplicationMore 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.

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.

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 the Software Architecture of a Throttle Position Control System
software function

A software function is an entry point that can be defined in a software component.

You can apply stereotypes to software functions, edit sample times, and specify the function period using the Functions Editor.

Author and Extend Functions for Software Architectures
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 R2022a