Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
Process step descriptions
- ARCH.900 Determine the operational needs
- ARCH.901 Capture existing and initial operational understanding
- ARCH.001 Define boundary of wider system of interest (operating entity of system of interest)
- ARCH.004 Analyse trade space factors
- ARCH.005 Define set of system of interest lifecycle variants
- ARCH.002 Create initial set of operational capabilities
- ARCH.144 Define enterprise goals
- ARCH.003 Create initial set of operational actors & operational entities
- ARCH.006 Create initial set of operational states for operational entities/actors
- ARCH.007 Create set of initial operational activities
- ARCH.008 Define abstract concepts relevant to the wider system of interest
- ARCH.009 Define measures of effectiveness
- ARCH.902 Analyse the operational capabilities to determine detailed operational needs
- ARCH.177 Complete the definition of the operational capability of interest
- ARCH.078 Create bare business operational scenario
- ARCH.079 Create bare business operational process
- ARCH.080 Model operational activities and interactions
- ARCH.153 Model data flowing between operational activities
- ARCH.159 Model operational states
- ARCH.903 Assess & mitigate the operational risks
- ARCH.171 Prepare business risk analysis
- ARCH.172 Prepare security risk analysis
- ARCH.173 Prepare safety risk analysis
- ARCH.020 Identify & classify operational deviations
- ARCH.011 Assess operational performance risks of scenario
- ARCH.017 Assess security risks of scenario
- ARCH.024 Assess operational safety risks of scenario
- ARCH.029 Allocate risk control responsibilities (op. activity to op. entity/actor)
- ARCH.175 Produce consolidated operational deviation analysis report
- ARCH.904 Incorporate risk control measures in the operational needs
- ARCH.905 Consolidate the operational needs
- ARCH.901 Capture existing and initial operational understanding
- ARCH.910 Determine the system requirements
- ARCH.911 Identify the system's contribution to the operational needs
- ARCH.035 Identify constraints on the system solution
- ARCH.043 Define set of potential system actors
- ARCH.049 Define set of potential system capabilities/missions
- ARCH.039 Define set of potential system and actor functions
- ARCH.036 Identify all alternative system boundaries
- ARCH.042 Select system boundary (or set of variants)
- ARCH.912 Finalise the system context and constraints
- ARCH.048 Identify system implementation constraints
- ARCH.045 Define complete set of system-level actors
- ARCH.119 Define consolidated set of system capabilities/missions
- ARCH.041 Transfer or trace upper level model elements to system level
- ARCH.044 Define requirements from non-actor stakeholders
- ARCH.051 Align the system context with collaboration projects
- ARCH.913 Analyse the system capabilities to determine detailed system needs
- ARCH.179 Complete the definition of the system capability of interest
- ARCH.088 Define system functions and functional exchanges
- ARCH.052 Create initial system exchange scenarios
- ARCH.053 Create initial system functional chains
- ARCH.054 Model data flowing between system functions
- ARCH.055 Model system and actor states
- ARCH.158 Model external system interface
- ARCH.058 Define measures of performance
- ARCH.915 Assess & mitigate the risks of system failure
- ARCH.916 Incorporate risk control measures in the system needs
- ARCH.917 Finalise the system requirements
- ARCH.152 Consolidate system functionality
- ARCH.157 Consolidate system data
- ARCH.081 Update constraints on system solution
- ARCH.109 Consolidate traceability between model elements at system level and model elements at operational level
- ARCH.082 Trade off system requirements and constraints
- ARCH.083 Agree the system requirements with stakeholders
- ARCH.911 Identify the system's contribution to the operational needs
- ARCH.920 Define the logical architecture
- ARCH.921 Decompose system functionality
- ARCH.922 Define logical components
- ARCH.923 Apportion the non-functional requirements
- ARCH.924 Finalise the logical architecture
- ARCH.154 Consolidate logical functional flow
- ARCH.096 Allocate logical functions to logical components (including alternative allocations)
- ARCH.086 Create or update exchange scenarios at logical level
- ARCH.110 Consolidate traceability between model elements at logical level and model elements at system level
- ARCH.190 Consolidate logical data
- ARCH.099 Define behaviour for logical functions
- ARCH.930 Define the physical architecture
- ARCH.932 Define the subsystem boundaries
- ARCH.090 Identify alternative subsystem options
- ARCH.118 Identify implementation constraints on the subsystem solution
- ARCH.097 Evaluate subsystem boundary options against the architectural tradeoff criteria
- ARCH.111 Execute automatic transition of logical elements to physical level
- ARCH.098 Define selected subsystem option
- ARCH.117 Align the subsystems with collaborative project
- ARCH.933 Define the subsystem interfaces
- ARCH.156 Define single inter-subsystem interface
- ARCH.151 Refine system interface to subsystem interface to actor
- ARCH.114 Define single interface layer
- ARCH.128 Define functions of single interface layer
- ARCH.129 Model data flowing between interface layer functions
- ARCH.130 Define interface layer exchange scenarios
- ARCH.122 Define behaviour for interface layer functions
- ARCH.934 Define supporting physical architecture
- ARCH.935 Finalise the subsystem architecture
- ARCH.936 Assess risks associated with subsystem architecture
- ARCH.101 Carry out failure modes, effects and criticality analysis (FMECA)
- ARCH.103 Identify new functions needed for robustness to failures
- ARCH.104 Identify new non-functional requirements needed for robustness to failures
- ARCH.105 Identify new non-functional requirements needed to mitigate hazards introduced by architecture choice
- ARCH.106 Identify new functions needed for mitigating hazards introduced by architecture choice
- ARCH.135 Carry out HAZID on tenderable elements
- ARCH.937 Allocation/Derivation of NFRs
- ARCH.938 Consolidate the overall architecture
- ARCH.136 Push back chosen physical architecture from child models to parent model
- ARCH.169 Consolidate traceability between model elements at physical level and model elements at logical level
- ARCH.168 Consolidate the overall reference architecture
- ARCH.100 Obtain stakeholder acceptance of preferred architecture
- ARCH.932 Define the subsystem boundaries
- ARCH.925 Transition from LA parent model to SA child models