Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.085 Create or update functional chains at logical level
SM-4715
-
Modify methodology of ARCH.085
Finished
Goal | Refine the functional chains with decomposed logical function definitions |
---|---|
Requirements met by this process step | ISO 15288 6.4.4.3 c) 4 |
Inputs | AMOD-082 Logical functional chain definition AMOD-081 Logical functional flow definition (single system capability realisation) |
Outputs | |
Methodology | Top-down: The viewpoint AMOD-082 Logical functional chain definition was initially created in step ARCH.084 after the functional chain was transferred from system level. Within step ARCH.182 the functions are further decomposed so the initially created logical functional chains must be updated, so that the newly created functions of interest and functions which provide information are now respresented in AMOD-082 Logical functional chain definition. Do the following modifications on AMOD-082: If involved functions were decomposed during ARCH.182 Replace the function involvements on the functional chain such that only leaf-level functions are involved end if If the logic of the functional chain has changed because of alterations to arising from decomposition in ARCH.182 update the logic of the functional chain so that it is consistent with the rest of the model end if Bottom-up: If there are already logical functions that exist in the model from previous activities that happened before the ARCH process was fully introduced, the sequential order of these functions can be described in a function chain. The functional chain should be located underneath an assumed corresponding capability realisation. However, it is important that the functions used in this chain are merged with the top-down functions in process step ARCH.182. The same should happen with the functional chain in this step. So that at the end of this process step, the top down and bottom up functions produce a common result in a combined functional chain. |
Tools and non-human resources | Team for Capella |
Cardinality | Once per capability realisation |
Completion criteria | The output views conform to their modelling rules |
Design review | ARCH.R.5 Logical capability review |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None identified |
SM-4715
-
Modify methodology of ARCH.085
Finished
Goal | Refine the functional chains with decomposed logical function definitions |
---|---|
Requirements met by this process step | ISO 15288 6.4.4.3 c) 4 |
Inputs | AMOD-082 Logical functional chain definition AMOD-081 Logical functional flow definition (single system capability realisation) |
Outputs | |
Methodology | Top-down: The viewpoint AMOD-082 Logical functional chain definition was initially created in step ARCH.084 after the functional chain was transferred from system level. Within step ARCH.182 the functions are further decomposed so the initially created logical functional chains must be updated, so that the newly created functions of interest and functions which provide information are now respresented in AMOD-082 Logical functional chain definition. Do the following modifications on AMOD-082: If involved functions were decomposed during ARCH.182 Replace the function involvements on the functional chain such that only leaf-level functions are involved end if If the logic of the functional chain has changed because of alterations to arising from decomposition in ARCH.182 update the logic of the functional chain so that it is consistent with the rest of the model end if Bottom-up: If there are already logical functions that exist in the model from previous activities that happened before the ARCH process was fully introduced, the sequential order of these functions can be described in a function chain. The functional chain should be located underneath an assumed corresponding capability realisation. However, it is important that the functions used in this chain are merged with the top-down functions in process step ARCH.182. The same should happen with the functional chain in this step. So that at the end of this process step, the top down and bottom up functions produce a common result in a combined functional chain. |
Tools and non-human resources | Team for Capella |
Cardinality | Once per capability realisation |
Completion criteria | The output views conform to their modelling rules |
Design review | ARCH.R.5 Logical capability review |
Step done by (Responsible) | System architect |
Provides input to/assists (Contributes) | Inclusive OR:
|
Uses outputs (Informed) | None identified |