Clause 6.6.2.2.2: Configuration identification

Current editionISO/IEC/IEEE 29148:2018, Clause 6.6.2.2.2Edition 3 at DIS ballotNo public change recorded

The process decides which system elements and information items count as configuration items, establishes identifiers and attributes, and defines the baselines through the life cycle.

What clause 6.6.2.2.2 asks

The process decides which system elements and information items count as configuration items, establishes identifiers and attributes, and defines the baselines through the life cycle. The operational concept and the stakeholder, system, software and element requirement sets are information items under configuration control and need unique identifiers. The four common baselines are functional, allocated, developmental and product. The functional baseline is the agreed system requirement specification and its interface definitions; the allocated baseline is the reviewed system element requirements; the developmental baseline is the evolving configuration; the product baseline is the completed system.

Why it matters

The baseline names give a project a shared language for what is approved. The clause makes the requirements information items configuration items, which is the step many projects skip. Without it, a requirement can be changed without a version and no one can tell which set was approved.

What good looks like

List the configuration items, including the concept and the requirement specifications. Assign identifiers and attributes. Define each baseline with its approval authority. Record the baseline in the configuration management plan.

Evidence an assessor asks for

The assessor will ask which baseline is approved and who approved it. A folder called baseline is not a baseline.

• Configuration item list The system elements and information items under control, including the concept and requirement specifications
• Identifier scheme The identifiers and attributes for each item, with the rule against reuse
• Baseline definitions Functional, allocated, developmental and product baselines, with the approval authority for each
• Configuration plan The plan that names the items, the baselines and the change authority

Where it commonly fails

• The requirement specifications are not configuration items, so changes have no version
• The baseline is defined but the approval authority is not named
• The identifiers are reused after a document is retired

What to do before the revision

Put the concept and the four requirement specifications on the configuration item list first. They are the items the rest of the process depends on.

Read across

• 5.2.8 Requirements attributes
• 6.4.3.5 Manage system or software requirements
• 6.6.2.2.3 Configuration change control
• 7 The required information items

← 6.6.2.1 Change management 6.6.2.2.3 Configuration change control →

Full register / Revision record