• RCA ARCH Release Information
  • Modelling Rules for Capella Analysis Model (CapStan)
    • 1. Modelling Rules for Operational Analysis
    • 2. Modelling Rules for System Analysis
    • 3. Modelling Rules for Logical Architecture
    • 4. Modelling Rules for Physical Architecture
    • 5. Modelling Rules for Data
    • 6. Modelling Rules for Traceability
    • 7. Modelling Rules for Non-Functional Requirements
    • 8. Modelling Rules for Risk Model
    • 9. Modelling Rules for Interfaces to Simulation Tools
  • Methods for ARCH
    • ARCH.M.010 Method for definition of functionality
      • Technical note on definition of functions
      • Method for definition of functions
      • Method for definition of operational activities
      • Method for decomposition of functions
      • Set of examples for definition and decomposition of functions
    • ARCH.M.020 Method for definition of behaviour
      • Method for definition of actions
      • Method for definition of behavioural constraints
      • Method for definition of functional chains
      • Method for definition of lookup tables
      • Method for definition of scenarios
      • Method for definition of state machines
      • Method for definition of truth tables
    • ARCH.M.030 Method for definition of interfaces
      • Method for definition of system interfaces
      • Method for definition of subsystem interfaces
    • ARCH.M.040 Method for definition of capabilities
    • ARCH.M.050 Method for definition of data model
      • Method for definition of data model
      • Best practices to maintain a consistent data model
      • Data modelling with capella (what is possible)
    • ARCH.M.060 Method for the execution of automatic transition in capella
    • ARCH.M.070 Method for definition of architectural elements
      • Method for definition of logical components
  • ARCH - Problem definition & architectural design process area
    • 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.012 Determine measure of effectiveness target values
            • ARCH.013 Identify risks to business effectiveness (business loss-risk mapping)
          • ARCH.172 Prepare security risk analysis
            • ARCH.018 Identify internal & external issues affecting successful security
            • ARCH.019 Determine need for information availability, confidentiality, integrity
            • ARCH.170 Identify security losses and threats
          • ARCH.173 Prepare safety risk analysis
            • ARCH.023 Identify relevant safety legislation and regulation
            • ARCH.025 Create foundation for safety risk model
              • Draft foundation accidents
              • Draft foundation hazard
              • Draft foundation control measure
            • ARCH.026 Define the state model of accidents, hazardous and safe state
          • ARCH.020 Identify & classify operational deviations
          • ARCH.011 Assess operational performance risks of scenario
            • ARCH.014 Evaluate risks to business effectiveness
            • ARCH.015 Define business risk control measures
          • ARCH.017 Assess security risks of scenario
            • ARCH.021 Evaluate security risks
            • ARCH.022 Define operational security measures
          • ARCH.024 Assess operational safety risks of scenario
            • ARCH.027 Evaluate operational safety risks
            • ARCH.028 Define operational safety measures
          • 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.121 Consolidate operational activities and interactions
          • ARCH.183 Consolidate operational data
      • 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.065 Derive safety target to system functions and define additional risk control measure needed
            • ARCH.066 Identify system level deviations
            • ARCH.067 Populate the fault tree
            • ARCH.068 Assess deviation probability (external constraints)
            • ARCH.069 Add system level risk measures
          • ARCH.070 Calculate system deviation probability
        • 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.920 Define the logical architecture
        • ARCH.921 Decompose system functionality
          • ARCH.084 Execute automatic transition of system elements to logical level
          • ARCH.182 Split the system functions
          • ARCH.085 Create or update functional chains at logical level
          • ARCH.087 Model data flowing between logical functions
          • ARCH.191 Refine capability realisations for the logical architecture
        • ARCH.922 Define logical components
          • ARCH.180 Define logical component candidates
          • ARCH.181 Reconcile candidate logical components
        • ARCH.923 Apportion the non-functional requirements
          • ARCH.107 Apportion non-functional requirements to logical functions
          • ARCH.108 Define acceptance criteria for 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.127 Define location kinds
          • ARCH.126 Define structure of computation assets
          • ARCH.125 Define structure of communication assets
        • ARCH.935 Finalise the subsystem architecture
          • ARCH.116 Define subsystem specific requirements
          • ARCH.192 Refine capability realisations for the subsystem architecture
          • ARCH.176 Create subsystem exchange scenarios
          • ARCH.186 Consolidate single subsystem interface
        • 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.131 Derive & allocate NFRs to location kinds
          • ARCH.132 Derive & allocate NFRs to communication assets
          • ARCH.133 Derive & allocate NFRs to computation assets
          • ARCH.137 Allocate interface NFRs to interface layers/interface functions
          • ARCH.155 Allocate hazard mitigation NFRs to subsystems
        • 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.925 Transition from LA parent model to SA child models
        • ARCH.112 Execute vertical transition from logical architecture of parent model to system analysis of child model
        • ARCH.113 Trace elements between parent model and an already existing child model
    • Model view specifications
      • Views produced by ARCH
        • Enterprise level
          • AMOD-022 Enterprise & environment definition
          • AMOD-106 Enterprise goals
        • Operational level
          • AMOD-010 Trade space assessment
          • AMOD-012 System lifecycle model
          • AMOD-021 Operational capabilities definition
          • AMOD-023 Operational entity/actor states
          • AMOD-024 Operational activity definition and allocation
          • AMOD-025 Abstract concepts
          • AMOD-027 Operational bare business scenario
          • AMOD-028 Operational activities and interaction definitions (single operational capability)
          • AMOD-029 Operational bare business process
          • AMOD-030 Accident and hazard state model
          • AMOD-031 Unified risk model (to be discussed)
          • AMOD-032 Allocated risk control measures
          • AMOD-033 Operational business scenario with risk control measures
          • AMOD-034 Abstract concept states
          • AMOD-035 Operational business process with risk control measures
          • AMOD-101 Consolidated operational activities & interactions
          • AMOD-105 Operational data objects [O.CDB]
          • AMOD-107 Safety hazard, security issue, business risk log
          • AMOD-109 Accident hazard record
          • AMOD-110 Operational exchange items [O.CDB]
          • AMOD-128 Safety compliance strategy
          • AMOD-129 Relevant safety legislation/regulations
          • AMOD-130 Business loss and risk state model
          • AMOD-131 Security loss and threat state model
          • AMOD-135 Consolidated operational deviation analysis report
          • AMOD-136 Single operational capability deviation analysis report
          • AMOD-137 Single operational capability context
          • AMOD-145 Security compliance strategy
        • System level
          • AMOD-004 Fault tree (per operational deviation)
          • AMOD-041 System boundary options
          • AMOD-045 System capabilities
          • AMOD-046 Selected system boundary tradeoff record
          • AMOD-049 Non-functional requirements implementation
          • AMOD-050 Stakeholder non-functional requirements
          • AMOD-055 System functions to state allocation map [Matrix]
          • AMOD-056 System functions and exchanges (single system capability)
          • AMOD-057 Measures of performance
          • AMOD-058 Initial system exchange scenario
          • AMOD-059 Initial system functional chain description
          • AMOD-060 System/actor states
          • AMOD-071 System failure modes and effects analysis
          • AMOD-079 Agreed system requirements baseline (functional + non functional)
          • AMOD-103 Consolidated system functions
          • AMOD-104 System level - operational level traceability report
          • AMOD-112 System data objects [S.CDB]
          • AMOD-113 System exchange items [S.CDB]
          • AMOD-114 System interface definition
          • AMOD-115 External interface behaviour
          • AMOD-116 System implementation constraints
          • AMOD-117 System exchange scenarios with risk control measures [S.ES]
          • AMOD-118 System functional chain descriptions with risk control measures [SFCD]
          • AMOD-119 System context definition
          • AMOD-120 Record of system capabilities and missions
          • AMOD-121 Record of system and actor functions
          • AMOD-122 Record of system actors
          • AMOD-133 Consolidated system function allocation
          • AMOD-138 Single system capability context
          • AMOD-142 Single subsystem definition
          • AMOD-146 System needs and constraints tradeoff decision record
        • Logical level
          • AMOD-081 Logical functional flow definition (single system capability realisation)
          • AMOD-082 Logical functional chain definition
          • AMOD-083 State-based behaviour definition (logical function)
          • AMOD-084 Logical exchange scenario definition
          • AMOD-088 Consolidated logical functional flow definition
          • AMOD-091 Logical data objects [L.CDB]
          • AMOD-092 Logical exchange items [L.CDB]
          • AMOD-125 Logical architecture definition
          • AMOD-126 Logical level - system level traceability report
          • AMOD-147 Logical capability realisation
          • AMOD-149 Record of elements between models
        • Physical level
          • AMOD-075 Subsystem implementation constraints
          • AMOD-080 Subsystem option sketch
          • AMOD-085 Subsystem architecture definition (single realised capability)
          • AMOD-086 Interface layer data objects
          • AMOD-089 Subsystem lifecycle definition
          • AMOD-093 Subsystem architecture definition
          • AMOD-094 Interface layer exchange items
          • AMOD-095 Location kind definitions
          • AMOD-096 Communication asset structure
          • AMOD-097 Computation asset structure
          • AMOD-098 Consolidated tenderable element structure
          • AMOD-099 Interface layer exchange scenario
          • AMOD-100 Interface layer definition
          • AMOD-111 Subsystem interface definition to external system / actor
          • AMOD-124 Subsystem architecture tradeoff record
          • AMOD-127 Physical level - logical level traceability report
          • AMOD-140 Subsystem exchange scenario
          • AMOD-143 Inter-subsystem interface definition
          • AMOD-144 Behaviour definition (interface layer function)
          • AMOD-148 Subsystem capability realisation
      • Views produced outside ARCH
        • AMOD-015 Example CONOPS from other railway
        • AMOD-018 Organisation future process framework
        • AMOD-026 Service reliability/ availability targets
    • Whole Design Ontology
    • Design reviews
      • Design review structure
      • ARCH.R.1 Operational capability review
      • ARCH.R.2 Operational review - consolidated
      • ARCH.R.3 System capability review
      • ARCH.R.4 System review - consolidated
      • ARCH.R.5 Logical capability review
      • ARCH.R.6 Logical review - consolidated
      • ARCH.R.7 Subsystem capability review
      • ARCH.R.8 Subsystem review - consolidated
      • Definition of scope of compliance
    • ARCH - Process FAQs
    • ARCH.161
    • ARCH.056 Map system functionality to states
    • ARCH.057 Model non-payload data on external interfaces
