Clause 6.3.3.7: Manage stakeholder needs and requirements
The process obtains explicit agreement from the designated stakeholders, maintains traceability from the requirements to the stakeholders and their needs, and provides the key artefacts and information items for baselines.
What clause 6.3.3.7 asks
The process obtains explicit agreement from the designated stakeholders, maintains traceability from the requirements to the stakeholders and their needs, and provides the key artefacts and information items for baselines. The information items can include the stakeholder requirements specification, the concept of operations and the system operational concept. The requirements repository is a key artefact in its own right.
Why it matters
Agreement can be partial: stakeholders may agree to subsets, and conflicts can remain in the stakeholder set as long as they are recorded. The clause distinguishes agreement on stakeholder requirements from agreement on system requirements. The traceability and the baseline are what let the project show that the agreed set is the set being built.
No clause level change is public for this unit; the DIS keeps the title and scope, and the requirement text is not released.
What good looks like
Record who agreed to what, including the subsets and the open conflicts. Baseline the set and the repository. Keep the traceability from each requirement to its stakeholder and need. Revisit the agreement when a change is proposed.
Evidence an assessor asks for
The assessor will ask who agreed the set and which version is baselined. A document approval with no version is not a baseline.
- Agreement record Each stakeholder, the subset agreed and any open conflict
- Traceability matrix The links from each requirement to its stakeholder and need
- Baseline record The baselined information items and the repository, with the version and date
- Repository index The location of the requirements and the source documents behind them
Where it commonly fails
- Agreement is recorded as a meeting attendance list
- The repository is a folder of spreadsheets with no version control
- Open conflicts are removed from the minutes so the set looks agreed
What to do before the revision
Record the agreement and the conflicts in the same document. A clean record with no conflict usually means the hard conversation did not happen.
Read across
- 6.3.1 Purpose: stakeholder needs and requirements definition
- 6.3.3.6 Analyze stakeholder requirements
- 6.4.3.5 Manage system or software requirements
- 6.6.2.2.2 Configuration identification
← 6.3.3.6 Analyze stakeholder requirements 6.4.1 Purpose: system requirements definition →
Source for clause 6.3.3.7: ISO/IEC/IEEE 29148:2018, Clause 6.3.3.7, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.