SWE.4 Software Unit Verification#
The purpose is to verify that software units are consistent with the software detailed design
Process outcomes#
Verification measures for the software unit verification are specified.
Software unit verification measures are selected according to the release scope, including criteria for regression verification.
Software units are verified using the selected verification measures, and results are recorded.
Consistency and bidirectional traceability are established between verification mesaures and software units; and bidirectional traceability are established between verification results and verification mesaures.
Results of the software unit verification are summarized and communicated to all affected parties.
Base practices#
SWE.4.BP1: Specify software unit verification measures
|
status: valid
|
||||
Specify verification measures for each software unit defined in the software detailed design, including - pass/fail criteria for verification measures, - entry and exit criteria for verification measures, and - the required verification infrastructure. Note Examples for unit verification measures are static analysis, code reviews, and unit testing. Note Static analysis can be done based on MISRA rulesets and other coding standards. |
|||||
SWE.4.BP2: Select software unit verification measures
|
status: valid
|
||||
Document the selection of verification measures considering selection criteria including criteria for regression verification. The documented selection of verification measures shall have sufficient coverage according to the release scope. |
|||||
SWE.4.BP3: Verify software units
|
status: valid
|
||||
Perform software unit verification using the selected verification measures. Record the verification results including pass/fail status and corresponding verification measure data. Note See SUP.9 for handling of verification results that deviate from expected results |
|||||
SWE.4.BP4: Ensure consistency and establish bidirectional traceability
|
status: valid
|
||||
Ensure consistency and establish bidirectional traceability between verification measures and the software units defined in the detailed design. Establish bidirectional traceability between the verification results and the verification measures. Note Bidirectional traceability supports consistency, and facilitates impact analysis of change requests, and demonstration of verification coverage. Traceability alone, e.g., the existence of links, does not necessarily mean that the information is consistent with each other. |
|||||
SWE.4.BP5: Summarize and communicate results
|
status: valid
|
||||
Summarize the results of software unit verification and communicate them to all affected parties. Note Providing all necessary information from the test case execution in a summary enables other parties to judge the consequences. |
|||||