Requirement Elicitation Flashcards
(14 cards)
Requirements Elicitation
The process of seeking, capturing and consolidating requirements from available requirements sources
3 Requirement Sources
- Stakeholders
- Documents
- Systems in Operation
Stakeholders
People or organizations that (directly or indirectly) influence the requirements of a system. Exam ples of stakeholders are users of the system, operators of the system, developers, architects, customers, and testers.
Documents
Standards and legal documents, as well as domain- or organization specific documents, such as requirements documents and error reports of legacy systems.
Requirements Categorization According to Kano Model
- Dissatisfier (a must-be requirements)
- Satisfiers (a one-dimensional customer requirement)
- Delighters (an attractive requirement)
Dissatisfiers (Basic Factors)
Properties of the system that are self-evident and taken for granted (subconscious knowledge).
- must be fulfilled by the system in any case
- observation (Field observation, Apprenticing) and document-centric (system archeology, perspective-based reading) techniques are well suited for this
Satisfiers (Performance Factors)
Explicitly demanded system properties (conscious knowledge)
- Satisfiers can be well using survey techniques (interview, questionnaire).
Delighters (Excitement Factors)
System properties that the stakeholder does not know or expect and discovers only while using the system—a pleasant and useful surprise (unconscious knowledge)
- Creativity techniques are best suited to elicit delighters (Establishing innovations, Brainstorming, change of perspective, analogy technique)
Elicitation Techniques
(SCODS)
1. Survey Techniques
2. Creativity Techniques
3. Observation Techniques
4. Document-centric Techniques
5. Supporting Techniques
Survey Techniques
- Interview
- Questionnaire
Creativity Techniques
- Brainstorming
- Change of Perspective (etg; six thinking hats)
- Analogy
Observation Techniques
- Field Observation (Observation of the users at work)
- Apprenticing (executing the work of the user under their guidance)
Document-centric Techniques
- System Archeology - exploration of functionality of an existing system
- Perspective-based reading
- Reuse
Supporting Techniques
- Workshops
- Prototyping
a) Throw-away prototyping
b) Evolutionary prototyping