Name: Khalid Mehmood

Admission No: 9465

Semester: 3rd
Section:
Assignment No: 1st
Assignment Title: Elicitation Technique

Signature: Marks:
Requirement Elicitation Techniques:
Requirement elicitation is the practice of collection the requirement of a system from
users. It can be successful only through an effective customer-developer partnership. It
is needed to know what the users really need.
There are a number of requirements elicitation methods. Few of them are listed below –

1: Interviews:
Objective of conducting an interview is to understand the customer’s expectations
from the software.
Interviews maybe be open ended or structured.
1. In open ended interviews there is no pre-set agenda. Context free questions may
be asked to understand the problem.
2. In structured interview, agenda of fairly open questions is prepared. Sometimes a
proper questionnaire is designed for the interview.

2. Brainstorming Sessions:
 It is a group technique
 It is intended to generate lots of new ideas hence providing a platform to share
views
 A highly trained facilitator is required to handle group bias and group conflicts.
 Every idea is documented so that everyone can see it.
 Finally a document is prepared which consists of the list of requirements and their
priority if possible.

3: Questionnaires:
Leading a survey is an incredible method to find solutions to questions you can’t answer
by yourself.

Questionnaires take into consideration data to be evoked from numerous individuals,

which is vital if the venture has several partner

4: Prototyping:
Prototyping is a relatively latest procedure for gathering requirements.
In this technique, you gather initial requirements for making a basic sort of clarification –
known as a prototype.
Prototyping is a valuable device for business analysts to decide whether the solution
being created is actually what the stakeholder’s demand.

5: Document Analysis:
Document analysis is an extremely valuable requirements elicitation method which is
generally utilized in the IT industry.
This method is particularly significant when you are rolling out an improvement to a
current structure like an upgrade or change request. Document analysis includes
investigating down all the current documentation identified with a processor the system.
6: Facilitated Application Specification Technique:
Its objective is to bridge the expectation gap – difference between what the developers
think they are supposed to build and what customers think they are going to get.
A team oriented approach is developed for requirements gathering.
Each attendee is asked to make a list of objects that are-
1. Part of the environment that surrounds the system
2. Produced by the system
3. Used by the system

7: Quality Function Deployment:

In this technique customer satisfaction is of prime concern, hence it emphasizes on the
requirements which are valuable to the customer.

8: Use Case Approach:

This technique combines text and pictures to provide a better understanding of the
requirements.
The use cases describe the ‘what’, of a system and not ‘how’. Hence they only give a
functional view of the system.

9. Reverse Engineering
Is this a last resort or starting point? When a migration project is not having enough
documentation of the current system, reverse engineering will determine what system
does? It will not determine what the thing went wrong with the system and what a
system must do?

10. Survey
When gathering information from many people: to many to interview with time
constraints and less budget: a questionnaire survey can be used. The survey insists the
users to choose from the given options agree / disagree or rate something. Do not think
that you can make a survey on your own but try to add meaningful insight in it. A well
designed survey must give qualitative guidance for characterizing the market. It should
not be utilized for prioritizing of requirements or features.