1. Purpose and scope
Unit work is where most code is written and most defects are introduced, and it is also where evidence is easiest to produce automatically. The detailed design states what each unit does, its interfaces and its behaviour, linked to the architecture component it belongs to. Units implement the design. Verification then shows that each unit meets its detailed design and the criteria in the unit verification strategy, using a mix of static analysis, coding rule checks, reviews and unit tests with structural coverage measured to the level the strategy sets.
Assessors check that the strategy exists and was followed, that criteria were defined before verification and not adjusted to fit results, that every unit in the release has recorded results, that static analysis findings were resolved or justified, and that results are traced to the detailed design and kept with the baseline they belong to. Automating analysis and tests in continuous integration makes all of this a by-product of normal development.
In scope: software detailed design, software units, static analysis, coding rule checking, unit tests, coverage measurement, unit verification results, problem reports for unit defects and, where in scope, hardware detailed design and its verification. Out of scope: integration of units into components and the software, which belongs to Integration, Software & System Verification and Validation.
13 more sections for registered members.