Common use of Overall Model Clause in Contracts

Overall Model. Figure 9 provides a package structure overview of the expected EAST-ADL modelling elements for the braking system architecture, as well as its associated requirements, variability and other non- functional constraints (e.g., timing and dependability), and verification&validation (V&V) cases. The SystemModel (within the 0_TopPackage) contains the entire braking electrical/electronic system architecture, for which specifications at various abstraction levels are applied. Figure 10 provides a graphical representation of this multi-level braking electrical/electronic system specification and its related environment model (EnvironmentBBW). Figure 10: The braking electrical/electronic system and its environment‌ EAST-ADL supports requirements, V&V cases, and the annotations of variability and other non- functional constraints through separate modeling packages shown in Error! Reference source not found.. (Such extension packages are contained in the EAST-ADLExtensionElements package in Error! Reference source not found.). A requirement model specifies the conditions or capabilities that must be met or possessed by a system or its component. In a model-based approach, requirements are derived, refined, mapped, validated and verified along with the progress of system design. The specifications of variability and other non-functional constraints augment the multi-level system architecture specification with analytical information (e.g. timing, reliability, and safety integrity) for early quality predictions and contract declarations. Normally, an analytical model should have its level of abstraction according to its target artefacts.

Overall Model. Figure 9 2-19 provides a package structure overview of the expected EAST-ADL modelling elements for the braking system architecture, as well as its associated requirements, variability and other non- non-functional constraints (e.g., timing and dependability), and verification&validation (V&V) cases. The SystemModel (within the 0_TopPackage) contains the entire braking electrical/electronic system architecture, for which specifications at various abstraction levels are applied. Figure 10 2-20 provides a graphical representation of this multi-level braking electrical/electronic system specification and its related environment model (EnvironmentBBW). Figure 10: The braking electrical/electronic system and its environment‌ EAST-ADL supports requirements, V&V cases, and the annotations of variability and other non- functional constraints through separate modeling modelling packages shown in Error! Reference source not found.. Figure 2-21. (Such extension packages are contained in the EAST-ADLExtensionElements ADL ExtensionElements package in Error! Reference source not found.Figure 2-21). A requirement model specifies the conditions or capabilities that must be met or possessed by a system or its component. In a model-based approach, requirements are derived, refined, mapped, validated and verified along with the progress of system design. The specifications of variability and other non-functional constraints augment the multi-level system architecture specification with analytical information (e.g. timing, reliability, and safety integrity) for early quality predictions and contract declarations. Normally, an analytical model should have its level of abstraction according to its target artefacts.

Overall Model. Figure 9 2-33 provides a package structure overview of the expected EAST-ADL modelling elements for the braking system architecture, as well as its associated requirements, variability and other non- non-functional constraints (e.g., timing and dependability), and verification&validation (V&V) cases. The SystemModel (within the 0_TopPackage) contains the entire braking electrical/electronic system architecture, for which specifications at various abstraction levels are applied. Figure 10 2-34 provides a graphical representation of this multi-level braking electrical/electronic system specification and its related environment model (EnvironmentBBW). Figure 10: The braking electrical/electronic system and its environment‌ EAST-ADL supports requirements, V&V cases, and the annotations of variability and other non- functional constraints through separate modeling modelling packages shown in Error! Reference source not found.. Figure 2-35. (Such extension packages are contained in the EAST-ADLExtensionElements ADL ExtensionElements package in Error! Reference source not found.Figure 2-35). A requirement model specifies the conditions or capabilities that must be met or possessed by a system or its component. In a model-based approach, requirements are derived, refined, mapped, validated and verified along with the progress of system design. The specifications of variability and other non-functional constraints augment the multi-level system architecture specification with analytical information (e.g. timing, reliability, and safety integrity) for early quality predictions and contract declarations. Normally, an analytical model should have its level of abstraction according to its target artefacts.