dido:public:ra:xapend:xapend.a_glossary:s:should_req
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.a_glossary:s:should_req [2021/02/01 12:13] nick created |
dido:public:ra:xapend:xapend.a_glossary:s:should_req [2021/10/04 13:40] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Should (Requirement) ====== | + | ===== Should (Requirement) ===== |
| - | [[dido:public:ra:xapend:xapend.a_glossary| Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| - | **Should is not per se the specification of a requirement** but is used to capture Goals, non-mandatory provisions. Should is used to indicate a goal which must be addressed by the design team but is not formally verified. | + | **Should is not per se the specification of a requirement** but is used to capture Goals, non-mandatory provisions. Should is used to indicate a [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]] which must be addressed by the design team but is not formally verified. |
| Why include should (goal) statements in your requirement document? Because you may have a very important issue that you want to communicate to the developers, but can’t think of a way to do so in the form of a verifiable requirement. For example, NASA was developing a jet pack called SAFER and one of the requirements read “The SAFER shall not impede crew mobility”. Well anything but a decal will probably impeded crew mobility so how am I going to verify that statement if it is written as a requirement? I can’t. So, now that I recognize this, I change the statement from a requirement “shall” to a goal “should” and then I ask my designers and developers at every subsequent review, “how are you going to design the jet pack so that it does not impeded crew mobility”? | Why include should (goal) statements in your requirement document? Because you may have a very important issue that you want to communicate to the developers, but can’t think of a way to do so in the form of a verifiable requirement. For example, NASA was developing a jet pack called SAFER and one of the requirements read “The SAFER shall not impede crew mobility”. Well anything but a decal will probably impeded crew mobility so how am I going to verify that statement if it is written as a requirement? I can’t. So, now that I recognize this, I change the statement from a requirement “shall” to a goal “should” and then I ask my designers and developers at every subsequent review, “how are you going to design the jet pack so that it does not impeded crew mobility”? | ||
| + | |||
| + | Also see: [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:2119]] | ||
| Source: [[https://reqexperts.com/2012/10/09/using-the-correct-terms-shall-will-should/ ]] | Source: [[https://reqexperts.com/2012/10/09/using-the-correct-terms-shall-will-should/ ]] | ||
dido/public/ra/xapend/xapend.a_glossary/s/should_req.1612199624.txt.gz · Last modified: 2021/02/01 12:13 by nick
