DesignationISO/IEC/IEEE DIS 42703
Stage40.99, DIS approved for FDIS
Planning date, an estimate13 Sep 2027
Published source todayIEEE Std 7003-2024
6.5Clause
Stakeholder identification

Outcomes

IEEE Std 7003-2024, Clause 6.5Carried into ISO/IEC/IEEE DIS 42703Retrieved 20 October 2026

The team has a stakeholder reference set that is used across the life cycle, with types, attributes and protected attributes identified.

What clause 6.5 asks

The step succeeds when the set is complete, versioned and in use. Every stakeholder has a type. Every attribute has a source. Every protected attribute has a basis and a guard. The data and risk leads hold the same version. Where protected attributes are present, the team also examines its own makeup and knowledge, because those shape what it notices.

Why it matters

The outcome is a set that is actually used, not a list that is filed. The test is whether the data map, the evaluation and the risk assessment all refer to the same reference set and version. The clause also asks the identification team to reflect on itself when protected attributes are in play, because the team's own assumptions can shape which attributes are seen and how they are described.

What good looks like

At the end of the step, run three checks. First, every stakeholder has a type. Second, every attribute has a source, inherent or context. Third, every protected attribute has a basis and a protection step. Then confirm that the data lead and the risk lead have the current version. Record the self-reflection on the identification team where protected attributes are present, including any competence gap and how it was addressed.

Evidence an assessor asks for

The assessor will ask the data lead which stakeholder version the map used. If the answer is vague, the set is not being used.

  • Reference set The complete set, with type, attributes and protection status for every entry
  • Use confirmation The data and risk leads' confirmation that they hold the current version
  • Self-reflection record The team's composition and competence, and any gap that was addressed
  • Handover note What the next step needs from the set

Where it commonly fails

  • The set is filed and never referenced again
  • Some stakeholders have no type
  • The team's own composition is never considered

What to do before publication

Confirm the handover to clauses 7 and 8 before closing the step. The set is only an outcome when the next steps use it.

Read across

← 6.4 Actions7.1 Purpose →

Full register / The dates / Free scope check