++ :CAPACITY--MANAGEMENT--SYSTEM_lexForm_3
++ :EUROPE_S--RAIL--JOINT--UNDERTAKING_lexForm_4
++ :FUTURE--RAILWAY--MOBILE--COMMUNICATION--SYSTEM_lexForm_3
++ :TRAFFIC--MANAGEMENT--SYSTEM_lexForm_5
++ :TRAFFIC--MANAGEMENT--SYSTEM_lexForm_6
++ :CAPACITY--MANAGEMENT--SYSTEM_lexConcept_2
++ :COMMON--BUSINESS--OBJECTIVE_lexConcept_2
++ :EUROPE_S--RAIL--JOINT--UNDERTAKING_lexConcept_2
++ :EUROPE_S--RAIL--JOINT--UNDERTAKING_lexConcept_3
++ :FUTURE--RAILWAY--MOBILE--COMMUNICATION--SYSTEM_lexConcept_2
++ :SYSTEM--PILLAR--STEERING--GROUP_lexConcept_2
++ :TRAFFIC--MANAGEMENT--SYSTEM_lexConcept_4
++ :TRAFFIC--MANAGEMENT--SYSTEM_lexConcept_5
-- "An Application Condition is a requirement for the environment of a system in its application. Concretely these can be for example requirements concerning the skills of the users, temperatures in a data center, or maintenance processes that need to be established."
++ "An Application Condition is a requirement for the environment of a system in its application. Concretely these can be for example requirements concerning the skills of the users, temperatures in a data center, or maintenance processes that need to be established."
++ "{comment:33} A building block is a sourceable unit of the CCS system (hardware and/or software), having standardised functionality, standardised performance (RAM), standardised safety (including Tolerable Functional Failure Rate [TFFR], Safety Integrity Level [SIL] and Safety Related Application Conditions [SRAC]), standardised security and standardised interfaces towards other building blocks and/or external systems. A building block can also be defined as a standardised module. {comment:158}"
-- "A Building Block is a sourceable unit of the CCS System (hardware and/or software), having standardised functionality, standardised PRAMS requirements (including Tolerable Functional Failure Rate [TFFR], Safety Integrity Level [SIL] and Safety Related Application Conditions [SRAC]), standardised cyber security requirements (including Security Level [SL] based on the security requirements, and Security Related Application Conditions [SRAC]), standardised interfaces (on all OSI Layers) towards other Building Blocks and/or external systems. Building Blocks are exchangeable and migrateable, without impacting other Building Blocks. Building Blocks are separately sourceable from different suppliers and capable of being integrated by a third party."
++ "A Building Block is a sourceable unit of the CCS System (hardware and/or software), having standardised functionality, standardised PRAMS requirements (including Tolerable Functional Failure Rate [TFFR], Safety Integrity Level [SIL] and Safety Related Application Conditions [SRAC]), standardised cyber security requirements (including Security Level [SL] based on the security requirements, and Security Related Application Conditions [SRAC]), standardised interfaces (on all OSI Layers) towards other Building Blocks and/or external systems. Building Blocks are exchangeable and migrateable, without impacting other Building Blocks. Building Blocks are separately sourceable from different suppliers and capable of being integrated by a third party."
-- "{comment:33} A building block is a sourceable unit of the CCS system (hardware and/or software), having standardised functionality, standardised performance (RAM), standardised safety (including Tolerable Functional Failure Rate [TFFR], Safety Integrity Level [SIL] and Safety Related Application Conditions [SRAC]), standardised security and standardised interfaces towards other building blocks and/or external systems. A building block can also be defined as a standardised module. {comment:158}"
-- "ARCADIA (Architecture Analysis & Design Integrated Approach) is a system and software architecture engineering method based on architecture-centric and model-driven engineering activities. Main resources about ARCADIA can be found on the official websites: https://www.eclipse.org/capella/arcadia-reference.html (image: 1-screenshot-20230107-163323.png)"
++ "ARCADIA (Architecture Analysis & Design Integrated Approach) is a system and software architecture engineering method based on architecture-centric and model-driven engineering activities. Main resources about ARCADIA can be found on the official websites: https://www.eclipse.org/capella/arcadia-reference.html (image: 1-screenshot-20230107-163323.png)"
++ "An input or output of a task that crosses the process boundaries. Any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project. (e.g. Requirement Specification)"
-- "An input or output of a task that crosses the process boundaries. Any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project. (Source: ISO 24765:2017 3.1098) (e.g. Requirement Specification)"
++ "A function transforms several one or more input values to several one or more output values according to the function’s behaviour. The function’s behaviour is defined by one or multiple functional requirements, defining “what” the function is doing. Additional non-functional requirements attached to the function define the quality attributes of “how” (how safe, how accurate, how fast, how reliable, etc.) the function is performing the transformation. Some non-functional requirements, e.g., on weight constraints or physical dimension constraints), will also be allocated to subsystems."
-- "action, operation or service fulfilled by the system, or by an actor interacting with the system"
++ "action, operation or service fulfilled by the system, or by an actor interacting with the system"
-- "A function transforms several one or more input values to several one or more output values according to the function’s behaviour. The function’s behaviour is defined by one or multiple functional requirements, defining “what” the function is doing. Additional non-functional requirements attached to the function define the quality attributes of “how” (how safe, how accurate, how fast, how reliable, etc.) the function is performing the transformation. Some non-functional requirements, e.g., on weight constraints or physical dimension constraints), will also be allocated to subsystems."
++ "Integration is to combine current and/or new systems with a known behaviour to a larger system with a target behaviour. For any country migrating or upgrading their system(s) ‘integration’ is an important consideration to ensure the whole railway operates in a safe and reliable manner."
-- "See SPT2CE-244 - Horizontal integration and SPT2CE-245 - Vertical integration"
++ "See SPT2CE-244 - Horizontal integration and SPT2CE-245 - Vertical integration"
-- "Integration is to combine current and/or new systems with a known behaviour to a larger system with a target behaviour. For any country migrating or upgrading their system(s) ‘integration’ is an important consideration to ensure the whole railway operates in a safe and reliable manner."
++ "Based on ISO/IEC 2382, a shared boundary between two systems or subsystems, defined by various characteristics pertaining to the functions, physical signal exchanges, and other characteristics."
-- "a means provided or required by components for an interaction between them or with actors"
++ "a means provided or required by components for an interaction between them or with actors"
-- "Based on ISO/IEC 2382, a shared boundary between two systems or subsystems, defined by various characteristics pertaining to the functions, physical signal exchanges, and other characteristics."
++ "Interoperability means the ability to allow the safe and uninterrupted movement of trains that accomplish the specified levels of performance.Reference to the TSI (European Regulation) would be good to understand the importance (double. needs to be deleted)"
-- "Interoperability means the ability to allow the safe and uninterrupted movement of trains that accomplish the specified levels of performance, see [Subset-023] SPT2ARC-1619 and [IOP-Dir 2016/797] SPT2ARC-1617 so that a train is able to run across different infrastructure networks (IMs) and that an infrastructure network is able to interact with trains of different Railway Undertakings, using systems/sub-systems from different origins. Exchangeability and interchangeability are related to the physical characteristics of sub-systems whereas interoperability is related to interactions between subsystems (e.g. also between STM and ETCS on-board there is interoperability)."
++ "Interoperability means the ability to allow the safe and uninterrupted movement of trains that accomplish the specified levels of performance, see [Subset-023] SPT2ARC-1619 and [IOP-Dir 2016/797] SPT2ARC-1617 so that a train is able to run across different infrastructure networks (IMs) and that an infrastructure network is able to interact with trains of different Railway Undertakings, using systems/sub-systems from different origins. Exchangeability and interchangeability are related to the physical characteristics of sub-systems whereas interoperability is related to interactions between subsystems (e.g. also between STM and ETCS on-board there is interoperability)."
-- "Interoperability means the ability to allow the safe and uninterrupted movement of trains that accomplish the specified levels of performance.Reference to the TSI (European Regulation) would be good to understand the importance (double. needs to be deleted)"
++ "A collection of related processes, methods, and tools."
-- "A collection of related processes, methods, and tools. (Source: OMG)"
++ "A technique for performing a task. Method is a grouping of guidance, modelling{comment:72} language, rules, techniques and patterns. Different methods may be available for the same task. It defines the “HOW” of each task. (In this context, the words “method,” “technique,” “practice,” and “procedure” are often used interchangeably.) At any level, process tasks are performed using methods."
-- "A technique for performing a task. Method is a grouping of guidance, modelling{comment:72} language, rules, techniques and patterns. Different methods may be available for the same task. (Source: OMG)"
++ "On operational activity is one step in an operational process, that has one or more inputs, and one or more outputs. The activity describes what and how the operational entity the operational activity is allocated to is doing."
-- "A step or function of an operational process, done by actors that might need to use the system to reach certain objectives."
++ "A step or function of an operational process, done by actors that might need to use the system to reach certain objectives."
-- "On operational activity is one step in an operational process, that has one or more inputs, and one or more outputs. The activity describes what and how the operational entity the operational activity is allocated to is doing."
++ "An operational capability is an ability given by a group of processes."
-- "ability of an operational entity to provide a service"
++ "ability of an operational entity to provide a service"
-- "An operational capability is an ability given by a group of processes."
++ "A person or organisation performing an operational activity."
-- "Denotes an entity of the real world (such as another system, device, group or organisation ...) involved in operational activities to which the system of interest or stakeholders must contribute. An actor is a type of operational entity (usually human and indivisible).{comment:1}"
++ "Denotes an entity of the real world (such as another system, device, group or organisation ...) involved in operational activities to which the system of interest or stakeholders must contribute. An actor is a type of operational entity (usually human and indivisible).{comment:1}"
-- "A person or organisation performing an operational activity."
++ "An ordered (time or information) flow of operational activities."
-- "Specific organisation of activities and interactions, forming one path to fulfil an operational capability, within the set of all possible paths of operational data flows. It describes either an expected behaviour of one or several operational entities in a given context, or expresses non-functional properties on the path (such as latency, criticality, confidentiality, redundancy ...)."
++ "Specific organisation of activities and interactions, forming one path to fulfil an operational capability, within the set of all possible paths of operational data flows. It describes either an expected behaviour of one or several operational entities in a given context, or expresses non-functional properties on the path (such as latency, criticality, confidentiality, redundancy ...)."
-- "An ordered (time or information) flow of operational activities."
++ "A set of interrelated or interacting set of cohesive process tasks that transforms inputs into outputs. The Processes require a purpose and outcome, all processes have at least one process task."
-- "A set of interrelated or interacting set of cohesive process tasks that transforms inputs into outputs. The Processes require a purpose and outcome, all processes have at least one process task. (Source: ISO9001 and ISO 15288, 4.1.30)"
++ "Safety related application condition."
-- "Safety related application conditions are SPPR-2246 - Application Condition relevant for the safety of the application."
++ "Safety related application conditions are SPPR-2246 - Application Condition relevant for the safety of the application."
-- "Safety related application condition."
-- "a switch is a device that opens or closes electrical circuits."
++ "a switch is a device that opens or closes electrical circuits."
-- "Electrical switch. Closes or opens a circuit."
++ "Electrical switch. Closes or opens a circuit."
++ "Actors are entities outside the system (either humans or other technical systems) that interact with the system."
-- "external entity (human, system, ...) interacting with the system of interest through its interfaces"
++ "external entity (human, system, ...) interacting with the system of interest through its interfaces"
-- "Actors are entities outside the system (either humans or other technical systems) that interact with the system."
++ "A System capability is a service an actor requires from the system to fulfil its business goals. System capabilities are realised by exploiting one or multiple Functions, usually in a chain of functions. System capabilities in terms of this document are very similar to Use cases and the theory behind it."
-- "Ability of the system to provide a service that support the realisation of high-level operational objectives (including the contribution of the system to an operational capability)."
++ "Ability of the system to provide a service that support the realisation of high-level operational objectives (including the contribution of the system to an operational capability)."
-- "A System capability is a service an actor requires from the system to fulfil its business goals. System capabilities are realised by exploiting one or multiple Functions, usually in a chain of functions. System capabilities in terms of this document are very similar to Use cases and the theory behind it."
++ "According to ISO 15288 a system is “a combination of interacting elements organized to achieve one or more stated purposes. “. In terms of this document, a system in black box view is furthermore defined by: * interfaces to actors outside the system, defining the system boundary * at least one function allocated to it * at least one system capability that the system delivers as a service to the actors A system in white box view can be further refined into (exclusive or): * into a more granular systems, hence making itself to a system of systems * into subsystems on the lowest level of system of systems refinement In both cases, a system is a conceptual entity that aggregates the properties of its constituents but is not the element that defines the properties itself. A system is hence subject to the emerging properties of its constituents. Example: The system “onboard CCS” does not define the properties of this system itself, the properties emerge from the combined properties of the subsystems “ETCS core”, “Onboard localization” and “Onboard map” (examples only). Usage context definitions of term „system“: * Constituent system: according to ISO 21839, a system that forms part of a system of systems * System of interest: according to ISO 21839, a system whose life cycle or properties are under consideration in a given context"
-- "Subject of interest of the engineering activities described by ARCADIA, which is also an organized collection of elements working as a whole."
++ "Subject of interest of the engineering activities described by ARCADIA, which is also an organized collection of elements working as a whole."
-- "According to ISO 15288 a system is “a combination of interacting elements organized to achieve one or more stated purposes. “. In terms of this document, a system in black box view is furthermore defined by: * interfaces to actors outside the system, defining the system boundary * at least one function allocated to it * at least one system capability that the system delivers as a service to the actors A system in white box view can be further refined into (exclusive or): * into a more granular systems, hence making itself to a system of systems * into subsystems on the lowest level of system of systems refinement In both cases, a system is a conceptual entity that aggregates the properties of its constituents but is not the element that defines the properties itself. A system is hence subject to the emerging properties of its constituents. Example: The system “onboard CCS” does not define the properties of this system itself, the properties emerge from the combined properties of the subsystems “ETCS core”, “Onboard localization” and “Onboard map” (examples only). Usage context definitions of term „system“: * Constituent system: according to ISO 21839, a system that forms part of a system of systems * System of interest: according to ISO 21839, a system whose life cycle or properties are under consideration in a given context"
++ "The term Tools refers to all supplier specific applications required to develop, test, integrate, deploy, diagnose and maintain FA Tasks, Functional Applications, Functional Systems and/or Systems of Systems. It may also include applications needed for the the virtualisation and/or hardware layer."
-- "An instrument that, when applied to a particular method, can enhance the efficiency of the task, provided it is applied properly and by somebody with proper skills and training."
-- "Traffic Management System (double, needs to be deleted)"
++ "Traffic Management System (double, needs to be deleted)"
-- "Traffic Management System is used to manage the operation of the railway system and to ensure efficient recovery when unexpected traffic disruptions occur."
-- "* ork items examples: “A requirement”, or “a function”, or “a concept aspect” * Work items are objects in the “engineering database” (ALM) that represent the result of a design step. * The structure of the work items is defined by the SEMP process definition documents (overview in the maps), that also make use of modelling standards like ARCADIA or SysML * The master-engineering database is the ALM System (currently Polarion) which contains all work items and their links."
++ "* ork items examples: “A requirement”, or “a function”, or “a concept aspect” * Work items are objects in the “engineering database” (ALM) that represent the result of a design step. * The structure of the work items is defined by the SEMP process definition documents (overview in the maps), that also make use of modelling standards like ARCADIA or SysML * The master-engineering database is the ALM System (currently Polarion) which contains all work items and their links."
++ "An artefact associated with the execution of a process."
-- "An artefact associated with the execution of a process. (Source: ISO 24765:2017 3.4611)"