Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.182 Split the system functions
Goal | Each system function of interest has been split according to defined splitting principles and met a required level of detail into for the logical architecture. |
---|---|
Requirements met by this process step | ISO 15288 6.4.4.3 c) |
Inputs | |
Outputs | AMOD-081 Logical functional flow definition (single system capability realisation) |
Methodology | The logical level of the architecture is concerned with abstract partitioning of functionality. Therefore, when we split functions at logical level, we can only do this on the basis of some logical or abstract splitting principle.
Note: if there exist already logical functions in the model, this functions shall be reconciled with the transferred system functions or with the new leaf level logical functions as part of this process step. So that at the end only one set of consistent logical functions exists which are traced to system functions. Note: during consolidation in ARCH.154, the function that has been transferred to logical layer and split into logical functions will be deleted. |
Tools and non-human resources | Team for Capella |
Cardinality | Once per functional chain of interest. |
Completion criteria | The output view complies with its modelling rules. The content of the output view represents the team's current understanding of the way these system functions should be decomposed in the logical architecture layer. |
Design review | |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | RAMS manager RAMS engineer Verification & validation manager |