SR-07 · our practice ref · series-structure

Manage configuration and change

Practice SR-07 in the System Definition and Realisation group. The basis is series-structure, and the row asks for 3 pieces of evidence.

At a glance

Ref: SR-07
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 configuration item list with versions
System Definition and RealisationThe change records with approvals
System Definition and RealisationThe delivered baseline identifier

Questions before you sign

Which items are under configuration control?
What is the identifier of the delivered baseline?
Which change triggered a retest, and where is it?

The practice, in our words

Identify the configuration items, put them under control, and record every change with its approval and its effect on the baseline. Configuration management is what lets the team answer the assessor's question: what exactly did you deliver?

What it means in a VSE

Start with the items the acquirer will receive and the items the design depends on. Give each a version. A change record should say what changed, why, who approved it and which verification was repeated.

In a firm of 25 people or fewer, manage configuration and change has to earn its time. The test for SR-07 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 Manage configuration and change row with the project name, the owner and the date. The anchor for SR-07 is The configuration item list with versions. A named person must produce it on request.

For SR-07, the reviewer will sample one live decision and ask for The change records with approvals. No artefact, no evidence. A file that depends on one person's mailbox is not a file for manage configuration and change.

What an assessor samples

An assessor reads the manage configuration and change practice, asks for its evidence and tests one project against it. For SR-07, 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-07 if the practice cannot be shown to have happened when it mattered.

Common gaps

Versions in file names only
A change approved after the work was done

What changes from the 2019 report. For SR-07, 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 manage configuration and change inside one of the four processes the Intermediate profile covers. For SR-07, 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-07 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-07 statement above. Retrieved 2026-10-22.