Requirements engineering

Requirements engineering (RE)[1] refers to the process of defining, documenting and maintaining requirements[2][3] to the sub-fields 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 that has evolved into the current International Requirements Engineering Conference.

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]

Requirement management which is a sub-function of Systems Engineering practices are also indexed in the INCOSE (International Council on Systems Engineering) manuals.

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.[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 (e.g., software requirements specification; SRS) - documenting the requirements in a requirements document
  5. Systems 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.

Problems

One limited study in Germany presented possible problems in implementing requirements engineering and asked respondents whether they agreed that they were actual problems. The results were not presented as being generalizable but suggested that the principal perceived problems were incomplete requirements, moving targets, and time boxing, with lesser problems being communications flaws, lack of traceability, terminological problems, and unclear responsibilities.[9]

Criticism

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

See also

References

  1. ↑ Nuseibeh, B.; Easterbrook, S. (2000). Requirements engineering: a roadmap (PDF). ICSE'00. Proceedings of the conference on the future of Software engineering. pp. 35–46. doi:10.1145/336512.336523. ISBN 1-58113-253-0. CiteSeerX: 10.1.1.131.3116.
  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.
  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 (PDF). ICSE'87. Proceedings of the 9th international conference on Software Engineering. pp. 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. ↑ Méndez Fernández, Daniel; Wagner, Stefan (2015). "Naming the pain in requirements engineering: A design for a global family of surveys and first results from Germany". Information and Software Technology 57: 616–643. doi:10.1016/j.infsof.2014.05.008.
  10. ↑ Ralph, P. (September 2013). "The illusion of requirements in software development". Requirements Engineering 18 (3): 293–296. doi:10.1007/s00766-012-0161-4.

External links

This article is issued from Wikipedia - version of the Thursday, April 14, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.