Requirement Elicitation and Analysis

Requirement elicitation is the practice of collecting the requirements of a system from users, customers and other stakeholders.
This practice this practice is also sometimes referred to as "Requirement Gathering".

Requirement Elicitation Methods:

There are a number of requirement elicitation methods:

• Interviews
• Brainstorming Session
• FAST
• Quality Function Deployment
• Uscase Approach

Interviews: In this requirement gathering team Conduct an interview session with

• Entry level personal
• Middle level stakeholder
• Manager
• Users of the software(most important)

In that interview session team asks these types of questions.
Questions before successful deployment of project

• Any problem with existing system?
• Any calculation errors?
• How are the previous system works?
• Any additional functionality
• Any specific problem
• User requirements

Questions after installation or in Maintenance Phase

• Any calculation error
• Any additional functionality
• Goal of proposed product

Brainstorming Sessions

Brainstorming is a group creativity technique by which efforts are made to find a conclusion for a specific problem by gathering a list of ideas spontaneously contributed by its members.
It creates an atmosphere which is free from criticism and judgement and allow members to subject and explore ideas.
Mainly group of "4-10 people(depend on project and Organization )" attend the brainstorming session.

Brainstorming has two Phases:

Generation Phase: Offers as many ideas as possible and no Merits and demerits of the ideas as discussed. Consolidation Phase: Ideas are discussed, revised and organised.

Facilitated Application Specification Technique(FAST)

This approach encourages the creation of a joint team of customers and developers who works together to

Fast Goal

• 1- identify the problem
• 2- solution requirements
• 3- Propose elements of solutions
• 4- Negotiate different approach

• A Meeting is conducted at the neutral site and attended by both software engineers and customers.
• Rules for preparation and participation established.
• An Agenda is suggested that is formal enough to cover all important but informal enough to enough encourage the free flows of ideas.
• A Facilitator(can be a, customer, developer, or an outsider) controls the meeting.

    CLICK HERE TO Download This PDF NOTES