Tanik, Murat (Committee chair)
Kurfess, Franz J. (Committee member)
Sebastian, Donald H. (Committee member)
Dogru, Ali Hikmet (Committee member)
Rana, Ajaz A. (Committee member)
Date:
1998-05
Keywords:
System analysis.
Computer software--Development.
Internet (Computer network)--Standards.
Availability:
Unrestricted
Abstract:
There are many problems associated with Requirements Engineering such as defining the system scope, developing understanding among the communities involved in the system to be built, volatility of requirements etc. These problems may lead to poor requirements and therefore cancellation of the system development, or else the development of a system that is unsatisfactory, has high maintenance cost or is unacceptable. By improving Requirements Elicitation, the Requirements Engineering can be improved, leading to a better requirements specification and eventually a better product.
Requirements Elicitation requires effective communication among the team members, as communication is the key factor. Easing communications between stakeholders and developers makes the process of Requirements Elicitation easier. REPI guides team members through the elicitation phase using the SEI's framework. REPI forces stakeholders to explicitly describe the requirements resulting in reduced chances of misunderstood requirements, leading to better requirements specification.
If you have any questions please contact the ETD Team, libetd@njit.edu.