Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.005 Define set of system of interest lifecycle variants
Goal | Achieve and document a shared understanding of the system's possible lifecycles. |
---|---|
Requirements met by this process step | ISO 15288 6.4.1.3 c 1) |
Inputs | Briefing material from around the business Knowledge of contributors |
Outputs | AMOD-012 System lifecycle model |
Methodology | Two aspects are to be examined:
In theory these aspects can be modelled together, but it may be simpler to separate them if possible. From the business briefing materials, a proposed states model should be created. This should then be reviewed with contributors and adjusted according to their knowledge. The results should be drawn up into one or more Capella state diagrams. |
Tools and non-human resources | Team for Capella |
Cardinality | One-off, with possible revisions later |
Completion criteria | Contributors & reviewers agree the lifecycle model(s) are safe enough to try. All review feedback has been addressed. |
Design review | ARCH.R.2 Operational review - consolidated |
Step done by (Responsible) | Operational concept architect |
Provides input to/assists (Contributes) | External stakeholders concerned with system lifecycle activities |
Uses outputs (Informed) | All activities where system capabilities or functions are defined, i.e. |