SR-06 · our practice ref · public-record

Validate against the acquirer's needs

Practice SR-06 in the System Definition and Realisation group. The basis is public-record, and the row asks for 3 pieces of evidence.

At a glance

Ref: SR-06
Process: System Definition and Realisation
Basis: public-record
Source: Public abstract, 1.1 Fields of application
Evidence: 3 items
Gaps: 2 common

Evidence to keep

System Definition and RealisationThe validation plan and the acceptance criteria
System Definition and RealisationThe acquirer's recorded acceptance
System Definition and RealisationThe trace from the validation back to the stated needs

Questions before you sign

Which stated need does this test prove?
Who from the acquirer saw it, and what did they sign?
What changed since the needs were stated?

The practice, in our words

Validate the delivered system against the acquirer's stated needs, not only against the requirements the firm wrote. Validation closes the loop between what was asked for and what was built.

What it means in a VSE

Use the acquirer's own acceptance criteria and, where possible, the acquirer's own people. Record what they did, what they saw and whether they accepted. If the needs changed during the project, say so and show the change record.

In a firm of 25 people or fewer, validate against the acquirer's needs has to earn its time. The test for SR-06 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 Validate against the acquirer's needs row with the project name, the owner and the date. The anchor for SR-06 is The validation plan and the acceptance criteria. A named person must produce it on request.

For SR-06, the reviewer will sample one live decision and ask for The acquirer's recorded acceptance. No artefact, no evidence. A file that depends on one person's mailbox is not a file for validate against the acquirer's needs.

What an assessor samples

An assessor reads the validate against the acquirer's needs practice, asks for its evidence and tests one project against it. For SR-06, 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-06 if the practice cannot be shown to have happened when it mattered.

Common gaps

Validation replaced by a demonstration the team designed
Acceptance recorded without the acquirer's name

What changes from the 2019 report. For SR-06, system definition and realisation holds most of the evidence. The transition work is to keep the record as the work proceeds, not to reconstruct it at the end.

Where the draft fits

The public abstract places validate against the acquirer's needs inside one of the four processes the Intermediate profile covers. For SR-06, the draft clause numbering and wording are not public, so this page cites Public abstract, 1.1 Fields of application and does not quote the draft. The basis label for SR-06 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, 1.1 Fields of application. Open the record and compare it with the SR-06 statement above. Retrieved 2026-10-22.