SRE.lec#5 Req Elicitation

Software requirement
Engineering
Lecture #5
Content
 RE Process
Phase 1 : Requirement
Elicitation
 Requirement Elicitation
sources
Process
Technique
 Problems of This Phase
Phase 1: Requirement Elicitation
 Elicit means to gather, acquire, extract, and obtain, etc.
 Requirements elicitation means gathering requirements

or discovering requirements
 Different activities are involved in discovering the

requirements for the system
Basics of Knowledge Acquisition
 These are the sources of knowledge
acquisition
 Reading
 Asking
 Listening
 Observing
Requirements Elicitation Stages
 Objective setting
 Background knowledge acquisition
 Knowledge organization
 Stakeholder requirements
collection
Objective Setting
 Overall organizational objectives should

be established at this stage
 These include general goals of business, an

outline description of the problem to be
solved and why the system may be
necessary, and the constraints on the
system such as budget and schedule.
Background Knowledge Acquisition
 Requirements engineers gather and
understand background information.
 This includes information about the organization

where the system is to be installed, information
about the application domain of the system, and
information about any existing systems which are in use
and which may be replaced
Knowledge Organization
 The large amount of knowledge which has been
collected in previous stage must be organized and
collated.
 Identifying system stakeholders and their roles in

the organization, prioritizing the goals of the organization
and discarding domain knowledge which does not
contribute directly to the system requirements.
Stakeholder Requirements Collection
 It involves consulting system stakeholders to

discover their requirements and deriving
requirements which come from the application
domain and the organization which is acquiring the
system.
Specific Elicitation Techniques
 Interviews
 Scenarios and Use cases
 Observations and social
analysis
 Brain Storming
Interviews
 Direct conversations with stakeholders to
understand their needs and expectations.
 Interviews can be less effective because

they rely heavily on individual perspectives,
which may not capture the full range of
user needs and system requirements.
Types of Interviews
 Closed interviews
 The requirements engineer looks for answers to a pre-
defined set of questions
 Open interviews
 There is no predefined agenda and the requirements
engineer discusses, in an open-ended way, what
stakeholders want from the system
Interview Steps
1. Prepare
2. Conduct
3. Follow through
Prepare for the Interview
 Define the purpose and objectives
 Determine whether the interview should be conducted

by one person or a team
 Obtain background information

Conduct the Interview
 Introduce yourself (and your team); provide
information about role(s) in the interview process.
 Clarify purpose, time frame, and key objectives
 Identify interviewee’s main concerns
 Ask for and obtain relevant documentation
 Summarize findings and link to purpose

Follow Through
 Immediately after the interview, fill in your

notes; be sure to jot down impressions and
important ideas.
 Review any documentation received

from the interviewee
 Write an interview report, if necessary

Brain storming
 Brainstorming is a collaborative technique for

generating a variety of ideas in an open, judgment-
free environment.
 Encourages creativity and diverse ideas through
open collaboration.
 But More vocal participants may dominate, limiting
input from quieter members.
Brain storming
Scenarios and use cases
 Scenarios are examples of interaction sessions which describe how a
user interacts with a system.
 Use case define interactions between users and the system

to achieve specific goals..
This is a vending machine
Scenario Writing customer perspective
Actor: Customer
Precondition:
• The vending machine is in idle state waiting for the customer to put coin
Scenario:
• Customer will put the coin in the vending machine
• Vending machine check which coin it is.
• Vending machine drop the product into the box below
• Customer pick the product from the box
Postcondition:
• The vending machine is idle again and waiting for the next customer or the
same customer to put the money.
Scenario with Use case
Observation and Social Analysis
 Watching users interact with current systems or perform

tasks to identify pain points and areas for improvement.
 Actual work processes often differ from formal, prescribed processes.
 Use the Ethnography technique.

 Ethnography, simply stated, is the study of people in their own
environment using methods such as participant observation and face-
to- face interviewing.
Problems in Requirements Elicitation
 Problems of scope
 The boundary of the system is ill-defined
 Unnecessary design information may be given
 Problems of understanding
 Users have incomplete understanding of their needs
 Conflicting views of different users
 Problems of volatility
 Requirements evolve over time and hence there are some
requirements which are bound to change during the system
development process due to one reason or the other.

SRE.lec#5 Req Elicitation

Uploaded by

Copyright:

Available Formats

SRE.lec#5 Req Elicitation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRE.lec#5 Req Elicitation

Uploaded by

Copyright:

Available Formats

Software requirement

 Requirements elicitation means gathering requirements

 Different activities are involved in discovering the

 Background knowledge acquisition

 Overall organizational objectives should

 These include general goals of business, an

 This includes information about the organization

 Identifying system stakeholders and their roles in

 It involves consulting system stakeholders to

 Interviews can be less effective because

 Determine whether the interview should be conducted

 Obtain background information

 Clarify purpose, time frame, and key objectives

 Identify interviewee’s main concerns

 Ask for and obtain relevant documentation

 Summarize findings and link to purpose

 Immediately after the interview, fill in your

 Review any documentation received

 Write an interview report, if necessary

 Brainstorming is a collaborative technique for

 Use case define interactions between users and the system

 Watching users interact with current systems or perform

 Actual work processes often differ from formal, prescribed processes.

 Use the Ethnography technique.

You might also like