Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.108 Define acceptance criteria for non-functional requirements
Goal | high-level statement of the engineering objective being addressed, including reference to standards/legislation if that is relevant |
---|---|
Requirements met by this process step | EN 50126-1 7.6.1 |
Inputs | list of all input information needed for this process step to be carried out; for model views, add a hyperlink to the model view description; documents, published info, websites, knowledge from particular roles are all admissible. |
Outputs | list of all output artefacts this process should produce; for model views, add a hyperlink to the model view description; for documents, add a link to the document template or to the document publication area if it is directly generated from Confluence; |
Methodology | Only a summary of an initial investigation:
|
Tools and non-human resources | Capella for Teams |
Cardinality | state how many times this process step is expected to be carried out - e.g.
etc. |
Completion criteria | state the conditions that must be TRUE before this process step can be considered complete. These should be inserted in the Acceptance Criteria of a Jira ticket for this process step to be done. |
Design review | Link to the corresponding design review where the completion of this activity is evaluated. |
Step done by (Responsible) | Identify the role that is responsible for organising this process step and producing the output; This is the Assignee in Jira. |
Provides input to/assists (Contributes) | Identify the roles that assist in the work or provide input information |
Uses outputs (Informed) | Identify the roles and/or process areas that make use of this information outside of the ARCH process area; |