dido:public:ra:1.4_req:00_aboutreq:07_reqspec
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:00_aboutreq:07_reqspec [2021/08/17 12:25] murphy |
dido:public:ra:1.4_req:00_aboutreq:07_reqspec [2022/03/16 16:08] (current) char |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| Regardless of where the requirements are captured or by what organizations, they can in general be considered governing statements. The following are some guidance on how to write healthy governing statements and consequently also requirements. | Regardless of where the requirements are captured or by what organizations, they can in general be considered governing statements. The following are some guidance on how to write healthy governing statements and consequently also requirements. | ||
| - | A Governance Statement based on an __Engineering Governance__ Model developed at US Navy SPAWAR(( | + | A [[dido:public:ra:xapend:xapend.a_glossary:g:governance]] Statement based on an __Engineering Governance__ Model developed at US Navy SPAWAR(( |
| Stavros, Robert W. and | Stavros, Robert W. and | ||
| Albrant, Jeremiah; | Albrant, Jeremiah; | ||
| Line 18: | Line 18: | ||
| * **Definitive** - A Governance Statement is precisely worded and explicit in nature. Their words, terms and expressions need to be defined and not subject to interpretation. Indicators of non-definitive guidance are words that are not intuitively obvious to an outside reader. Some words that are examples of non-explicit words are: object, service and function. | * **Definitive** - A Governance Statement is precisely worded and explicit in nature. Their words, terms and expressions need to be defined and not subject to interpretation. Indicators of non-definitive guidance are words that are not intuitively obvious to an outside reader. Some words that are examples of non-explicit words are: object, service and function. | ||
| - | Another issue or controversy with specifying requirements is how the statements use imperatives, words like: | + | Another issue or controversy with specifying requirements is how the statements use imperatives originally defined in [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:2119]], words like: |
| * [[dido:public:ra:xapend:xapend.a_glossary:s:shall_req]] | * [[dido:public:ra:xapend:xapend.a_glossary:s:shall_req]] | ||
| Line 50: | Line 50: | ||
| )). | )). | ||
| + | <color darkred><todo @char>Review </todo></color> | ||
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
dido/public/ra/1.4_req/00_aboutreq/07_reqspec.1629217543.txt.gz · Last modified: 2021/08/17 12:25 by murphy
