Requirements engineering (RE) refers to the process of defining, documenting and maintaining [1 ] requirements [2 ] and to the subfields of [3 ] 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 [4 ] IEEE Computer Society tutorial and the establishment of a conference series on requirements engineering. [5 ]
waterfall model, requirements engineering is presented as the first phase of the development process. Later software development methods, including the [6 ] 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.
These may include: [8 ]
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 [ edit ]
Some links to the tools [ edit ]
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 ]
^ Nuseibeh, B.; Easterbrook, S. (2000). Requirements engineering: a roadmap (PDF). 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
^ Kotonya, Gerald; Sommerville, Ian (September 1998). Requirements Engineering: Processes and Techniques. John Wiley & Sons. ISBN 0-471-97208-8.
^ 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.
^ 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.
^ 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 [ edit ]