Open Access Open Access  Restricted Access Subscription or Fee Access

Requirement Engineering: A Comprehensive Review

Arti Rani, Kamna Solanki, Geeta Jangra


The area of Requirements Engineering is often underestimated in value in the area of Software Engineering. Requirements engineering is a repeatable and systematic technique. The main objective of requirement engineering is “to gather the requirements”. The requirements engineering phase of software development projects is characterized by the intensity and importance of communication activities. During this phase, the various stakeholders must be able to communicate their requirements to the analysts, and the analysts need to be able to communicate the specifications they generate back to the stakeholders for validation. It includes set of activities like system feasibility study, elicitation analysis, validation and management of the requirements. This paper presents the conceptual view of requirement engineering and its types and techniques come under these types. The activities include software implementation, maintenance, and enhancement. This paper describes the challenges on the requirements engineering for developing an enterprise applications. This paper overviews a systematic, goal-oriented approach to requirements engineering. This paper presents an overview of the field of software systems requirements engineering (RE). It describes the main areas of RE practice.


Requirement Engineering, Requirement Elicitation, Requirement Analysis, Requirement Management and Validation

Full Text:



Jamaludin Sallim, “Requirements Engineering for Enterprise Applications Development: Seven Challenges in Higher Education Environment”, World Academy of Science, Engineering and Technology 4 2005.

Axel van lamsweerde, “Engineering Requirements for System Reliability and Security”, 2007.

Anthony Finkelstein, “Requirements Engineering Research: coordination and infrastructure” March 1996.

Linda Westfall, “Software Requirements Engineering: What, Why, Who, When, and How”, The Westfall Team.2006.

Brooks, F., “No Silver Bullet: Essence and Accidents of Software Engineering”, IEEE Computer, Vol. 20, No. 4, April 1987, p. 10-19.

Bill Davey, “Requirements Elicitation – What‟s Missing? ", Issues in Informing Science and Information Technology Volume 5, 2008.

Lynette Sparrow, Lemai Nguyen, “The Slow Wheels of Requirements Engineering Research: Responding to the Challenge of Societal Change”, AWRE Adelaide, Australia 2006.

Bashar Nuseibeh, Steve Easterbrook, “Requirements Engineering: A Roadmap”, ACM 2000.

Axel van Lamsweerde, “Requirements Engineering: From Craft to Discipline”, Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering ACM New York, NY, USA ©2008.

Dr. Sohail Asghar., “Requirement Engineering Challenges in Development of Software Applications and Selection of Customer-off-the-Shelf (COTS) Components” International Journal of Software Engineering (IJSE), Volume (1): Issue (2) .

Axel van Lamsweerde, “Reasoning about Alternative Requirements Options*”, 2009.

Amer Al-Rawas and Steve Easterbrook. "Communication problems in requirements engineering: a field study " To appear in Proceedings of the First Westminster Conference on Professional Awareness in Software Engineering, Royal Society, London, 1-2 February 1996.

Uolevi Nikula,”BaRE – A Ready to Use Method for Requirements Engineering”, Licentiate Thesis Lappeenranta, December 2002.

Andrigo Gomes, Andreas Pettersson, “Market-Driven Requirements Engineering Process Model – MDREPM”, Master Thesis Software Engineering Thesis no: MSE-2007-06 January 2007.

Tony Gorschek Kaarina Tejle, “A Method for Assessing Requirements Engineering Process Maturity in Software Projects”, Master Thesis Computer Science Thesis no: MCS-2002:2 June 2002.


  • There are currently no refbacks.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.