MEE.4
Mechanical Integration and Verification against Mechanical Architecture and Design
# PROCESS PURPOSE
The purpose is: 1. to verify the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) against the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design and 2. to ensure the integration of the Mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.) into an integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.) consistent with the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture and 3. to verify the integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.) against the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture.
# PROCESS OUTCOMES
O1 (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) are specified for Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) based on the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design.
O2 (Measure = An activity to achieve a certain intent.) for Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) are selected according to the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) Scope considering Regression Criteria.
O3
The Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design is verified using the selected (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) and the (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results are recorded.
O4
The Mechanical Integration Sequence of the Mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.) (Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) and/or Mechanical (System = A system consists of at least two elements which can be either a system or a component.)) is specified consistent with the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture.
O5 (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) are specified for the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) based on the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture, including the interfaces and (Interaction = Interaction occurs between elements of the respective system or between elements of the respective system and the Operating Environment.) between Mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.).
O6
Mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.) are integrated up to a complete integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.) consistent with the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) Scope.
O7 (Measure = An activity to achieve a certain intent.) for Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) are selected according to the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) Scope considering Regression Criteria.
O8
Integrated Mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.) are verified using the selected (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) and the (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results are recorded.
O9 (Consistency = Consistency addresses content and semantics and ensures that Information items are not in contradiction to each other.
Consistency is supported by bidirectional traceability.
See also chapter D.3.) and bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) are established between the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) and Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design; and bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) is established as chain between the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.), Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results and Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.).
O10 (Consistency = Consistency addresses content and semantics and ensures that Information items are not in contradiction to each other.
Consistency is supported by bidirectional traceability.
See also chapter D.3.) and bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) are established between Integration Steps and the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture; and (Consistency = Consistency addresses content and semantics and ensures that Information items are not in contradiction to each other.
Consistency is supported by bidirectional traceability.
See also chapter D.3.) and bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) are established between the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) (Measure = An activity to achieve a certain intent.) and Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture; and bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) is established as chain between the Mechanical (System = A system consists of at least two elements which can be either a system or a component.), Integration Data and Integration Steps; and bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) is established as chain between the Mechanical (System = A system consists of at least two elements which can be either a system or a component.), Mechanical S
O11
Bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) is established between the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) and Mechanical (System = A system consists of at least two elements which can be either a system or a component.).
O12
The Integration Data are summarized to the Integration Report, which is communicated to all affected parties; the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results and the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) Results are summarized and communicated to all affected parties.
Specify Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) suitable to provide evidence for compliance of the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) with the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design. This includes:
a) techniques for the (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.)
b) pass/fail criteria for (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.)
c) a definition of Entry and Exit Criteria for the (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.)
d) necessary sequence of (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.)
e) the required (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Infrastructure and Environment Setup
Document the selection of the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) considering selection criteria including criteria for (Regression verification = Selective re-verification of elements to verify that modifications have not caused unintended effects.). The documented selection of (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) shall have sufficient (Coverage = There are:
all objects
relevant objects
mapped objects
Coverage is a measure used to describe the ratio of mapped objects to relevant objects for a specific purpose.
For instance:
Requirements coverage: ratio of mapped system requirements versus relevant system requirements
Dimensional test coverage: ratio of tested dimensions versus total numbers of dimensions
Elements test coverage: degree of tested elements versus all created elements
Verification coverage for critical characteristics: ratio of tested or verified (e.g. production process capability – CpK) critical characteristics based on control plan
) according to the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) Scope.
Note 1: Examples for Selection Criteria can be prioritization of requirements, the need for (Regression verification = Selective re-verification of elements to verify that modifications have not caused unintended effects.) due to e.g. changes to the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design, the intended use of the delivered product (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) (test bench, test track, public road, etc.).
Perform Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) using the selected Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.). Record the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results including pass/fail status and measured values with reference to the verified Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.).
Note 2: (Capable Verification Environment = Documented, qualified (e.g., gauge repeatability and reproducibility [R&R]) and released test infrastructure.) as defined in the (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) needs to be available for performing (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) against Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design.
Note 3: See SUP.9 for handling (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results that deviate from expected results.
Imagine You Enjoy Improvement
Sponsored
At Process Fellows, we believe that progress should be both inspiring and rewarding. With a pragmatic approach and a strong team spirit, our internationally recognized experts help organizations worldwide optimize their processes and projects providing assessment, consulting, coaching, and training services.
Join us in shaping success. Because improvement isn’t just a goal—it’s an experience.
Let’s improve together!
BP4
Define Integration Sequence Instruction and specify Mechanical System Integration Verification Measures. (
O4, O5 )
Identify Mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.) based on the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture.
Define the Integration Sequence Instruction including Integration Steps and (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) (Measure = An activity to achieve a certain intent.) for the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Integration.
The Integration Sequence Instruction shall be suitable to provide evidence for compliance of the integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.) with the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture. This includes:
a) preconditions and techniques for the (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.)
b) pass/fail criteria for (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.)
c) a definition of Entry and Exit Criteria for Integration and the (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.)
d) necessary sequence of (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.)
e) the required (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Infrastructure and Environment Setup
Note 4: Internal interfaces (between the mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.)) and external interfaces should be verified according to the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture and the specified Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) (Measure = An activity to achieve a certain intent.).
BP5
Select Mechanical System Integration verification measures. (
O7 )
Document the selection of Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) (Measure = An activity to achieve a certain intent.) for each Integration Step considering selection criteria including criteria for (Regression verification = Selective re-verification of elements to verify that modifications have not caused unintended effects.). The documented selection of (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) shall have sufficient (Coverage = There are:
all objects
relevant objects
mapped objects
Coverage is a measure used to describe the ratio of mapped objects to relevant objects for a specific purpose.
For instance:
Requirements coverage: ratio of mapped system requirements versus relevant system requirements
Dimensional test coverage: ratio of tested dimensions versus total numbers of dimensions
Elements test coverage: degree of tested elements versus all created elements
Verification coverage for critical characteristics: ratio of tested or verified (e.g. production process capability – CpK) critical characteristics based on control plan
) according to the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) Scope.
Note 5: Examples for Selection Criteria can be prioritization of requirements, the need for (Regression verification = Selective re-verification of elements to verify that modifications have not caused unintended effects.) due to e.g., changes to the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture, or the intended use of the delivered product (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.).
BP6
Integrate Mechanical System elements and perform Mechanical System integration verification. (
O6, O8 )
Integrate the Mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.) into an integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.) according to the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) Scope based on the Integration Sequence Instruction.
Perform the selected Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) (Measure = An activity to achieve a certain intent.) to verify the Mechanical Interfaces.
Record the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) Results including pass/fail status, integration data and the corresponding (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) Data with reference to the Mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.).
Note 6: The Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Integration should be performed with verified Mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.). If not, justification should be provided.
Note 7: Capable (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Infrastructure and Environment Setup as defined in the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) (Measure = An activity to achieve a certain intent.) needs to be available for performing Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Integration and Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.).
Note 8: See SUP.9 for handling (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results that deviate from expected results.
1. Ensure (Consistency = Consistency addresses content and semantics and ensures that Information items are not in contradiction to each other.
Consistency is supported by bidirectional traceability.
See also chapter D.3.) and establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) and the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design.
2. Establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results and the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.).
3. Establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the verified Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) and the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results.
4. Ensure (Consistency = Consistency addresses content and semantics and ensures that Information items are not in contradiction to each other.
Consistency is supported by bidirectional traceability.
See also chapter D.3.) and establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the Integration Steps and the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture.
5. Establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the Integration Data and the Integration Steps.
6. Establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.) and the Integration Data.
7. Ensure (Consistency = Consistency addresses content and semantics and ensures that Information items are not in contradiction to each other.
Consistency is supported by bidirectional traceability.
See also chapter D.3.) and establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) (Measure = An activity to achieve a certain intent.) and the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Architecture.
8. Establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) Results and the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) (Measure = An activity to achieve a certain intent.).
9. Establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the verified integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.) and the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) Results.
10. Establish bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) and the integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.).
Note 9: Bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) supports (Consistency = Consistency addresses content and semantics and ensures that Information items are not in contradiction to each other.
Consistency is supported by bidirectional traceability.
See also chapter D.3.), and facilitates impact analyses of change requests, and demonstration of (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) (Coverage = There are:
all objects
relevant objects
mapped objects
Coverage is a measure used to describe the ratio of mapped objects to relevant objects for a specific purpose.
For instance:
Requirements coverage: ratio of mapped system requirements versus relevant system requirements
Dimensional test coverage: ratio of tested dimensions versus total numbers of dimensions
Elements test coverage: degree of tested elements versus all created elements
Verification coverage for critical characteristics: ratio of tested or verified (e.g. production process capability – CpK) critical characteristics based on control plan
). (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) alone, e.g. the existence of links, does not necessarily mean that the information is consistent with each other.
Linked Knowledge Nuggets: arrow_forward "Consistency vs. Traceability – What’s the Difference?"
personAuthor: Process Fellows
Consistency ensures that related content doesn’t contradict itself – e.g., requirements align with architecture and test. Traceability, in contrast, is about links: can you follow a requirement through to implementation and verification? Both are needed – consistency builds trust, traceability enables control. Typically, traceability strongly supports consistency review.
arrow_forward "The role of traceability in risk control"
personAuthor: Process Fellows
Traceability isn’t just about completeness — it’s about managing impact. When a requirement changes, trace links tell you what’s affected. That’s your early-warning system.
arrow_forward "The true benefit of traceability
"
personAuthor: Process Fellows
Sometimes the creation of traceability is seen as an additional expense, the benefits are not recognized.
Traceability should be set up at the same time as the derived elements are created. Both work products are open in front of us and the creation of the trace often only takes a few moments.
In the aftermath, the effort increases noticeably and the risk of gaps is high.
If the traceability is complete and consistent, the discovery of dependencies is unbeatably fast and reliable compared to searching for dependencies at a later stage, when there may also be time pressure.
It also enables proof of complete coverage of the derived elements and allows the complete consistency check.
BP8
Summarize and communicate the Integration and verification results. (
O11, O12 )
Summarize the Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Design (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results.
Summarize the Integration Data into the Integration Report.
Summarize the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Integration Verification = The emphasis of integration verification is on the interfaces and interactions between the different elements.) Results.
Communicate them to all affected parties.
Note 10: Providing all necessary information from the (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) execution in a summary enables other parties to judge the consequences.
# OUTPUT INFORMATION ITEMS
13-52
Communication Evidence (
O12 )
All forms of interpersonal communication such as
emails, also automatically generated ones
tool-supported workflows
meeting, verbally or via meeting minutes (e.g. daily standups)
podcasts
blogs
videos
forums
live chats
wikis
photo protocols
Used by these processes:
MEE.1 Mechanical Requirements Analysis
MEE.2 Mechanical Architecture and Design
MEE.3 Mechanical Component Sample Production
MEE.4 Mechanical Integration and Verification against Mechanical Architecture and Design
MEE.5 Verification against Mechanical Requirements
Used by these process attributes:
PA2.1 Performance Management
13-51
Consistency Evidence (
O9, O10, O11 )
Demonstrates bidirectional (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) between artifacts or information in artifacts, throughout all phases of the life cycle, by e.g.
tool links
hyperlinks
editorial references
naming conventions
Evidence that the content of the referenced or mapped information coheres semantically along the (Traceability = Traceability refers to the existence of references or links between Information items.
Traceability supports coverage analysis, impact analysis, requirements implementation status tracking etc.
See also chapter D.3.) chain, e.g. by
performing pair or group work
performing peer reviews, e.g. spot checks
maintaining revision histories in documents
providing change commenting (via e.g. meta-information) of database or repository entries
This evidence can be accompanied by e.g. Definition of Done (DoD) approaches
Used by these processes:
MEE.1 Mechanical Requirements Analysis
MEE.2 Mechanical Architecture and Design
MEE.3 Mechanical Component Sample Production
MEE.4 Mechanical Integration and Verification against Mechanical Architecture and Design
MEE.5 Verification against Mechanical Requirements
15-ME02
Integration Report (
O12 )
Identification of the used BOM
Identification of assembled (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.) (e.g. serial number, batch number, lot number)
Assembly related:
Findings and observations
Integration data
Deviations from the integration specification
Used by these processes:
MEE.4 Mechanical Integration and Verification against Mechanical Architecture and Design
06-50
Integration Sequence Instruction (
O4 )
Identification of required physical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.) (e.g., hardware, mechanical, wiring (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.)), and software executables and (Application parameter = An application parameter is a software variable containing data that can be changed at the system or software level; they influence the system or software behavior and properties.
The notion of application parameter is expressed in two ways:
The specification (including variable names, the domain value range, technical data types, default values, physical unit (if applicable), the corresponding memory maps, respectively).
The actual quantitative data value it receives by means of data application.
Application parameters are not requirements. They are a technical implementation solution for configurability-oriented requirements.) (being a technical implementation solution for configurability-oriented requirements)
Necessary sequence or ordering of integration
Preconditions for starting (System = A system consists of at least two elements which can be either a system or a component.) integration
Used by these processes:
MEE.4 Mechanical Integration and Verification against Mechanical Architecture and Design
11-ME03
Mechanical System (
O6 )
Mechanical (System = A system consists of at least two elements which can be either a system or a component.) is an integration of at least two mechanical (Element = The term Element is a collective term for virtual or physical objects on architecture, design, and verification level on the left and right side of the "V-Model".
An architecture specifies the elements of the system. Elements are hierarchically decomposed into smaller elements down to the components which are at the lowest level of the architecture.) (e.g. Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.), Mechanical (System = A system consists of at least two elements which can be either a system or a component.))
Used by these processes:
MEE.4 Mechanical Integration and Verification against Mechanical Architecture and Design
08-60
Verification Measure (
O1, O5 )
A (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) can be a (Test case = a) A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.
b) Documentation specifying inputs, predicted results, and a set of execution conditions for a test item.), a (Measurement = The activity to find the size, quantity or degree of something.), a calculation, a simulation, a review, an optical inspection, or an analysis
The specification of a (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) includes:
pass/fail criteria for (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) (test completion and ending criteria)
a definition of entry and exit criteria for the (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.), and abort and re-start criteria
Techniques (e.g., black-box and/or white-box-testing, equivalence classes and boundary values, fault injection testing for Functional Safety, penetration testing for Cybersecurity, back-to-back testing for (Model-based development = Development which is based on models (e.g., analytical, numerical) that represent the reality of the respective elements in a sufficient way and that are used for sizing, design, simulation, optimization, and validation.
Note: Simulation results should be verified by tests of physical elements.), ICT)
Necessary (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) environment & infrastructure
Necessary sequence or ordering
Used by these processes:
MEE.4 Mechanical Integration and Verification against Mechanical Architecture and Design
MEE.5 Verification against Mechanical Requirements
03-50
Verification Measure Data (
O8 )
Used by these processes:
MEE.4 Mechanical Integration and Verification against Mechanical Architecture and Design
MEE.5 Verification against Mechanical Requirements
08-58
Verification Measure Selection Set (
O2, O7 )
Include criteria for re- (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) in the case of changes (regression)
Identification of (Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.), also for regression testing
Used by these processes:
MEE.4 Mechanical Integration and Verification against Mechanical Architecture and Design
MEE.5 Verification against Mechanical Requirements
15-52
Verification Results (
O3, O8 )
(Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) data and logs
(Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) passed
(Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) not passed
(Verification measure = Verification measures can be:
Test cases
Measurements
Calculations
Simulations
Reviews
Analyses
Note: In particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.) not executed
information about the test execution (date, tester name, etc.)
Abstraction or summary of (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results
Used by these processes:
MEE.4 Mechanical Integration and Verification against Mechanical Architecture and Design
MEE.5 Verification against Mechanical Requirements
MEE.4
Mechanical Integration and Verification against Mechanical Architecture and Design
