At a glance
- Ref
- SR-05
- Process
- System Definition and Realisation
- Basis
- series-structure
- Source
- Public abstract, process list
- Evidence
- 3 items
- Gaps
- 2 common
Evidence to keep
- System Definition and RealisationThe integration plan and the as-built configuration
- System Definition and RealisationThe verification cases and their results
- System Definition and RealisationThe defect log with the fix and the retest
Questions before you sign
- What configuration was tested?
- Which requirement has no passing case?
- What failed, and what changed before the retest?
The practice, in our words
Integrate the elements into the system and verify it against the requirements baseline. Verification shows the system was built right; validation, in the next unit, shows the right system was built.
What it means in a VSE
Write the integration order and the verification cases before integration starts. Record the result of each case with the date, the configuration tested and the person who ran it. A failure is evidence too, if the fix and the retest are recorded.
In a firm of 25 people or fewer, integrate and verify the system has to earn its time. The test for SR-05 is not whether the team understands it but whether the artefact exists at the end of the project. Shrink the meeting. Shrink the document. Keep the record.
How to evidence it
Attach the artefacts above to the Integrate and verify the system row with the project name, the owner and the date. The anchor for SR-05 is The integration plan and the as-built configuration. A named person must produce it on request.
For SR-05, the reviewer will sample one live decision and ask for The verification cases and their results. No artefact, no evidence. A file that depends on one person's mailbox is not a file for integrate and verify the system.
What an assessor samples
An assessor reads the integrate and verify the system practice, asks for its evidence and tests one project against it. For SR-05, the useful sample is the most recent project that used the practice, not the best one. A reconstruction written for the visit is a finding for SR-05 if the practice cannot be shown to have happened when it mattered.
Common gaps
- Verification cases written after the result was known
- A pass recorded with no configuration identified
Where the draft fits
The public abstract places integrate and verify the system inside one of the four processes the Intermediate profile covers. For SR-05, the draft clause numbering and wording are not public, so this page cites Public abstract, process list and does not quote the draft. The basis label for SR-05 says whether the practice is stated in the public record, named as a process in the series, or our reading.
Related practices
Source for this page: Public abstract, process list. Open the record and compare it with the SR-05 statement above. Retrieved 2026-10-22.