Quiz Entry - updated: 2026.07.14
What is the main goal of stakeholder identification in requirements elicitation?
To map every party with an interest in or influence over the system, so no perspective is missed and it's clear who is in charge of what.
Stakeholder identification maps out all parties who have an interest in or influence over the system being developed. This includes:
- Direct users (local users, regular users, potential users)
- Indirect stakeholders (public agencies, civil society organizations)
- Business interests (economic interests, other businesses)
- Authorities and regulators
- Professional interests
Proper stakeholder identification ensures no important perspectives are missed and responsibilities are clear.
Common stakeholder categories:
| Category | Examples |
|---|---|
| Primary | End users, system administrators |
| Secondary | Management, trainers, maintainers |
| Tertiary | Regulators, auditors, legal |
| Negative | Attackers, competitors (for security requirements!) |
Tip: Missing a key stakeholder often leads to late-stage requirement changes - expensive!
Go deeper:
Project stakeholder (Wikipedia) — who counts as a stakeholder and how they are categorised by interest and influence.