Requirements engineering

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Requirements engineering (RE)[1] refers to the process of defining, documenting and maintaining requirements[2][3] 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[4] but did not come into general use until the 1990s with the publication of an IEEE Computer Society tutorial[5] and the establishment of a conference series on requirements engineering.

In the waterfall model,[6] 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.

Alan M. Davis maintains an extensive bibliography of requirements engineering.[7]

Requirements engineering activities[edit]

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.[8] These may include:

  1. Requirements inception or requirements elicitation -
  2. Requirements identification - identifying new requirements
  3. Requirements analysis and negotiation - checking requirements and resolving stakeholder conflicts
  4. Requirements specification (software requirements specification; SRS) - documenting the requirements in a requirements document
  5. System modeling - deriving models of the system, often using a notation such as the Unified Modeling Language (UML)
  6. Requirements validation - checking that the documented requirements and models are consistent and meet stakeholder needs
  7. 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[edit]

Some links to the tools[edit]

Product Link Notes
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
IBM Rational DOORS http://www-01.ibm.com/software/awdtools/doors/ ex. "Telelogic DOORS"; used for system engineering
IBM Rational DOORS Next Generation http://www-03.ibm.com/software/products/en/ratidoorng The followup to IBM Rational RRC.
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
TraceCloud http://www.tracecloud.com/GloreeJava2/jsp/WebSite/TCHome.jsp TraceCloud
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 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
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

Criticism[edit]

Some recent research suggests that software requirements are often an illusion misrepresenting design decisions as requirements in situations where no real requirements are evident.[9]

See also[edit]

References[edit]

  1. ^ Nuseibeh, B.; Easterbrook, S. (2000). "Requirements engineering: a roadmap". ICSE'00. Proceedings of the conference on the future of Software engineering: 35–46. doi:10.1145/336512.336523. ISBN 1-58113-253-0. CiteSeerX: 10.1.1.131.3116.  edit
  2. ^ Kotonya, Gerald; Sommerville, Ian (September 1998). Requirements Engineering: Processes and Techniques. John Wiley & Sons. ISBN 0-471-97208-8. 
  3. ^ Chemuturi, M. (2013). Requirements Engineering and Management for Software Development Projects. doi:10.1007/978-1-4614-5377-2. ISBN 978-1-4614-5376-5.  edit
  4. ^ Software Requirements Engineering Methodology (Development) Alford, M. W. and Lawson,J. T. TRW Defense and Space Systems Group. 1979.
  5. ^ Thayer, Richard H.; Dorfman, Merlin, eds. (March 1997). Software Requirements Engineering (2nd ed.). IEEE Computer Society Press. ISBN 0-8186-7738-4. 
  6. ^ Royce, W. W. (1970). "Managing the Development of Large Software Systems: Concepts and Techniques". ICSE'87. Proceedings of the 9th international conference on Software Engineering: 1–9. 
  7. ^ Requirements bibliography Reviewed November 10th 2011
  8. ^ Sommerville, Ian (2009). Software Engineering (9th ed.). Addison-Wesley. ISBN 978-0-13-703515-1. 
  9. ^ Ralph, P. (September 2013). "The illusion of requirements in software development". Requirements Engineering 18 (3): 293–296. doi:10.1007/s00766-012-0161-4.  edit

External links[edit]