Iycee Charles de Gaulle Summary A it is more practical for the

A it is more practical for the

A number of researchers talk about requirement
elicitation and use some approaches , technique , and tools to collect a
requirement from user  .

In 1 the first researcher used approach this approach leverages design processes
and promotes realization of the required user experience, including usability
and accessibility requirements. In this positional paper, a new approach to the
technological evolution occurring in our complex world is proposed, which
requires knowledge integration and the linking of diverse disciplinary fields. The pro-posed approach aims at overcoming
the observed results and fosters enhanced processes that encompass the
different perspectives. We demonstrate this approach using a design object
created in a multidisciplinary team.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!

order now

2 the second researcher used Elicitation tool is an effortless one that
visually aids the user to state their needs more accurately as it is more
practical for the user to imagine by seeing instead of hearing. This tool can
be used by the analyst as an aid to gather requirements in a more efficient
manner compared to other existing methods.

In 3 the third researcher used technique  to overcome the problem of requirement
elicitation technique for web application using a combination of interview and
Joint Application Development technique between developers and users. This
technique will improve the requirement elicitation process and help developers
and users to clearly define their requirements in web based application. We
also anticipate this technique will decrease the time spent to develop a web
application by using this combined technique.


In 4the fourth
researcher  gives review of five elicitation based
tools in context with visualization of requirements to stakeholders. Benefits
and limitations of tools have been presented and the limitations reflect the
aspects of improvements.


In 5 Researches have identified the major cause
behind software project failures to be poor RE . Requirement elicitation is
arguably the most important part of the whole RE process. It is concerned
primarily with the communication between client stakeholders and engineer
stakeholders. A successful level of elicitation early on in the project is
important in order to create a solid mutual understanding so as to not leave
some project goals out. These left out goals produce a lot of dissatisfaction
for the final project and may imply a lot of work, and cost, to implement later
on. Another kind of failure is misunderstandings of requirements.
Misinterpreting and wrongly implementing requirements produce just as bad
results as not implementing them at all. There are many elicitation techniques
and also methodologies that propose complete roadmaps using a combination of
different techniques and tools. Some of these techniques are interviews,
workshops, observational and documentation