Sidebar
dido:public:ra:1.4_req
4 Requirements
return to Reference Architecture
The term requirement first appeared in software engineering in the 1960s.1)
The Business Analysis Body of Knowledge® version 2 from IIBA (BABOK),2) defines a requirement as having one or more of the following characteristics:
- 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).3)
This definition is based on IEEE Standardized vocabulary.4)
1)
Boehm, Barry (2006). A view of 20th and 21st century software engineering. ICSE '06 Proceedings of the 28th international conference on Software engineering. University of Southern California, University Park Campus, Los Angeles, CA: Association for Computing Machinery, ACM New York, NY, USA. pp. 12–29. ISBN 1-59593-375-1. Retrieved January 2, 2013.
http://dl.acm.org/citation.cfm?id=1134288
2)
1.3 Key Concepts - IIBA | International Institute of Business Analysis“. www.iiba.org. Retrieved 2016-09-25.
http://www.iiba.org/babok-guide/babok-guide-v2/babok-guide-online/chapter-one-introduction/1-3-key-concepts.aspx
4)
IEEE/ISO/IEC 24765-2010 - ISO/IEC/IEEE International Standard - Systems and software engineering – Vocabulary ,
2010-02-02, published 15 December 2015,
IEEE,
[https://standards.ieee.org/standard/24765-2010.html]]
dido/public/ra/1.4_req.txt · Last modified: 2021/08/17 14:41 by murphy
Translations of this page:
