SWE.4 Software Unit Verification

Linked Knowledge Nuggets:
arrow_forward "Software Unit Verification"

person Author: Process Fellows
SWE.4 – Software Unit Verification ensures that individual software units behave as intended and conform to the detailed design. The process covers test planning, execution, traceability, and clear communication of results—ensuring quality from the ground up.

• school PF_SWE.4_Software Unit Verification_Extract.pdf
  

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)

arrow_forward "Verification level vs. Verification timepoint"

person Author: Process Fellows
The execution of a verification measure is not necessarily linked to the verification time point. It is possible that a verification measure from SWE.6 is carried out as part of the verification of the SW component and integration verrifcation if the setup or the environment is better suited to this. However, it remains a verification of the SW requirements. The decisive factor is what a verification measure is derived from. However, it is important to ensure that this verification measure is included in and part of the report and in the summary of the SW verification. Pay attention to the sequences and dependencies to be followed.

• 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.) for software unit (Software unit = Software unit in design and implementation-oriented processes: As a result of the decomposition of a software component, the software is decomposed into software units which are a representation of a software element, which is decided not to be further subdivided and that is a part of a software component at the lowest level, in a conceptual model. Software unit in verification-oriented processes: An implemented SW unit under verification is represented e.g., as source code files, or an object file.) verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) are specified.
• O2 Software unit (Software unit = Software unit in design and implementation-oriented processes: As a result of the decomposition of a software component, the software is decomposed into software units which are a representation of a software element, which is decided not to be further subdivided and that is a part of a software component at the lowest level, in a conceptual model. Software unit in verification-oriented processes: An implemented SW unit under verification is represented e.g., as source code files, or an object file.) 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, including criteria for regression verification (Regression verification = Selective re-verification of elements to verify that modifications have not caused unintended effects.).
• O3 Software units (Software unit = Software unit in design and implementation-oriented processes: As a result of the decomposition of a software component, the software is decomposed into software units which are a representation of a software element, which is decided not to be further subdivided and that is a part of a software component at the lowest level, in a conceptual model. Software unit in verification-oriented processes: An implemented SW unit under verification is represented e.g., as source code files, or an object file.) are verified 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 results are recorded.
• O4 Consistency and bidirectional traceability are 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 software units (Software unit = Software unit in design and implementation-oriented processes: As a result of the decomposition of a software component, the software is decomposed into software units which are a representation of a software element, which is decided not to be further subdivided and that is a part of a software component at the lowest level, in a conceptual model. Software unit in verification-oriented processes: An implemented SW unit under verification is represented e.g., as source code files, or an object file.); and bidirectional traceability is established between verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results 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 Results of the software unit (Software unit = Software unit in design and implementation-oriented processes: As a result of the decomposition of a software component, the software is decomposed into software units which are a representation of a software element, which is decided not to be further subdivided and that is a part of a software component at the lowest level, in a conceptual model. Software unit in verification-oriented processes: An implemented SW unit under verification is represented e.g., as source code files, or an object file.) verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) are summarized and communicated to all affected parties.

BP3 Verify software units. ( O3 )

Perform software unit (Software unit = Software unit in design and implementation-oriented processes: As a result of the decomposition of a software component, the software is decomposed into software units which are a representation of a software element, which is decided not to be further subdivided and that is a part of a software component at the lowest level, in a conceptual model. Software unit in verification-oriented processes: An implemented SW unit under verification is represented e.g., as source code files, or an object file.) verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) 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.). Record the verification (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 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.) data.
Note 3: See SUP.9 for handling of verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results that deviate from expected results.

Linked Knowledge Nuggets:
arrow_forward "Archiving test results"

person Author: Process Fellows
Don’t lose your evidence. With perspective to testing, SUP.8.BP1 in combination with SUP.8.BP8 expects structured storage of test logs, verdicts, anomalies, and configuration info. This is not only a formality: It enables you to later on reproduce details about a certain system version.

BP4 Ensure consistency and establish bidirectional traceability. ( O4 )

Ensure consistency and establish bidirectional traceability 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 the software units (Software unit = Software unit in design and implementation-oriented processes: As a result of the decomposition of a software component, the software is decomposed into software units which are a representation of a software element, which is decided not to be further subdivided and that is a part of a software component at the lowest level, in a conceptual model. Software unit in verification-oriented processes: An implemented SW unit under verification is represented e.g., as source code files, or an object file.) defined in the detailed design. Establish bidirectional traceability between the verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results 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.).
Note 4: 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.