destroy

Remove model element

Syntax

destroy(element)

Description

destroy(element) removes and destroys the architecture model element element.

Examples

Destroy Component

Create a component named 'NewComponent' then remove it from the model.

model = systemcomposer.createModel('newModel',true);
rootArch = get(model,'Architecture');
newComponent = addComponent(rootArch,'NewComponent');
destroy(newComponent)

Input Arguments

element — Architecture model element

component object | variant component object | component port object | architecture port object | connector object | signal interface object | signal element object | property object | view object | element group object

Architecture model element, specified as one of these objects:

• systemcomposer.arch.Component

• systemcomposer.arch.VariantComponent

• systemcomposer.arch.ComponentPort

• systemcomposer.arch.ArchitecturePort

• systemcomposer.arch.Connector

• systemcomposer.interface.SignalInterface

• systemcomposer.interface.SignalElement

• systemcomposer.profile.Property

• systemcomposer.view.View

• systemcomposer.view.ElementGroup

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. You can represent specific architectures using alternate views.	Different types of architectures describe different aspects of systems: Functional architecture describes the flow of data in a system. Logical architecture describes the intended operation of a system. Physical architecture describes the platform or hardware in a system.	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: Extract the root level architecture contained in the model. Apply profiles. Link interface data dictionaries. Generate instances from model architecture. System Composer models are stored as .slx files.	Create an Architecture Model
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: 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
interface	An interface defines the kind of information that 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.	Define Interfaces
interface element	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: Pins or wires in a connector or harness. Messages transmitted across a bus. Data structures shared between components.	Assign Interfaces to Ports
interface dictionary	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 .sldd files.	Save, Link, and Delete Interfaces Reference Data Dictionaries
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.	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 conversion UnitDelay to break an algebraic loop. Apply an interface conversion RateTransition to reconcile different sample time rates for reference models.	Interface Adapter

Term	Definition	Application	More Information
stereotype	A stereotype is a custom extension of the modeling language. Stereotypes provide a mechanism to extend the architecture language elements by adding domain-specific metadata.	Apply stereotypes to the root level architecture, component architecture, connectors, ports, and interfaces of a model. Stereotypes provide model elements within the architecture a common set of property fields, such as mass, cost, and power.	Define Profiles and Stereotypes
profile	A profile is a package of stereotypes to create a self-consistent domain of model element types.	Apply profiles to a model through the Profile Editor. You can store stereotypes for a project in one profile or in several. Profiles are stored in .xml files when they are saved.	Use Stereotypes and Profiles
property	A property is a field in a stereotype. For each model element the stereotype is applied to, specific property values are specified.	Use properties to store quantitative characteristics, such as weight or speed, that are associated with a model element. Properties can also be descriptive or represent a status.	Set Properties

Term	Definition	Application	More Information
view	A view shows a customizable subset of elements in a model. Views can be filtered based on stereotypes or names of components, ports, and interfaces, along with the name, type, or units of an interface element. Construct views by pulling in elements manually. Views create a simplified way to work with complex architectures by focusing on certain parts of the architecture design.	You can use different types of views to represent the system: Operational views demonstrate how a system will be used and should be well integrated with requirements analysis. Functional views focus on what the system must do to operate. Physical views show how the system is constructed and configured. A viewpoint represents a stakeholder perspective that specifies the contents of the view.	Create Architecture Views Interactively Modeling System Architecture of Keyless Entry System
element group	An element group is a grouping of components in a view.	Use element groups to programmatically populate a view.	Create Architectural Views Programmatically
query	A query is a specification that describes certain constraints or criteria to be satisfied by model elements.	Use queries to search elements with constraint criteria and to filter views.	Find Elements in a Model Using Queries

.