IN4MATX 113 Lecture Notes - Lecture 2: Requirements Elicitation, Stakeholder Analysis
Stakeholders- (Preview) SRS: Systems/software, requirements, specifications document
- What are the two parts of requirements elicitation?
Ā· Domain understanding
Ā· Elicitation
- What are some popular elicitation techniques?
Ā· Questionnaire
Ā· Survey
Ā· Interview
- Stakeholder:
Ā· Stakeholder is a group/individual has something to with the system (both success and
failure of project)
Ā· Basic types: system engineers, users, managers of system end-users, external regulators,
domain experts, developers etc.
- CRACK: Collaborative, representative, accountable, committed, knowledgeable
- Often conflict with each other
Ā· Hierarchical dissonance
- Identifying stakeholders:
Ā· Software development phases
Ā· Reference list (framework for stakeholder model)
Ā· Business/operational context
Ā· Goals
- Stakeholder analysis:
Ā· Motivation: For the project? How involved they want to be.
Ā· Authority:
Ā· Relation to other stakeholders: conflict?
Ā· Level of expertise:
Ā· Their expectations:
Ā· Your expectations of them: available for interviews? Fill out a questionnaire? Just
there/no expectations?
Ā· Location/ availability: remote?
- Onion stakeholder model
Ā· Usually 4 or 5 layers, center out
1. Product or solution
2. System (business system)
3. Containing system (The business)
4. Wider environment
5. Outer layer for stakeholders who do not map to other layers
- Stakeholder matrix
- Specification and documentation
Ā·
find more resources at oneclass.com
find more resources at oneclass.com
