dido:public:ra:1.4_req
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.4_req [2021/06/09 15:50] char |
dido:public:ra:1.4_req [2021/08/17 14:41] (current) murphy |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| [[dido:public:ra|return to Reference Architecture]] | [[dido:public:ra|return to Reference Architecture]] | ||
| - | The term requirement first appeared in software engineering in the 1960s.(( | + | The term [[dido:public:ra:xapend:xapend.a_glossary:r:requirement|requirement]] first appeared in software engineering in the 1960s.(( |
| 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. | 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]] | [[http://dl.acm.org/citation.cfm?id=1134288]] | ||
| Line 13: | Line 13: | ||
| )) defines a requirement as having one or more of the following characteristics: | )) 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 needed by a [[dido:public:ra:xapend:xapend.a_glossary:s:stakeholder|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 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).(([[https://en.wikipedia.org/wiki/Requirement#cite_note-2 | Wikipedia Requirement]] | - //A documented representation of a condition or capability as in (1) or (2).(([[https://en.wikipedia.org/wiki/Requirement#cite_note-2 | Wikipedia Requirement]] | ||
dido/public/ra/1.4_req.1623268200.txt.gz · Last modified: 2021/06/09 15:50 by char
