User Tools

Site Tools


dido:public:ra:1.4_req

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:public:ra:1.4_req [2021/03/07 16:11]
nick
dido:public:ra:1.4_req [2021/08/17 14:41] (current)
murphy
Line 1: Line 1:
 ====== 4 Requirements ====== ====== 4 Requirements ======
 +
 [[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 12: 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]]
Line 25: Line 26:
  
   * [[[[dido:​public:​ra:​1.4_req:​00_AboutReq]]   * [[[[dido:​public:​ra:​1.4_req:​00_AboutReq]]
-  * [[dido:​public:​ra:​1.4_req:​01_govReqMdl]] 
-  * [[dido:​public:​ra:​1.4_req:​02_cogReqMdl]] 
-  * [[dido:​public:​ra:​1.4_req:​03_combReqMdl]] 
-  * [[dido:​public:​ra:​1.4_req:​04_combExmpMdl]] 
-  * [[dido:​public:​ra:​1.4_req:​05_currState]] 
-  * [[dido:​public:​ra:​1.4_req:​06_oneDegree]] 
-  * [[dido:​public:​ra:​1.4_req:​07_reqSpec]] 
   * [[dido:​public:​ra:​1.4_req:​1_func]]   * [[dido:​public:​ra:​1.4_req:​1_func]]
   * [[dido:​public:​ra:​1.4_req:​2_nonfunc]]   * [[dido:​public:​ra:​1.4_req:​2_nonfunc]]
 +  * [[dido:​public:​ra:​1.4_req:​3_assessment]]
  
  
dido/public/ra/1.4_req.1615151498.txt.gz · Last modified: 2021/03/07 16:11 by nick