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 Next revision | Previous revision | ||
|
cbdc:public:cbdc_omg:04_doc:90_recommend:50_recomend:start [2022/05/13 16:28] nick |
cbdc:public:cbdc_omg:04_doc:90_recommend:50_recomend:start [2022/06/17 19:38] (current) terrance |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 6.05 Formally Define Non-Functional Requirements ====== | ====== 6.05 Formally Define Non-Functional Requirements ====== | ||
| - | [[cbdc:private:cbdc_omg:04_doc:90_recommend:start| Return to Recommendations]] | + | |< 100% >| |
| + | | [[cbdc:public:cbdc_omg:04_doc:90_recommend:start| Return to Recommendations ]] | <WRAP> | ||
| + | <html><b> | ||
| + | <a href="mailto:[email protected]?Subject=OMG's CBDC WG Response: | ||
| + | 6.05 Formally Define Non-Functional Requirements | ||
| + | ">Provide Feedback</a></b> | ||
| + | </html> | ||
| + | </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. | ||
| Line 9: | Line 16: | ||
| Users expect new features to be added to a system and tested before they use them. Users assume the software is maintainable without an explicit declaration for “[[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:m:maintainability|maintainability]]”. In many ways, they expect it to be an unwritten requirement and or [[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:g:goal|goal]]. In other words, users expect the system to be analyzable, changeable, stable, and testable(( | Users expect new features to be added to a system and tested before they use them. Users assume the software is maintainable without an explicit declaration for “[[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:m:maintainability|maintainability]]”. In many ways, they expect it to be an unwritten requirement and or [[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:g:goal|goal]]. In other words, users expect the system to be analyzable, changeable, stable, and testable(( | ||
| - | Prolifics Testiing, __Achieving Requirements Testability__, 10 October 2018, Accessed 10 November 2020, [[https://www.prolifics-testing.com/news/achieving-requirements-testability]] | + | Prolifics Testing, __Achieving Requirements Testability__, 10 October 2018, Accessed 10 November 2020, [[https://www.prolifics-testing.com/news/achieving-requirements-testability]] |
| )). For example, smartphone users will switch apps to other apps if the energy consumed by the app is not efficient. Efficiency is therefore a non-functional requirement. Energy consumption may also be a [[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:f:funcreq|functional requirements]] (i.e., An [[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:a:application|application]] can not use more than 1040 mW (milli-Watt) per [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:s:sms | Short Message Service (SMS) ]] message. (( | )). For example, smartphone users will switch apps to other apps if the energy consumed by the app is not efficient. Efficiency is therefore a non-functional requirement. Energy consumption may also be a [[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:f:funcreq|functional requirements]] (i.e., An [[https://www.omgwiki.org/dido/doku.php?id=ddido:public:ra:xapend:xapend.a_glossary:a:application|application]] can not use more than 1040 mW (milli-Watt) per [[https://www.omgwiki.org/dido/doku.php?id=dido:public:ra:xapend:xapend.a_glossary:s:sms | Short Message Service (SMS) ]] message. (( | ||
| Sai Suren Kumar Kasireddy and Vishnuvardhan Reddy Bojja, __Measurements of Energy Consumption in Mobile Applications with respect to the quality of Experience__, School of Computing, Blekinge Institute of Technology, 37179 Karlskrona, Sweden, March 2012, Accessed: 10 November 2020, [[https://www.diva-portal.org/smash/get/diva2:829733/FULLTEXT01.pdf]] | Sai Suren Kumar Kasireddy and Vishnuvardhan Reddy Bojja, __Measurements of Energy Consumption in Mobile Applications with respect to the quality of Experience__, School of Computing, Blekinge Institute of Technology, 37179 Karlskrona, Sweden, March 2012, Accessed: 10 November 2020, [[https://www.diva-portal.org/smash/get/diva2:829733/FULLTEXT01.pdf]] | ||
cbdc/public/cbdc_omg/04_doc/90_recommend/50_recomend/start.1652473726.txt.gz · Last modified: 2022/05/13 16:28 by nick
