The first use of the term 'requirements engineering' was probably in 1979 in a TRW technical report  but did not come into general use until the 1990s with the publication of an IEEE Computer Society tutorial  and the establishment of a conference series on requirements engineering.
In the waterfall model, requirements engineering is presented as the first phase of the development process. Later software development methods, including the Rational Unified Process, Extreme Programming and Scrum assume that requirements engineering continues through the lifetime of a system.
Requirements engineering activities
The activities involved in requirements engineering vary widely, depending on the type of system being developed and the specific practices of the organization(s) involved. These may include:
- Requirements inception or requirements elicitation -
- Requirements identification - identifying new requirements
- Requirements analysis and negotiation - checking requirements and resolving stakeholder conflicts
- Requirements specification (Software Requirements Specification)- documenting the requirements in a requirements document
- System modeling - deriving models of the system, often using a notation such as the Unified Modeling Language
- Requirements validation - checking that the documented requirements and models are consistent and meet stakeholder needs
- Requirements management - managing changes to the requirements as the system is developed and put into use
These are sometimes presented as chronological stages although, in practice, there is considerable interleaving of these activities.
Requirements engineering tools
Tool support is very important to track and store requirements.
|IBM Rational DOORS||http://www-01.ibm.com/software/awdtools/doors/||ex. "Telelogic DOORS"; used for system engineering|
|IBM Rational RequisitePro||http://www-01.ibm.com/software/awdtools/reqpro/||Used for software engineering|
|IBM Rational Requirements Composer||http://www-01.ibm.com/software/awdtools/rrc/||The followup to IBM Rational RequisitePro|
|Blueprint Requirements Definition & Management||http://www.blueprintsys.com/resources/product-brochures/|
|Visual Paradigm Requirements Capturing||http://www.visual-paradigm.com/product/vpuml/provides/reqmodeling.jsp|
|HP Requirements Management||http://www8.hp.com/us/en/software-solutions/software.html?compURI=1172907|
|PTC Integrity for Requirements Engineering||http://www.mks.com/solutions/discipline/rm/requirements-engineering||Formerly MKS Integrity for Requirements Management - optimized for system and software requirements|
|Polarion REQUIREMENTS||http://www.polarion.com/products/requirements/index.php||Web Requirements Management solution for any product, process or service|
|RQA Requirements Quality Analyzer for system engineering projects||http://www.reusecompany.com/requirements-quality-analyzer||The Requirements Quality Analyzer tool (RQA) allows you to define, measure, improve and manage the quality of the requirements specifications within the systems
- Kotonya G. and Sommerville, I. Requirements Engineering: Processes and Techniques. Chichester, UK: John Wiley & Sons
- Software Requirements Engineering Methodology (Development) Alfor,M. W. and Lawson,J. T. TRW Defense and Space Systems Group. 1979.
- Thayer, R.H., and M. Dorfman (eds.), System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, CA, 1990.
- Royce, W.W. 'Managing the Development of Large Software Systems: Concepts and Techniques', IEEE Westcon, Los Angeles, CA> pp 1-9, 1970. Reprinted in ICSE '87, Proceedings of the 9th international conference on Software Engineering.
- Requirements bibliography Reviewed November 10th 2011
- Sommerville, I. Software Engineering, 7th ed. Harlow, UK: Addison Wesley, 2006.
- Ralph, Paul (2012). "The Illusion of Requirements in Software Development". Requirements Engineering.