Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.191 Refine capability realisations for the logical architecture
Goal | Capture any refinements/adjustments to system capabilities after splits are done at logical level |
---|---|
Requirements met by this process step | ISO 15288 6.4.3.3 d) 2) EN 50126 7.6.2 |
Inputs | |
Outputs | AMOD-147 Logical capability realisation |
Methodology | For the most part, the system capabilities are not expected to change when transferred down to logical architecture level. However, the "logical capability realisations" still need to be shown on a dedicated viewpoint for at least two reasons:
Some example conditions (non-exhaustive) under which it may be appropriate to refine the system capabilities can be found in ARCH.M.040 Method for definition of capabilities. Important The amount of refinement of capability realisations at logical level should be kept to the minimum necessary, because each new capability realisation creates new work to do in verification and validation. Further refinement will be allowed at subsystem level - see ARCH.192 Refine capability realisations for the subsystem architecture |
Tools and non-human resources | Team for Capella |
Cardinality | Once per package of system capabilities being delivered |
Completion criteria | The output view conforms to its modelling rules. |
Design review | |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | IVV role TBD
|