Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.044 Define requirements from non-actor stakeholders
SM-2780
-
Populate Confluence page for activity definition: ARCH.044 Define requirements from non-actor stakeholders
Finished
Goal | Ensure all the requirements are captured early |
---|---|
Requirements met by this process step | ISO 15288 6.4.2.3 b 2)-4), d 2)-3), e 2)-4) |
Inputs | |
Outputs | |
Methodology | Non-actor stakeholder candidates are identified in AMOD-022 Enterprise & environment definition. Operational entities in the "wider environment" and possibly also in the "environment" boundaries could be non-actor stakeholders with needs that could influence the development of the system. Two main stages to this step:
|
Tools and non-human resources | Team for Capella |
Cardinality | Theoretically one-off with revisions allowed; practically, may need to be done in several batches, divided by stakeholder or stakeholder group. |
Completion criteria | The set of non-actor stakeholders was identified. The set of non-actor stakeholders that was consulted was sufficient to give confidence that risk of undiscovered requirements is as low as practicable. The capture of requirements from each stakeholder set is sufficiently thorough. Conflicts in the requirements arising from different stakeholders have been resolved. |
Design review | |
Step done by (Responsible) | new role Stakeholder manager/Business development manager Lead system architect |
Provides input to/assists (Contributes) | System architect Workshop facilitator |
Uses outputs (Informed) | None directly |