Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Determine how the elicitation notes will be taken (manually, audio, video, by whom…) Elicitation Techniques Existing Systems Interviews. Brainstorming Joint ...
Typology: Schemes and Mind Maps
1 / 125
This page cannot be seen from the preview
Don't miss anything!
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Table of Contents
Elicitation Techniques
When people talk, listen completely. Most people neverlisten.
1
[1] Ernest Miller Hemingway (1899-1961)
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Elicitation Techniques
Elicitation techniques
background reading
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Comparison of Data-Gathering Techniques
1
[1] Preece, Rogers, and Sharp “Interaction Design: Beyond human-computer interaction”, p
Day-to-day work will
differ from documented
procedures
No time commitment
from users required
Quantitative
Learning about
procedures,
regulations, and
standards
Studyingdocumentation
Very time consuming. Huge amounts of data
Observing actual work gives insight that other techniques cannot give
Qualitative
Understanding context
of user activity
Naturalisticobservation
Possibility of dominant
characters
Highlights areas of
consensus and
conflict. Encourages
contact between
developers and users
Some quantitative but mostly qualitative data
Collecting multiple
viewpoints
Focus groups andworkshops
Time consuming.
Artificial environment
may intimidate
interviewee
Interviewer can guide
interviewee.
Encourages contact between developers
and users
Some quantitative but mostly qualitative data
Exploring issues
Interviews
The design is crucial.
Response rate may be
low. Responses may not be what you want
Can reach many
people with low
resource
Quantitative and
qualitative data
Answering specific
questions
Questionnaires
Minus
Plus
Kind of data
Good for
Technique
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Analysis of Existing Systems (1)
Useful when building a new improved version of an existingsystem
Important to know:
supposed to be used, and how we would like to use it
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Analysis of Existing Systems (2)
Why analyze an existing system?
new system if it is too different or does not do what they want (risk ofnostalgia for old system)
common activities, relative importance of tasks/features
do not currently work well)
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Observation and Related Techniques (1)
Observation
Ethnography also attempts to discover social, human, andpolitical factors, which may also impact requirements
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Observation and Related Techniques (2)
Can be supplemented later with questionnaires
(confirmation)
statistical significance!), e.g.:
How often do you use feature X?
What are the three features you would most like to see?
Can be supplemented later with interviews
questions require more detailed answers
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Ethnography – Overview (2)
Useful to discover for example
Less useful to explore political factors
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Ethnography – Example (1)
Sommerville et al. were involved in a project where they hadto elicit the requirements of an air traffic control system
They observed the air traffic controllers in action with theexisting system
Surprising observations
the intention of fixing them later
constant warnings
Incorrect conclusion
More accurate observation
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Interviews (1)
Requires preparation and good communication management
promising leads
Interview as many stakeholders as possible
Ask problem-oriented questions
real requirements. Example:
vs.
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Interviews – Planning and Preparation
Important to plan and prepare interviews
effective interview
(work tasks, attitude...)
by whom…)
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
SEG3101 (Fall 2010).
Requirements Elicitation Techniques
Interviews – Session
Make the interviewee comfortable and confident
Be polite and respectful!
Adjust to the interviewee
Interview several people at once to create synergy
Try to detect political aspects as they may influence the saidand the unsaid
Existing Systems
Interviews
Brainstorming
Joint Application Design
Prototyping
Use Cases
