Legal information

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 complianceArtefactSS1Identities of views createdModelling rules compliance (tick)/(error)

Notes (last update before Review)

Review
fullAMOD.025 Abstract conceptsupdated

                                            



capability-basedAMOD-081 Logical functional flow definition (single system capability realisation) initial

Updated by ARCH.085,
capability-basedAMOD-082 Logical functional chain definitioninitial

Updated by ARCH.085,
capability-basedAMOD-084 Logical exchange scenario definitioninitial



capability-basedAMOD.091 Logical data objects [LCDB]initial



fullAMOD.092 Logical exchanges items [LCDB]initial



--deliverable arch.107initial

ARCH task still on development, ticket RCAMT-265 created in order to finish this page once the step is validated
--deliverable arch.108initial

ARCH task still on development, ticket RCAMT-266 created in order to finish this page once the step is validated
fullAMOD-125 Logical architecture definitionupdated

Updated by ARCH.181,
fullAMOD-126 Logical level - system level traceability reportinitial



capability-basedAMOD.147 Logical capability realizationinitial





2. AREV-5.2 Review criteria

2.1. Activity & viewpoint completion

ID

Prefix AREV-5.2.1.x

EN 50126 phaseActivityTicketsViewpoint output

Scope of compliance

NotesRemarks by Reviewer
020SS1ARCH.182 Split the system functions
AMOD.081capability-based

030SS1ARCH.085 Create or update functional chains at logical level
AMOD.082 (updated arch.085)capability-based

040
AMOD.081 (updated arch.085)capability-based

050S4

ARCH.087 Model data flowing between logical functions
AMOD.091capability-based

060
AMOD.092full

070
AMOD.025full

100SS1ARCH.191 Refine capability realisations for the logical architecture
AMOD.147capability-based



110SS1

ARCH.180 Define logical component candidates


AMOD-125


130SS1ARCH.181 Reconcile candidate logical components
AMOD-125 (updated arch.181)capability-based

140SS1ARCH.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


150SS1ARCH.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 - initialEN 50126 phase - final updateContent criterionEvidence

Achieved 

(tick)/(error)

Required review roleReviewer identityReviewer commentaryBlocking corrective actionNon-blocking corrective action
010O1SS1Abstract concepts defined for the operational capability under review are safe enough to tryAMOD.025 
Design authority



020SS1SS3

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



050S4SS1The set of logical functionals flows needed to achieve all or part of a system capability realisation is self enough to tryAMOD-082 
Design authority



080SS1SS3The interactions between logical components needed to achieve a given system capability are adequately highlighted to be safe enough to tryAMOD-084 
Design authority



100S4SS1Data types supporting the logical level data are adequately defined to be safe enough to try.AMOD.091
Design authority



110S4SS1Exchange item definitions and supporting logical level data are safe enough to tryAMOD.092
Design authority



120SS1?Non functional requirement defined for the system capability under review are safe enough to try.deliverable arch.107
Design authority



130SS1?Acceptance criteria for non functional requirement, defined for the system capability under review are safe enough to try.deliverable arch.108
Design authority



140S4SS1The functional allocations to logical components / actors are consistent and safe enough to tryAMOD-125
Design authority



160SS1SS3The traceability between model elements at logical level and model elements at system level is full and consistent.AMOD-126 
Design authority



170SS1SS1System capabilities resulting from logical decomposition of system and functions are weel refined and safe enough to try the scenarios for first logical simulationsAMOD.147 
Design authority