With the swift growth in technology and businesses in recent decades, software has become very essential component in all facets of the modern world. But Software development segment is in trouble, due to project failures, budget overruns, extended time frame, failure to meet needs and poor quality levels. Proportion of projects failure is caused by requirement affairs. Now, the crucial issue in the software development process is getting the operational requirements right and to welcome change in the requirements even late in the development process. Users have difficulty in explaining what they need and the problems multiply when developers fail to translate requirements into working software. Therefore, an effective and efficient system is required to improve requirement engineering process. This paper reviews the existing requirement engineering practices that agile and non-agile software teams follow and explores the parameters required for effective elicitation and analyzing of requirements. We also proposed a model based on these parameters that effectively handle the changing user’s requirements.

Full text: IJEIR_2892_FINAL.pdf