logo

Requirement Elicitation Technique

   

Added on  2023-01-10

12 Pages2823 Words39 Views
Running head - REQUIREMENT ELICITATION TECHNIQUE
Requirement Elicitation Technique
Name of the student
Name of the university
Author’s note

1REQUIREMENT ELICITATION TECHNIQUE
Table of Contents
Introduction................................................................................................................................2
Discussion..................................................................................................................................2
Survey Technique...................................................................................................................3
Creative Technique................................................................................................................4

2REQUIREMENT ELICITATION TECHNIQUE
Introduction
In the field of requirement engineering, requirement elicitation technique is
considered to be a technique that helps in practicing in research, along with discovering the
requirements of a particular system for the users, for the customers and other stakeholders.
This form of practice is sometimes also referred as the gathering of requirements. The basic
difference between the stakeholders and the requirement engineers are quite simple (Wong,
Mauricio & Rodriguez, 2017). The first and foremost work of the requirement elicitation
process is to identify the stakeholders. Stakeholders hold the organization on their shoulders.
Each stakeholders are each pillar of any organization that helps the organization to operate.
The requirement engineers identifies the stakeholders and assess the information from them.
It is a common fact in requirement engineering that stakeholders are recognized as stake of
the project. Sometimes, it is extremely difficult to find some cripple in the system that is not
being affected by the system requirements. Thus, requirement engineers sometimes find it
difficult to locate any particular stakeholder that is not being effected by them.
The following report would be elaborately discuss about the various kind of
techniques that is used by requirement engineers for in the process of requirement elicitation.
The report would be discussing techniques like – survey, creativity, document-centric,
observation and support.
Discussion
Requirement elicitation is regarded as the first step in the process of requirement
engineering. It is estimated as the goal for eliciting the relevant information for the problem
or the solution. The information that are gathered are analysed and = documented for further
processing. After validating the information, they are finally managed through the project life
cycle (Pacheco, García & Reyes, 2018).

3REQUIREMENT ELICITATION TECHNIQUE
The requirement elicitation is also seen as human intensive activity. It is known as
that as sometimes the information that are gathered are highly dependable on the involvement
of the correct stakeholders. The activity is highly likeable to intercede with the analysis of the
requirement and the documentation that are gathered during the documentation process. Due
to these factors, there are times when the process faces a lot of problem. The problems are
classified as volatility, scope and understanding. It would be impossible to estimate the
feasible solution of the problem without knowing the scope of the results that are to be
expected for elicitation. There are times when analyst there time while expecting the results
without thinking of the scopes of the process. Stakeholders are sometimes also the main focus
of the problem that arises from the process (Carrizo, Dieste & Juristo, 2017). This occurs due
to fact that sometimes the stakeholders are not aware their own needs. The management
undergo from a period of crisis due to the fact that there would be clashing of viewpoints
among the stakeholders of the organization itself. Thus, there are possible delay. Final
problem that keeps on coming is the fact that requirements sometimes evolves from time to
time which changes the process from the inside itself, keeping the outcomes at stake and
upholding the changes.
Overviewing all the possible problem that could arise from the processes, the
techniques that could avoid the problem would be – survey, creative, document-centric,
observation and support.
Survey Technique
Survey is demonstrated to be one of the most important and most commonly used
method that could be used for collecting data and analysing it. Leading a survey would be
helpful and an incredible for the process of gathering as the question that lead a survey could
not be answered by themselves or the data would not be centred to one individual only
(Aylward et al., 2018). All the questionnaires are taken into account and the data collected are

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Business Requirements Analysis: Questionnaires and Interviews
|10
|2729
|494

Process of Requirements Engineering
|18
|3928
|16

Information System - Requirements Elicitation and UML Modelling
|10
|1818
|274

“As-is” workflow modeling analysis.
|5
|1270
|259

Business Requirement Analysis
|11
|2006
|76

Facilitated Application Specification Technique (FAST)
|14
|3031
|23