Editing Requirements engineering (section)

{{Short description|Defining and maintaining requirements in systems engineering}}
{{Close paraphrasing|source=|date=September 2020}}
{{Use American English|date = March 2019}}
{{Use mdy dates|date = March 2019}}

'''Requirements engineering''' ('''RE''')<ref>{{Cite conference | doi = 10.1145/336512.336523| title = Requirements engineering: a roadmap| work = Proceedings of the conference on the future of Software engineering| conference= [[International Conference on Software Engineering|ICSE]]'00| pages = 35–46| year = 2000| last1 = Nuseibeh | first1 = B. | last2 = Easterbrook | first2 = S. | isbn = 1-58113-253-0| citeseerx = 10.1.1.131.3116| url = http://mcs.open.ac.uk/ban25/papers/sotar.re.pdf}}</ref> is the process of defining, documenting, and maintaining [[requirement]]s<ref>
*{{cite book |last1=Kotonya |first1=Gerald |last2=Sommerville |first2=Ian |author-link2=Ian Sommerville (academic) |title=Requirements Engineering: Processes and Techniques |date=September 1998 |publisher=[[John Wiley & Sons]] |isbn=978-0-471-97208-2 |url-access=registration |url=https://archive.org/details/requirementsengi1998koto }}
*{{Cite book | doi = 10.1007/978-1-4614-5377-2| title = Requirements Engineering and Management for Software Development Projects| year = 2013| last1 = Chemuturi | first1 = M. | author-link1 = Murali Chemuturi| isbn = 978-1-4614-5376-5| s2cid = 19818654}}</ref> in the [[engineering design process]]. It is a common role in [[systems engineering]] and [[software engineering]].

The first use of the term ''requirements engineering'' was probably in 1964 in the conference paper "Maintenance, Maintainability, and System Requirements Engineering",<ref>{{cite conference |last1=Dresner |first1=K. H. Borchers  |title=Maintenance, maintainability, and system requirements engineering |work=SAE Technical Paper 640591 |conference=[[SAE International|SAE World Congress & Exhibition]] 1964 |year=1964 |doi=10.4271/640591 }}</ref> but it did not come into general use until the late 1990s with the publication of an [[IEEE Computer Society]] tutorial<ref>{{cite book |editor-last1=Thayer |editor-first1=Richard H. |editor-last2=Dorfman |editor-first2=Merlin |title=Software Requirements Engineering |edition=2nd |publisher=[[IEEE Computer Society Press]] |date=March 1997 |isbn=978-0-8186-7738-0 |url-access=registration |url=https://archive.org/details/softwarerequirem2000unse }}</ref> in March 1997 and the establishment of a conference series on requirements engineering that has evolved into the [[International Requirements Engineering Conference]].

In the [[waterfall model]],<ref>{{cite conference |last1=Royce |first1=W. W. |author-link1=Winston W. Royce |title=Managing the Development of Large Software Systems: Concepts and Techniques |work=Proceedings of the 9th international conference on Software Engineering |conference=[[International Conference on Software Engineering|ICSE]]'87 |pages=1–9 |year=1970 |url=http://www.serena.com/docs/agile/papers/Managing-The-Development-of-Large-Software-Systems.pdf}}</ref> requirements engineering is presented as the first phase of the development process. Later development methods, including the [[Rational Unified Process]] (RUP) for software, assume that requirements engineering continues through a system's lifetime.

[[Requirements management]], which is a sub-function of Systems Engineering practices, is also indexed in the [[International Council on Systems Engineering]] (INCOSE) manuals.