cbdc:public:cbdc_omg:04_doc:90_recommend:50_recomend:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
cbdc:public:cbdc_omg:04_doc:90_recommend:50_recomend:start [2022/05/18 00:44] nick |
cbdc:public:cbdc_omg:04_doc:90_recommend:50_recomend:start [2022/06/17 19:38] (current) terrance |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| | [[cbdc:public:cbdc_omg:04_doc:90_recommend:start| Return to Recommendations ]] | <WRAP> | | [[cbdc:public:cbdc_omg:04_doc:90_recommend:start| Return to Recommendations ]] | <WRAP> | ||
| <html><b> | <html><b> | ||
| - | <a href="mailto:[email protected]?Subject=OMG CBDC Response: | + | <a href="mailto:[email protected]?Subject=OMG's CBDC WG Response: |
| 6.05 Formally Define Non-Functional Requirements | 6.05 Formally Define Non-Functional Requirements | ||
| ">Provide Feedback</a></b> | ">Provide Feedback</a></b> | ||
| Line 9: | Line 9: | ||
| </WRAP> | | </WRAP> | | ||
| - | The OMG members recommend the Federal Reserve define a task for defining, developing, and perfecting the [[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq|Non-functional requirements]] that are acceptable to the Federal Reserve and its Stakeholders. | + | The OMG's CBDC WG members recommend the Federal Reserve define a task for defining, developing, and perfecting the [[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq|Non-functional requirements]] that are acceptable to the Federal Reserve and its Stakeholders. |
| Non-Functional Requirements are often incorrectly assumed rather than explicitly defined by users. This can lead to problems towards the end of a project as the user expectations for non-functional requirements are not met. Many times, the developers dismiss non-functional requirements as non-testable and therefore not enforceable. | Non-Functional Requirements are often incorrectly assumed rather than explicitly defined by users. This can lead to problems towards the end of a project as the user expectations for non-functional requirements are not met. Many times, the developers dismiss non-functional requirements as non-testable and therefore not enforceable. | ||
cbdc/public/cbdc_omg/04_doc/90_recommend/50_recomend/start.1652849091.txt.gz · Last modified: 2022/05/18 00:44 by nick
