System to Sub System transition add-on enables automated and iterative transition between system and subsystems.
System to Sub System transitions are top-down and iterative: any change performed in the original System can be propagated at any moment to the Sub System.
Traceability between System and Sub System is ensured through a mechanism based on system-wide ID’s.
The objective of this transition is to extract a subset of the Physical or Logical Architecture and populate a new model with this subset.
Configuration Items and Nodes :
Behaviour components :
The transformation algorithm performs the following steps:
Recommandations
Selecting both Node and Behavior PCs as the Subsystem is not recommended.
However if you do so, deploying nodes and merging rules will be applied for all deployed Behavioral PCs
The objective of this transition is to re-apply the methodology starting from one or several given Configuration Item(s).
Configuration Items and Nodes :
Behaviour components :
The transformation algorithm performs the following steps:
Recommandations
Selecting both Node and Behavior PCs as the Subsystem is not recommended.
However if you do so, deploying nodes and merging rules will be applied for all deployed Behavioral PCs
The principle of the transition is to select one or more Node Physical Component from a source model and generate (or update) a target model whose system of interest will be the selection.
The transition will automatically create the target model and fill its three phases (System Analysis, Logical Architecture and Physical Architecture) with new Capella objects linked to the objects of the source model: