Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.168 Consolidate the overall reference architecture
RCAMT-358
-
Create Confluence page for activity definition ARCH.168
BACKLOG
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 | cite requirements from standards and legislation (by standard/document number and paragraph number only, no complete copy and paste) |
Inputs | AMOD-095 Location kind definitions AMOD-097 Computation asset structure AMOD-093 Subsystem architecture definition AMOD-085 Subsystem architecture definition (single realised capability) |
Outputs | |
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. WIP Lorenzo Grenier Elsa Lamblin [X] Warning: duplicates need to be merged manually (functions, subsystems seen as external actors depending on the scope). Rules to delete redundant elements are created here: Recommendation rules for redundant elements after fusion |
Tools and non-human resources | Team for Capella |
Cardinality | At least once prior to ARCH.R.8 Physical review - consolidated |
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 | ARCH.R.8 Physical review - consolidated |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None |