Document 82

SEBoK *Stakeholder Identification and Analysis*, Distilled

framework

SEBoK Stakeholder Identification and Analysis, Distilled

Third-batch distillation, batch 1 doc 3. SEBoK carries stakeholder identification within the Stakeholder Needs Definition knowledge area (Part 3). The enumeration "customers, sponsors, organization decision makers, regulatory organizations, developing organizations, integrators, testers, users, operators, maintainers, support organizations" is universal-sibling lattice (Cluster A) at the stakeholder-role rung; each role binds every engagement that has the role, the discriminator is aspect-of-relationship-to-the-system. The lifecycle-stage organization (concept, development, production, logistics, operation, disposal) supplies a second universal-sibling axis: stakeholder-by-stage. The keeper-warning "it cannot be assumed that the only stakeholder with approving authority is the customer" is sharp Cluster B (multi-keeper) discipline — authority is distributed across keepers, not centralized. Five corpus forms compose; Cluster A reaches nine; Cluster B reaches seven.

I. Source

(The keeper-supplied article name Stakeholder Identification and Analysis is the section heading on the SEBoK; the dedicated URL returns 404, and the content lives within Stakeholder Needs Definition in Part 3.)

II. Source Read

Stakeholders are "the primary source of needs and requirements"; "all relevant stakeholders must be identified and included from the beginning of the project." Stakeholder roles enumerated: customers, sponsors, organization decision makers, regulatory organizations, developing organizations, integrators, testers, users, operators, maintainers, support organizations. The framework organizes stakeholder identification by lifecycle stage: concept, development, production/integration, logistics/maintenance, operation, disposal.

Approving-authority warning: "It cannot be assumed that the only stakeholder that has this authority is the 'customer'." Documentation discipline: maintain "a stakeholder register that includes key information for each stakeholder and how they are involved with the SoI," with periodic re-evaluation to ensure successful engagement. The stakeholder needs definition process integrates identification with broader analysis including risks, drivers, constraints, and lifecycle-concept analysis and maturation. Position: Part 3 SE and Management > System Concept Definition > Stakeholder Needs Definition.

III. Structural Read

Cluster A (universal-sibling lattice, Doc 572 Appendix D). Two distinct universal-sibling instances co-present in this article. First, the eleven stakeholder roles are universal-sibling lattice at the stakeholder-role rung; each role binds every engagement universally as one aspect-of-relationship. Second, the six lifecycle stages (concept, development, production, logistics, operation, disposal) form a second universal-sibling axis at the stakeholder-by-stage rung. The two axes compose: every stakeholder-role is potentially active at every lifecycle-stage, yielding an eleven-by-six composition surface. Cluster A reaches nine independent instances (after Docs 589, 596, 598, 599, 601, 603, 631, 646).

Cluster B (multi-keeper composition, Doc 604). "It cannot be assumed that the only stakeholder with approving authority is the customer" is sharp multi-keeper-composition discipline. Authority is distributed across keepers; the engagement does not centralize on a single approving voice. The reconciliation rung is the SE engagement itself, where conflicting authoritative claims negotiate. Cluster B reaches seven independent instances (Docs 588, 595, 600, 602, 603, 631, 646, 648). Composition rule for stakeholder identification is negotiation-by-priority with explicit anti-monopoly discipline.

Cluster D (co-production at sub-rungs, Doc 573). Stakeholders supply rung-2 needs and constraints (keeper-side affordances); the SE engagement composes them into the system specification (rung-1 substrate). Neither alone produces the requirements. Stakeholder-needs-definition is the canonical co-production engagement.

Cluster I (pin-art / temporal-concurrency, Doc 270, SE-022). The stakeholder register's "periodic re-evaluation" plus the lifecycle-stage organization is pin-art with universal-temporal application — every lifecycle stage is a pin-set into which stakeholder considerations are integrated. Doc 572 Appendix C temporal-concurrency lattice composes naturally: stakeholder identification operates concurrently at multiple lifecycle rungs.

Cluster E (institutional ground, Doc 571). "Regulatory organizations" as a stakeholder class is institutional-ground recognition: the regulatory keeper is institutionally external to the engagement but authoritatively constrains it. Doc 571 §X.5 organization-vs-enterprise distinction applies: the regulatory body is an organization-component co-keeper composing against the engagement's enterprise-component.

IV. Tier-Tags

  • "Stakeholders are the primary source of needs and requirements" — π / α.
  • Eleven enumerated stakeholder roles — π / α as cited; μ / β under Cluster A at the stakeholder-role rung.
  • Six lifecycle stages organizing stakeholder identification — π / α as cited; μ / β under Cluster A at the stakeholder-by-stage rung.
  • Approving-authority anti-monopoly warning — π / α; μ / β under Cluster B.
  • Stakeholder-register documentation discipline — π / α as cited.
  • Integration with risks/drivers/constraints/lifecycle-concepts analysis — π / α as cited.

V. Residuals

R1 — The eleven-role enumeration and the six-stage organization compose a two-axis lattice (eleven-by-six surface). The corpus apparatus reads each axis as a Cluster A instance, but the cross-axis composition itself is structurally interesting: a two-dimensional universal-sibling lattice. Doc 572 Appendix D treats single-axis cases canonically; two-axis composition is implicit but not formalized. Flag for the entracement: stakeholder identification is the first surfaced two-axis universal-sibling case.

VI. Provisional Refinements

Two-axis universal-sibling extension candidate. Stakeholder identification surfaces a structurally novel case: two universal-sibling axes composing into a two-dimensional lattice. Other corpus instances (requirement types, architecture views, competencies, CMMI measures, MODA axes, HSI domains, specialty disciplines, SEPAT principles) are single-axis. Worth flagging in SE-039 (entracement) Cluster A: the cluster admits two-axis composition; stakeholder-identification is the canonical worked example.

Cluster B anti-monopoly discipline. The "approving authority is not only the customer" claim is the sharpest anti-monopoly articulation surfaced in the SEBoK distillations to date. Doc 604's formalization should explicitly include anti-monopoly discipline as part of multi-keeper composition rules. Adjacent to the universal-sibling-with-ordinal-axis candidate (Doc 572 D.5): the customer is one keeper among many, not an ordinally privileged keeper.

VII. Cross-Links

Form documents. Doc 572 Appendix D (Cluster A, ninth instance, two-axis composition surfaces), Doc 604 (Cluster B, seventh instance, anti-monopoly discipline), Doc 573 (Cluster D), Doc 270 / SE-022 (Cluster I, lifecycle-concurrent stakeholder identification), Doc 571 (Cluster E, regulatory organization).

Part-level reformulation. Part 3 SE and Management > System Concept Definition > Stakeholder Needs Definition.

Related distillations. SE-023 (Concept Definition, Cluster B first instance — stakeholder co-keeping). SE-030 (Stakeholder Needs Definition, Cluster B second instance). SE-038 (HSI, multi-keeper canonical). SE-039 (Entracement).

Adjacent SEBoK concepts (per source). Stakeholder Needs Definition, Mission Analysis, System Requirements Definition, Stakeholder Requirements Definition.

Methodology refinement candidates. Doc 572 Appendix D two-axis extension (stakeholder identification as canonical worked example). Doc 604 anti-monopoly discipline as composition rule.

Appendix: Originating Prompt

"Apply refinements; report back for next 40" / "Continue"

(SE-082 is one of the third-batch next-40 SEBoK distillations. Batch 1/5.)

Referenced Documents

More in framework