Editing Requirement (section)

== Origins of term ==
The term ''requirement'' has been in use in the software engineering community since at least the 1960s.<ref>{{cite conference |last= Boehm |first= Barry |title= A view of 20th and 21st century software engineering |book-title= ICSE '06 Proceedings of the 28th international conference on Software engineering|pages=12–29|ISBN= 1-59593-375-1 |publisher=Association for Computing Machinery, ACM New York, NY, USA |year=2006 |location=University of Southern California, University Park Campus, Los Angeles, CA |url=http://dl.acm.org/citation.cfm?id=1134288 |access-date=January 2, 2013}}</ref>

According to the ''Guide to the Business Analysis Body of Knowledge®'' version 2 from IIBA (BABOK),<ref>{{Cite web|url=http://www.iiba.org/babok-guide/babok-guide-v2/babok-guide-online/chapter-one-introduction/1-3-key-concepts.aspx|title=1.3 Key Concepts - IIBA {{!}} International Institute of Business Analysis|website=www.iiba.org|access-date=2016-09-25}}</ref> a requirement is:
# A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
# A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract, standard, specification, or other formally imposed documents.
# A documented representation of a condition or capability as in (1) or (2).
This definition is based on  IEEE 610.12-1990: IEEE Standard Glossary of Software Engineering Terminology.<ref>{{cite web | url = http://standards.ieee.org/findstds/standard/610.12-1990.html | archive-url = https://web.archive.org/web/20110110043912/http://standards.ieee.org/findstds/standard/610.12-1990.html | url-status = dead | archive-date = January 10, 2011 | title = IEEE SA - 610.12-1990 - IEEE Standard Glossary of Software Engineering Terminology }}</ref>