SWE.4 SW Unit Verification

Carry out SWE.4 process according to ISO 29119.

SW Unit Verification Management

For testing, a software unit verification strategy needs to be planed, including following necessary items.

  • Define verification objects (Items, Scope)
  • Define the way to cover specific requirement regarding verification, MISRA, ISO 26262, etc. (Risk Management, Schedule, RACI)
  • Define the method for test case, and test data development (Postive/Negative case, Equivalence paratitioning case, Boundary Value Analysis)
  • Define the method and tools for static verification and for reviews.
  • Define test environment regarding each test method (Dynamic Testing).
  • Define the test coverage (C0, C1, MC/DC) in relation to project and release plan.
  • Define the entry and exit criteria (Static analysis, Code review, Unit test).
  • Define the approach for handing of failed test, failed static verifications and review finding. (Deviation Stratergy)

SW Static Analysis

Set up the static analysis environment, like MathWork Polyspace.

https://www.mathworks.com/products/polyspace.html

Perform software detailed design verification, improve the defect code by code review, make the project meet the coding standards, such as MISRA C, reconstruct the complex source code based on cyclic complexity.

Performs regression testing to see whether the software matches the software design.

SW Dynamic Testing

Set up the dynamic test environment, like Tessy.

https://www.razorcat.com/en/product-tessy.html

Execute the unit testing, and confirm the software functions meet software detailed design.
Summarize all test scripts, as well as test reports including bug tracking.
Performs regression testing to see whether the software matches the software design.