HWE.3 Verification against Hardware Design

Linked Knowledge Nuggets:
arrow_forward "Testmanagement"

person Author: Process Fellows
Test Management ensures that testing activities are strategically planned, monitored, and evaluated across all development phases. From unit tests to system-level integration, this cross-cutting discipline defines methods, tools, documents, and roles to ensure traceable and efficient verification and validation.

• school PF_Testmanagement_Extract.pdf
  Short Overview of Test Management (related to all Automotive SPICE® verification processes)

• O1 Verification measures (Verification measure = Verification measure can be:
  • Test cases
  • Measurements
  • Calculations
  • Simulations
  • Reviews
  • Analyses
  Note, that 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 verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) of the hardware (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) against the hardware (Hardware = Assembled and interconnected electrical or electronic hardware components or parts which perform analog or digital functions or operations.) design, including the interfaces between hardware elements (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.) and the dynamic aspects.
• O2 Verification measures (Verification measure = Verification measure can be:
  • Test cases
  • Measurements
  • Calculations
  • Simulations
  • Reviews
  • Analyses
  Note, that 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 (Release = A physical product delivered to a customer, including a defined set of functionalities and properties.) scope considering criteria, including criteria for regression verification (Regression verification = Selective re-verification of elements to verify that modifications have not caused unintended effects.).
• O3 Verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) is performed on production data compliant samples using the selected verification measures (Verification measure = Verification measure can be:
  • Test cases
  • Measurements
  • Calculations
  • Simulations
  • Reviews
  • Analyses
  Note, that 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 verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results are recorded.
• O4 Consistency and bidirectional traceability are established between hardware elements (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.) and verification measures (Verification measure = Verification measure can be:
  • Test cases
  • Measurements
  • Calculations
  • Simulations
  • Reviews
  • Analyses
  Note, that 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 Bidirectional traceability is established between verification measures (Verification measure = Verification measure can be:
  • Test cases
  • Measurements
  • Calculations
  • Simulations
  • Reviews
  • Analyses
  Note, that 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 verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results.
• O6 Verification (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.

BP5 Ensure consistency and establish bidirectional traceability. ( O4, O5 )

Ensure consistency and establish bidirectional traceability between hardware elements (Hardware element = Generic term; can represent a hardware component, a hardware part, a hardware interface, or the hardware.) and the verification measures (Verification measure = Verification measure can be:

• Test cases
• Measurements
• Calculations
• Simulations
• Reviews
• Analyses

Note, that in particular domains certain verification measures may not be applicable, e.g., software units generally cannot be verified by means of calculations or analyses.). Establish bidirectional traceability between the verification measures (Verification measure = Verification measure can be:

• Test cases
• Measurements
• Calculations
• Simulations
• Reviews
• Analyses

Note, that 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 verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results.
Note 6: Bidirectional traceability supports consistency, and facilitates impact analysis of change requests, and demonstration of verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) coverage. Traceability 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?"

person Author: 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"

person Author: 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 "

person Author: 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.