|It has been suggested that Software requirements be merged into this article. (Discuss) Proposed since February 2015.|
Requirements engineering (RE) refers to the process of defining, documenting and maintaining requirements and to the subfields of systems engineering and software engineering concerned with this process.
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 (RUP), extreme programming (XP) 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; SRS) - documenting the requirements in a requirements document
- System modeling - deriving models of the system, often using a notation such as the Unified Modeling Language (UML)
- 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
|This article's use of external links may not follow Wikipedia's policies or guidelines. (December 2013)|
|Innoslate||http://www.innoslate.com/requirements||Cloud and on-site requirements solution with full lifecycle support (free version available)|
|Intland Software codeBeamer||http://www.intland.com/products/codebeamer/modules/||Agile Software Development - Enterprise Requirements Engineering + Management|
|Rational DOORS||http://www-01.ibm.com/software/awdtools/doors/||ex. "Telelogic DOORS"; used for system engineering|
|Rational DOORS Next Generation||http://www-03.ibm.com/software/products/en/ratidoorng||The followup to Rational RRC.|
|Rational RequisitePro||http://www-01.ibm.com/software/awdtools/reqpro/||Used for software engineering|
|Rational Requirements Composer||http://www-01.ibm.com/software/awdtools/rrc/||The followup to Rational RequisitePro|
|Kovair Requirements Management - ALM Studio||http://www.kovair.com/alm-studio/requirements-management/||Used for Requirements elicitation, analysis, specification and validation|
|Blueprint Requirements Definition & Management||http://www.blueprintsys.com/resources/product-brochures/||Blueprint Requirements|
|Visual Paradigm Requirements Capturing||http://www.visual-paradigm.com/product/vpuml/provides/reqmodeling.jsp||Visual Paradigm Requirements Capturing|
|HP Requirements Management||http://www8.hp.com/us/en/software-solutions/software.html?compURI=1172907||HP Requirements Management|
|PTC Integrity||http://www.mks.com/solutions/discipline/rm/requirements-engineering||Formerly MKS Integrity for Requirements Management - optimized for system and software requirements|
|objectiF Requirements Modeller||http://www.microtool.de/requirements-modeller/en/index.asp|
|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 engineering process|
|TestTrack||http://www.seapine.com/ttrm.html||Cloud and on-site requirements solution|
- Requirements Engineering Specialist Group (RESG)
- International Requirements Engineering Board (IREB)
- IEEE 12207
- Concept of operations
- Software requirements
- Software requirements specification
- Kotonya, Gerald; Sommerville, Ian (September 1998). Requirements Engineering: Processes and Techniques. John Wiley & Sons. ISBN 0-471-97208-8.
- Software Requirements Engineering Methodology (Development) Alford, M. W. and Lawson,J. T. TRW Defense and Space Systems Group. 1979.
- Thayer, Richard H.; Dorfman, Merlin, eds. (March 1997). Software Requirements Engineering (2nd ed.). IEEE Computer Society Press. ISBN 0-8186-7738-4.
- Royce, W. W. (1970). Managing the Development of Large Software Systems: Concepts and Techniques (PDF). ICSE'87. Proceedings of the 9th international conference on Software Engineering: 1–9.
- Requirements bibliography Reviewed November 10th 2011
- Sommerville, Ian (2009). Software Engineering (9th ed.). Addison-Wesley. ISBN 978-0-13-703515-1.
- 29148-2011 - Systems and software engineering — Life cycle processes — Requirements engineering. 2011. pp. 1–94. ISBN 978-0-7381-6591-2. doi:10.1109/IEEESTD.2011.6146379.("This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998 - http://standards.ieee.org/findstds/standard/29148-2011.html")