MEE.5
Verification against Mechanical Requirements
# PROCESS PURPOSE
The purpose is to ensure that 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.) are verified to provide evidence for compliance with the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Requirements and Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Requirements.
# 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 the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) and Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) based on the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Requirements and Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Requirements.
O2 (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 selected according to the (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) Scope considering Regression Criteria and including criteria for (Regression verification = Selective re-verification of elements to verify that modifications have not caused unintended effects.).
O3
The Mechanical (System = A system consists of at least two elements which can be either a system or a component.) and Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) 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.
O4 (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.) Requirements (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.) Requirements; 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 a chain between 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.) Requirements (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.) Requirements (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.).
O5 (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.) Requirements (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 (System = A system consists of at least two elements which can be either a system or a component.) Requirements; 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 a chain between the Mechanical (System = A system consists of at least two elements which can be either a system or a component.), Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Requirements (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results and Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Requirements (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.).
O6
The Mechanical (System = A system consists of at least two elements which can be either a system or a component.) (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.) (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results are summarized and communicated to all affected parties.
# BASE PRACTICES
BP1
Specify Verification Measures for Mechanical Components and integrated Mechanical System. (
O1 )
Specify (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.) for Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) and integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.) suitable to provide evidence for compliance with the functional and non-functional Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Requirements and with the functional and non-functional Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Requirements, including:
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
Note 1: 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.) may cover aspects such as thermal, environmental, robustness/ lifetime, etc.
BP2
Select Verification Measures for Mechanical Components and integrated Mechanical System. (
O2 )
Select Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Requirements (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.) as well as Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Requirements (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.). Document the selection of 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.) 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 2: Examples for Selection Criteria can be prioritization of requirements, the need for regression
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.) Requirements or the Mechanical (System = A system consists of at least two elements which can be either a system or a component.) Requirements,
the intended use of the delivered product (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) (e.g., test bench, test track, public road, etc. for integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.)).
BP3
Verify the Mechanical Components and integrated Mechanical System. (
O3 )
Perform the (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) 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.) and the integrated Mechanical (System = A system consists of at least two elements which can be either a system or a component.) 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.). Record the (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results including pass/fail status and 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.
Note 3: (Capable Verification Environment = Documented, qualified (e.g., gauge repeatability and reproducibility [R&R]) and released test infrastructure.) as defined needs to be available for performing (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) of mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) and integrated mechanical (System = A system consists of at least two elements which can be either a system or a component.).
Note 4: 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.) can be physical or virtual.
Note 5: 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 (System = A system consists of at least two elements which can be either a system or a component.) Requirements (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 (System = A system consists of at least two elements which can be either a system or a component.) Requirements.
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 (System = A system consists of at least two elements which can be either a system or a component.) Requirements (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.) Requirements (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 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.) Requirements (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 Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Requirements (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.) Requirements.
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 Mechanical (Component = Components (physical or virtual) are the lowest level elements of the mechanical architecture for which the component design is further defined.) Requirements (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.) Requirements (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.).
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 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.) Requirements (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results.
Note 6: 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.), facilitates impact analyses of change requests, and the 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.
BP5
Summarize and communicate the Verification Results. (
O6 )
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.) Requirements (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.) Requirements (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) Results and communicate them to all affected parties.
Note 7: 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 (
O6 )
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 (
O4, O5 )
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
08-60
Verification Measure (
O1 )
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 (
O3 )
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 )
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 )
(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.5
Verification against Mechanical Requirements
