SWIV Software Integration and Verification

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)

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 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.), for software component (Software component = Software component in design and implementation-oriented processes: The software architecture decomposes the software into software components across appropriate hierarchical levels down to the lowest-level software components in a conceptual model. Software component in verification-oriented processes: The implementation of a SW component under verification is represented e.g., as source code, object files, library file, executable, or executable model.) integration and for software verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) are specified
• O2 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 with specified 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 verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results are recorded
• O3 Software components (Software component = Software component in design and implementation-oriented processes: The software architecture decomposes the software into software components across appropriate hierarchical levels down to the lowest-level software components in a conceptual model. Software component in verification-oriented processes: The implementation of a SW component under verification is represented e.g., as source code, object files, library file, executable, or executable model.) are integrated up to a complete integrated software, the integration is verified with specified 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 verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) results are recorded
• O4 Integrated software is verified with specified 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 results of software verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) are recorded
• O5 Horizontal traceability is established on all levels

BP3 Specify and perform the verification measures for software. ( O1, O4 )

Specify and perform 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.) suitable to provide evidence of compliance of the integrated software with the software requirements. 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.

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 Establish horizontal traceability. ( O5 )

Ensure horizontal traceability from software requirements, software architecture and detailed design to corresponding 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.
Note 3: Horizontal traceability supports consistency, impact analysis and verification (Verification = Verification is confirmation through the provision of objective evidence that an element fulfils the specified requirements.) coverage demonstration for a respective V-model level.

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 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.