Legal information

Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)

AMOD-125 Logical architecture definition

RCAMT-429 - Update consolidation step for logical functions to show further affected viewpoints Finished

Created by

ARCH.180 Define logical component candidates

ConcernsEnsure completeness and consistency of functional allocations to logical components or to logical actors.
Modified by

ARCH.096 Allocate logical functions to logical components (including alternative allocations)

ARCH.181 Reconcile candidate logical components

ARCH.154 Consolidate logical functional flow

Used by

ARCH.086 Create or update exchange scenarios at logical level

ARCH.154 Consolidate logical functional flow

ARCH.090 Identify alternative subsystem options

Viewpoint

In Capella this corresponds to a LAB diagram.

Mandatory viewpoint:


Diagram modelling rules

3. Modelling Rules for Logical Architecture#ModRules_VP_LAB


Element modelling rules

3. Modelling Rules for Logical Architecture#ModRules_VE_LogFunction

3. Modelling Rules for Logical Architecture#ModRules_VE_LogFuncExchange

3. Modelling Rules for Logical Architecture#ModRules_VE_LogComponent

3. Modelling Rules for Logical Architecture#ModRules_VE_LogActor

3. Modelling Rules for Logical Architecture#ModRules_VE_LogCompExchange

Viewpoint modelling rules

3. Modelling Rules for Logical Architecture#ModRules_VS_AMOD-125