Clause 6.3.3.2: Prepare for stakeholder needs
Preparation has four tasks.
What clause 6.3.3.2 asks
Preparation has four tasks. Identify the stakeholders with an interest in the system across its life cycle, including representatives from each class and more than one level, because a single class or level gives a biased picture. Define the strategy for eliciting needs and transforming them into requirements, including how opposing interests will be handled and whether variants are needed. Identify the enabling systems or services, such as elicitation tools and repositories. Obtain access to them.
Why it matters
The clause is explicit about bias: information from one class or one level is likely to be partial. It also expects the strategy to handle disagreement, not to assume consensus. Variants of a requirement are a legitimate outcome when stakeholders genuinely need different behaviour.
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
Build the stakeholder map and the elicitation plan together. For each class, name the representative, the method and the date. Record the conflict approach before the first difficult meeting, not during it.
Evidence an assessor asks for
The assessor will look for a class or level that was never consulted. The map makes the omission visible.
- Stakeholder map Classes, representatives, levels, interests and the elicitation method for each
- Elicitation plan The methods, dates, participants and the record each session will produce
- Conflict approach How opposing needs will be surfaced, negotiated and recorded
- Enabling tools The repositories and tools, with the access confirmed
Where it commonly fails
- Only the buyer and the project team are consulted, so the operator and maintainer needs are missing
- A workshop is held with nine people from the same department
- Opposing needs are smoothed over in the minutes and reappear at acceptance
What to do before the revision
Add a level column to the stakeholder map: executive, management, operational. If every representative is at one level, the map is incomplete.
Read across
- 5.2.2 Stakeholders
- 6.3.1 Purpose: stakeholder needs and requirements definition
- 6.3.3.3 Define stakeholder needs
- 6.3.3.7 Manage stakeholder needs and requirements
← 6.3.1 Purpose: stakeholder needs and requirements definition 6.3.3.3 Define stakeholder needs →
Source for clause 6.3.3.2: ISO/IEC/IEEE 29148:2018, Clause 6.3.3.2, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.