Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.083 Agree the system requirements with stakeholders
RCAMT-395
-
Populate Confluence page for activity definition: ARCH.083 Agree the system requirements with stakeholders
Finished
Goal | Finalise a system requirements baseline |
---|---|
Requirements met by this process step | ISO 15288 6.4.3.3 d) 1 |
Inputs | AMOD-146 System needs and constraints tradeoff decision record |
Outputs | AMOD-079 Agreed system requirements baseline (functional + non functional) |
Methodology | Background: This process step ensures for a particular version of the whole set of system requirements (which could include multiple architectural decisions) that it is acceptable to stakeholders. This reduces the risk that the delivered system does not meet stakeholder needs. Main steps: Using model exports as references to interpret and validate the requirements, the stakeholders will be able to agree or disagree with solutions selected in AMOD-146 System needs and constraints tradeoff decision record. Steps are:
Note: stakeholder set here is the wider business plus regulators. The principle should be that the whole system is signed off by the sponsors here, but that they should not need to be consulted much during subsequent phases because the system boundary and scope is now established. |
Tools and non-human resources | Confluence-based templates & scripts for presenting AMOD-079 Team for Capella |
Cardinality | Once per system requirements roadmap milestone (e.g. particular releases, particular versions, baselines, etc.) |
Completion criteria | All stakeholders agreed with the requirements baseline |
Design review | ARCH.R.4 System review - consolidated |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
Note: not all stakeholders are equal; where there are disagreements, some stakeholders may be empowered by their position in the organization to make an executive decision or a tradeoff between business needs and then impose to prioritise one stakeholder need over another. |
Uses outputs (Informed) | IVV Manager, GEN roles (TBD) |