Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.R.5 Logical capability review
This is not finished, please do not use it at the moment.
RCAMT-306
-
Define criteria for review ARCH.R.5
Paused
ARCH graphml version
This Confluence page has been fulfilled thanks to the version of ARCH graphml delivered on the
1. AREV-5.1 Artefacts list
Scope of compliance | Artefact | SS1 | Identities of views created | Modelling rules compliance ![]() ![]() | Notes (last update before Review) | Review |
---|---|---|---|---|---|---|
full | AMOD.025 Abstract concepts | updated |
| |||
capability-based | AMOD-081 Logical functional flow definition (single system capability realisation) | initial | Updated by ARCH.085, | |||
capability-based | AMOD-082 Logical functional chain definition | initial | Updated by ARCH.085, | |||
capability-based | AMOD-084 Logical exchange scenario definition | initial | ||||
capability-based | AMOD.091 Logical data objects [LCDB] | initial | ||||
full | AMOD.092 Logical exchanges items [LCDB] | initial | ||||
-- | deliverable arch.107 | initial | ARCH task still on development, ticket RCAMT-265 created in order to finish this page once the step is validated | |||
-- | deliverable arch.108 | initial | ARCH task still on development, ticket RCAMT-266 created in order to finish this page once the step is validated | |||
full | AMOD-125 Logical architecture definition | updated | Updated by ARCH.181, | |||
full | AMOD-126 Logical level - system level traceability report | initial | ||||
capability-based | AMOD.147 Logical capability realization | initial |
2. AREV-5.2 Review criteria
2.1. Activity & viewpoint completion
ID Prefix AREV-5.2.1.x | EN 50126 phase | Activity | Tickets | Viewpoint output | Scope of compliance | Notes | Remarks by Reviewer |
---|---|---|---|---|---|---|---|
020 | SS1 | ARCH.182 Split the system functions | AMOD.081 | capability-based | |||
030 | SS1 | ARCH.085 Create or update functional chains at logical level | AMOD.082 (updated arch.085) | capability-based | |||
040 | AMOD.081 (updated arch.085) | capability-based | |||||
050 | S4 | ARCH.087 Model data flowing between logical functions | AMOD.091 | capability-based | |||
060 | AMOD.092 | full | |||||
070 | AMOD.025 | full | |||||
100 | SS1 | ARCH.191 Refine capability realisations for the logical architecture | AMOD.147 | capability-based | |||
110 | SS1 | AMOD-125 | |||||
130 | SS1 | ARCH.181 Reconcile candidate logical components | AMOD-125 (updated arch.181) | capability-based | |||
140 | SS1 | ARCH.107 Apportion non-functional requirements to logical functions | will be updated on later iteration | ? | ARCH task still on development, ticket RCAMT-265 created in order to finish this page once the step is validated | ||
150 | SS1 | ARCH.108 Define acceptance criteria for non-functional requirements | 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; will be updated on later iteration | full | ARCH task still on development, ticket RCAMT-266 created in order to finish this page once the step is validated |
2.2. Content criteria
ID Prefix AREV-5.2.2.x | EN 50126 phase - initial | EN 50126 phase - final update | Content criterion | Evidence | Achieved
| Required review role | Reviewer identity | Reviewer commentary | Blocking corrective action | Non-blocking corrective action |
---|---|---|---|---|---|---|---|---|---|---|
010 | O1 | SS1 | Abstract concepts defined for the operational capability under review are safe enough to try | AMOD.025 | Design authority | |||||
020 | SS1 | SS3 | The splitted functions meet the categorisation, the abstraction layer decomposition and the safety criticality criterias The functional exchanges and exchanges items between the leaf-functions are well defined and consistent to be safe enough to try | AMOD-081 | Design authority | |||||
050 | S4 | SS1 | The set of logical functionals flows needed to achieve all or part of a system capability realisation is self enough to try | AMOD-082 | Design authority | |||||
080 | SS1 | SS3 | The interactions between logical components needed to achieve a given system capability are adequately highlighted to be safe enough to try | AMOD-084 | Design authority | |||||
100 | S4 | SS1 | Data types supporting the logical level data are adequately defined to be safe enough to try. | AMOD.091 | Design authority | |||||
110 | S4 | SS1 | Exchange item definitions and supporting logical level data are safe enough to try | AMOD.092 | Design authority | |||||
120 | SS1 | ? | Non functional requirement defined for the system capability under review are safe enough to try. | deliverable arch.107 | Design authority | |||||
130 | SS1 | ? | Acceptance criteria for non functional requirement, defined for the system capability under review are safe enough to try. | deliverable arch.108 | Design authority | |||||
140 | S4 | SS1 | The functional allocations to logical components / actors are consistent and safe enough to try | AMOD-125 | Design authority | |||||
160 | SS1 | SS3 | The traceability between model elements at logical level and model elements at system level is full and consistent. | AMOD-126 | Design authority | |||||
170 | SS1 | SS1 | System capabilities resulting from logical decomposition of system and functions are weel refined and safe enough to try the scenarios for first logical simulations | AMOD.147 | Design authority | |||||