Requirement Elicitation is one of the most important phases
in SDLC during which all the requirements of
users are elicited.
SDLC Process |
Following are the techniques of requirement elicitation:-
- Conversational
methods
This is the verbal communication which takes place between
stakeholders. Analysts and the experienced persons conduct different interviews,
workshops to gather the requirements. Brain storming is also a conversational
method by which requirements are elicited through the collection of ideas.
- Observational
method
In this method the requirements are elicited by observing
the peoples. Persons may be attached to the environment in order to elicit
the requirements. Observations are made in such a way that it doesn't disturb
the peoples and the staff members of the organization.
- Analytical
method
In this method the analyst does the analysis of the
gathered information. In this method we reuse the specification of the legacy
systems to elicit the requirements. In this method requirements are also
elicited through the questionnaires.
- Synthetic
method
In this method we start the requirement elicitation from
the documentation study. In this method we combine the conversational,
observational and analytic methods to elicit the requirements. In this method
the scenarios and storyboards are used to elicit the requirements. This method
also include the JAD/RAD sessions, the purpose of including it in this method
is to include all the stakeholders in the design phase. The analyst and
stakeholders conduct contextual inquiry to elicit the requirements.
- GSD
methodology
In this methodology the advance problems are gathered and
the strategy is made to lessen that problems.
- Analysis
of data
Requirement elicitation I responsible for the success or
failure of the project.JAD/RAD and ethnography has very much usage rate as
compared to the R-group. Elicitation methods also depend on the development
process.
- Elicitation
guidelines
- Interviews/Surveys are important for web based systems
- 2 Checklists are important for the small scale systems
- JAD/RAD is recommended when we have to deal a lot of peoples in less time and in less budget
- Scenarios/Storyboards are used for the legacy system updates
- Ethnography is used during the updating and we have a lot of time and budget.
View Points
Many software houses have their own ways of developing. Due
to this reason sometimes they fails because their own ways of developing are
not sufficient sometimes to develop the modern software project. Engineers must
use proper and adequate model and method for requirement elicitation and
development for the user satisfactory.
0 comments: