What are Requirements Elicitation?

panicyfewInternet and Web Development

Nov 18, 2013 (3 years and 9 months ago)

64 views

Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
1




What are Requirements
Elicitation?

Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
2




Objective


By the end of this unit, you will be able to




Define Requirements Elicitation


Elicitation Techniques


How to prepare for Requirements Elicitation


How to conduct Elicitation Activity


How to document Elicitation Results


How to confirm Elicitation results


Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
3




Elicitation is the act of obtaining language data from another person. To draw forth
or bring out, To call forth or bring out.


Elicitation Techniques:



Brainstorming



Document Analysis



Focus Groups



Interface Analysis



Interviews



Observation



Prototyping



Requirements workshop



Survey/Questionnaire


Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
4




Prepare for Requirement Elicitation


Purpose:


Ensure all needed resources are organized and scheduled for conducting the elicitation
activities.

Description:


Build a detailed schedule for a particular elicitation activity, defining the specific activities
and planned dates.


Inputs:

Business Need:



Solution Scope and Business Case



Stakeholder List, Roles and Responsibilities


Elements:



Clarify Specific Scope for the selected elicitation technique and gather any supporting
materials.



Schedule all resources (people, facilities, equipment)



Notify appropriate parties of the Plan


Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
5




Prepare for Requirement Elicitation

Techniques:


Brain storming

Document Analysis

Focus Groups

Interface Analysis

Interviews

Observation

Prototyping

Requirements Workshop

Survey/Questionnaire


Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
6




Prepare for Requirement Elicitation

Stakeholders:


All Stakeholders

Project Manager


Output:


Schedule Resources:
This includes the participants, the location in which the
elicitation activity will occur and any other resources that maybe required.


Supporting Materials:
Any materials required to help explain the techniques
used or perform them.

Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
7




Conduct Elicitation Activity

Purpose:


Meet with stakeholders to elicit information regarding their needs

Description:


The elicitation event takes place (brainstorming, focus groups, interviews,
observation, prototyping, requirements workshop) or elicitation is performed
(document analysis, interface analysis) or distributed (survey/questionnaire)

Inputs:


Business Need

Organizational Process Assets

Requirements Management plan

Schedule Resources

Solution Scope and Business Case

Supporting Materials

Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
8




Conduct Elicitation Activity

Elements:



Tracing Requirements

Capturing Requirement Attributes

Metrics


Techniques:



Brain storming

Document Analysis

Focus Groups

Interface Analysis

Interviews

Observation

Prototyping

Requirements Workshop

Survey/Questionnaire




Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
9




Conduct Elicitation Activity

Stakeholders:



Customer, Domain SME, End User, Supplier and Sponsor


Implementation SME, Operational Support, Project Manager, Supplier and
Tester,

Regulator


Output:




Elicitation Results: May include documentation appropriate to the technique
and capture the information provided by the stakeholder.


Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
10




Document Elicitation Results


Purpose:


Record the information provided by stakeholders for use in analysis.

Description:


For an elicitation event (brainstorming, focus groups, interviews, observation,
prototyping, requirements workshop) a summary of the output from the event
including issues is produced.

Input:


Elicitation results: Includes the information provided by stakeholders that will
be recorded and structured.

Elements:


Documentation can take number of forms, including:

Written documents describing the outcomes such as meeting minutes.

Visual or audio recordings

Whiteboards




Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
11




Document Elicitation Results

Techniques:





Brain storming

Document Analysis

Focus Groups

Interface Analysis

Interviews

Observation

Problem Tracking

Prototyping

Requirements Workshop

Survey/Questionnaire




Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
12




Document Elicitation Results

Stakeholders:


Business Analyst


Output:


Requirements stated: Described from the perspective of the stakeholder,
stated requirements describe the stakeholder’s need from the
sta步桯l摥牳' pers灥捴p癥v


pta步桯汤敲 Co湣e牮猺rfnc汵摥 iss略猠ide湴楦n敤eby th攠sta步k潬摥爬rris歳Ⱐ
assumptions, constraints and other related information.

Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
13




Confirm Elicitation Results


Purpose:


Validate that the stated requirements expressed by the stakeholder match
the stakeholder's understanding of the problem and the stakeholder’s
needs.

Description:


Some elicitation techniques benefit from reviewing the documented
outputs with the stakeholders to ensure that the analyst’s understanding
conforms to actual desires or intentions of the stakeholder.


Input:


Requirement stated, unconfirmed: Represent the business analyst’s
understanding of the stakeholders intentions.


Stakeholder concerns unconfirmed: Represent the business analyst’s
understanding of issues identified by the stakeholder, risks, assumptions,
constraints and other relevant information that may be used in business
analysis.

Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
14




Confirm Elicitation Results

Elements:


Refer to the description of the relevant technique for unique aspects of confirming
the results of the interview and observation techniques.

Techniques:

Interviews

Observation

Stakeholders:


Any stakeholder who has participated in other elicitation tasks may participate in
this task.


Output:


Requirements stated and confirmed: Identical to Requirements stated for all
practical purposes including use as an input to other tasks.


Stakeholder concerns confirmed: Identical to stakeholder concerns for all practical
purposes including use as an input to other tasks.


Search Engine Optimization

©
HiTech

Institute. All rights reserved.







Slide
15




Elicitation Techniques


Group Activity




You were recently hired as a Lead BA for a Software Development company XYZ.
After joining the company, you were handed over with a few documents. One of it
was “AS IS” and “TO BE” document. The project Manager briefs you on his project
plan and he mentioned that he has planed the project to be completed in one
year. He asks you to come up with the activities and tasks which includes
requirement elicitation.




Out of the various requirement elicitation techniques you learned in this course
please identify the elicitation techniques best suites for this situation.




List the various steps, the review process and finalization of definition and listing
them in FDD or Use Case documentation.



Please be ready to list the merits and demerits (pro’s and con’s) of using such a
technique.