Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.107 Apportion non-functional requirements to logical functions
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 | AMOD-082 Logical functional chain definition AMOD-081 Logical functional flow definition (single system capability realisation) AMOD-091 Logical data objects [L.CDB] AMOD-092 Logical exchange items [L.CDB] AMOD-083 State-based behaviour definition (logical function) |
Outputs | None. |
Methodology | state the methodology as a list of instructions; this information forms the Description field of a ticket for this process to be done, so it must be sufficient for someone to follow the process, even if they have not done it before. |
Tools and non-human resources | Team for Capella |
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; |