Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.049 Define set of potential system capabilities/missions
Goal | Define a set of potential system capabilities/missions and rationales for their creation. |
---|---|
Requirements met by this process step | None defined |
Inputs | AMOD-021 Operational capabilities definition AMOD-012 System lifecycle model AMOD-035 Operational business process with risk control measures Operational concepts or system capabilities from collaborative projects |
Outputs | AMOD-120 Record of system capabilities and missions |
Methodology | The decision to define a potential system capability or mission should be made on the basis of the criteria explained in ARCH.M.040 Method for definition of capabilities. Document the decision and rationale for each capability in AMOD-120 Record of system capabilities and missions. |
Tools and non-human resources | Team for Capella + Proposal: Confluence or Excel for creation of AMOD-120 Record of system capabilities and missions. |
Cardinality | One-off with revisions permitted |
Completion criteria | The output view contains a valid decision and rationale for each operational capability in the model. |
Design review | |
Step done by (Responsible) | Lead System architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None directly |