A TECHNICAL DISCUSSION ON REQUIREMENT ENGINEERING WITH AN EXAMPLE

Requirements engineering is concerned with the early phases of software development. This paper presents historical background and need of Requirements Engineering. More and more problems with software projects were being traced back to problems in the requirements process, therefore, the importance of requirements engineering was realized. Various definitions are discussed. Subsequently, importance of Requirement Engineering is explained with cases.

[1]  Pamela Zave.  Classification of research efforts in requirements engineering , 1997, ACM Comput. Surv..

[2]  Pericles Loucopoulos,et al.  System Requirements Engineering , 1995, System Requirements Engineering.

[3]  Pete Sawyer,et al.  Requirements Engineering: A Good Practice Guide , 1997 .

[4]  Armin Eberlein,et al.  Architectural design of an intelligent requirements engineering tool , 2003, CCECE 2003 - Canadian Conference on Electrical and Computer Engineering. Toward a Caring and Humane Technology (Cat. No.03CH37436).

[5]  Janis A. Bubenko,et al.  Requirements Engineering and Technology Transfer: Obstacles, Incentives and Improvement Agenda , 2002, Requirements Engineering.

[6]  Richard H. Thayer,et al.  System and Software Requirements Engineering , 1994 .

[7]  Theodore Hammer,et al.  Automated requirements management-beware HOW you use tools: an experience report , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[8]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[9]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .