Iterative Transitions Between Engineering Phases

Overview

An automated transition should not always include all modeling elements from a phase to a lower phase.

To offer flexibility to the user and to allow performing transition of specific parts from a phase into a lower phase, modeling concepts have been categorized into activities, which are:

An activity is (of course) linked to others activities but categorizing modelling elements into these activities defines entry points for the user to trigger the automated transition.

Transition Entry Points

This section provides a simplified version of transition graph for each entry points to trigger transition and determines scope of transition for these entry points.

Data Transition

The transition is available at:

The involved element types are:



The transition tool performed on data should follow this sub-graph:

All data contained into a package is transitioned into the targeted phase.

Exchange Item Transition

The involved element types are:

Data types defined in a phase can be used in a lower phase. According to user preference, perform a transition of Exchange items can also trigger a transition of related datatypes. If a related datatype is not transitioned, exchange item will be linked to the data type from the upper phase.

State Machine Transition

The involved element types are:

According to user preference, perform a transition of Components can also trigger a transition of related State Machines.

Interface Transition

The transition is available at:

The involved element types are:

Exchange items defined in a phase can be used in a lower phase. According to user preference, perform a transition of Interface can also trigger a transition of allocated exchange items. If an allocated exchange item is not transitioned, interface will allocate the exchange item from the upper phase.

According to user preference, perform a transition of Interface can also trigger a transition of ports.

Operational Activity Transition

The transition is available at:

The involved element types are:

State/Modes are owned by Components and can’t be used between phases. Perform a Functional Transition without having triggered a State Machine transition will lose links between functions and defined state modes. After having transitioned state machine, a new functional transition will set missing links to mode/states into transitioned functions.

Exchange items defined in a phase can be used in a lower phase. According to user preference, perform a transition of Operational activities can also trigger a transition of convoyed exchange items. If a convoyed exchange item of functional exchanges is not transitioned, functional exchanges will convey exchange item from the upper phase.

Operational Entity Transition

The transition is available at:

The involved element types are:

An operational entity can be transitioned to an Actor or to the System.

While transition of an operational entity, if an allocated operational activity or an allocated interaction has not yet been transitioned, the transition tool triggers a transition of the given element.

Operational Capability Transition

An operational capability can be transitioned to a capability or a mission.

Functional Transition

The transition is available at:

The involved element types are:



State/Modes are owned by Components and can’t be used between phases. Perform a Functional Transition without having triggered a State Machine transition will lose links between functions and defined state modes. After having transitioned state machine, a new functional transition will set missing links to mode/states into transitioned functions.

Exchange items defined in a phase can be used in a lower phase. According to user preference, perform a transition of Functions can also trigger a transition of convoyed exchange items. If a convoyed exchange item of functional exchanges or function ports is not transitioned, functional exchanges or function ports will convey exchange item from the upper phase.

Actor Transition

The transition is available at:

State/Modes are owned by Components and cannot be used between phases. Perform an Actor Transition without having triggered a State Machine transition will lose links between actors and defined state modes. After having transitioned state machine, a new functional transition will set missing links to mode/states into transitioned functions.

Exchange items defined in a phase can be used in a lower phase. According to user preference, perform a transition of actors can also trigger a transition of related exchange items. If a related exchange item is not transitioned, actors will convey exchange item from the upper phase.

Interfaces defined in a phase can be used in a lower phase. According to user preference, perform a transition of interfaces can also trigger a transition of related exchange items. If a related exchange item is not transitioned, interface will allocate exchange item from the upper phase.

If a related function or a functional exchange has not yet been transitioned, the transition tool triggers a transition of the given element.

In the Logical Architecture to Physical Architecture transition, connections between actors and internal system components should not be transitioned if component is not transitioned.

Logical Component to Physical Component Transition

The transition is available at:

The involved element types are:

Two kind of transition should be available: Breakdown Strategy and Leaf Strategy

Breakdown Strategy

Propagate the logical component breakdown in physical architecture

Leaf Strategy

Propagate only leaf logical components in physical architecture (this strategy seems inconsistent with a system modelling allowing reuse of component through parts).

State/Modes are owned by Components and can’t be used between phases. Perform a Component Transition without having triggered a State Machine transition will lose links between components and defined state modes.

Exchange items defined in a phase can be used in a lower phase. According to user preference, perform a transition of components can also trigger a transition of related exchange items. If a related exchange item is not transitioned, components will convey exchange item from the upper phase.

Interfaces defined in a phase can be used in a lower phase. According to user preference, perform a transition of interfaces can also trigger a transition of related exchange items. If a related exchange item is not transitioned, interface will allocate exchange item from the upper phase.

If a related function or a functional exchange has not yet been transitioned, the transition tool triggers a transition of the given element.

See the Capella preferences for choosing the strategy of Logical to Physical Components transition.

According to user preference, perform a transition of components to physical architecture can also trigger a transition of related interfaces at system (i.e. context) and logical level.

Port Transition

According to user preference, perform a transition of ports can result of STANDARD ports instead of default FLOW ports.