Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.042 Select system boundary (or set of variants)
Goal | Determine the functional scope of the system |
---|---|
Requirements met by this process step | ISO 15288 6.4.3.3 a 1), 6.4.1.3 d), 6.4.4.3 c) 1 |
Inputs | AMOD-041 System boundary options |
Outputs | |
Methodology | Trade-off methods should be used to determine the optimal alternative for each of the choices of system scope that exist. A range of trade-off methods is documented here: ARCH.M.140 Method for tradeoff decisions The DAR method is recommended and the template for AMOD-046 Selected system boundary tradeoff record is constructed on this basis. The criteria for the assessment of the options should be derived from the trade space assessment and/or the system implementation constraints (both of which can be interpreted as quality factors that the system boundary options will achieve to varying degrees). It should be possible to reuse criteria for multiple decisions. |
Tools and non-human resources | Technique-dependent |
Cardinality | Once per individual system boundary decision |
Completion criteria | The selected system boundary definitions are safe enough to try. |
Design review | ARCH.R.4 System review - consolidated |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None |