Stakeholder
- •
- •
types
- •
end users — people who directly interact with the system in their daily work
- •
e.g., students accessing an e-learning system
- •
- •
system managers — people who manage and maintain the system
- •
e.g., IT staff managing servers and data backups
- •
- •
engineers / developers — technical parties who design and build the system
- •
e.g., the software house team developing the application
- •
- •
regulators / auditors — external parties ensuring the system complies with regulations and standards
- •
e.g., LLDIKTI or internal campus auditors
- •
- •
support staff — provide technical assistance and support to users
- •
e.g., helpdesk staff receiving and resolving system problem reports
- •
- •
customer — uses or may use the organization’s products or services; does not necessarily sponsor the project
- •
business analyst — performs and coordinates business-analysis activities
- •
supplier — provides external products or services
- •
domain subject matter expert — contributes specialized knowledge of the business domain
- •
implementation subject matter expert — contributes specialized knowledge about implementing solution components
- •
project manager — coordinates delivery while balancing scope, schedule, budget, resources, quality, and risk
- •
sponsor — initiates or authorizes the initiative and provides authority over funding or scope
- •
tester — evaluates whether the solution meets specified requirements and relevant quality expectations
- •
- •
- •
role in requirements engineering
- •
primary sources of requirements during Requirements Elicitation
- •
involved in Requirements Validation
- •
each stakeholder has unique views and needs; elicitation approach must be tailored accordingly — see Interviewee Types
- •
- •
- •
- •
Role in analysis
- •
stakeholders can supply requirements, assumptions, and constraints
- •
- •
- •