dido:public:ra:1.4_req:3_assessment:2_nonfunctional
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:1.4_req:3_assessment:2_nonfunctional [2021/08/11 12:21] murphy |
dido:public:ra:1.4_req:3_assessment:2_nonfunctional [2021/08/17 14:40] (current) murphy |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| [[dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq|Non-Functional requirements]] are by nature, hard to measure and hard to assess for compliance. The complexity of the assessment problem is compounded because products or systems as well as the environment they operate within are not static. Therefore, an assessment that is done today, may no longer be accurate in the future. When assessing [[dido:public:ra:xapend:xapend.a_glossary:c:cots]], [[dido:public:ra:xapend:xapend.a_glossary:g:gots]], [[dido:public:ra:xapend:xapend.a_glossary:m:mots]] or [[dido:public:ra:xapend:xapend.a_glossary:n:nots]] or the inclusion of [[dido:public:ra:xapend:xapend.a_glossary:o:oss]] the potential for changes (particularly enhancements) needs to be assed also. | [[dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq|Non-Functional requirements]] are by nature, hard to measure and hard to assess for compliance. The complexity of the assessment problem is compounded because products or systems as well as the environment they operate within are not static. Therefore, an assessment that is done today, may no longer be accurate in the future. When assessing [[dido:public:ra:xapend:xapend.a_glossary:c:cots]], [[dido:public:ra:xapend:xapend.a_glossary:g:gots]], [[dido:public:ra:xapend:xapend.a_glossary:m:mots]] or [[dido:public:ra:xapend:xapend.a_glossary:n:nots]] or the inclusion of [[dido:public:ra:xapend:xapend.a_glossary:o:oss]] the potential for changes (particularly enhancements) needs to be assed also. | ||
| - | One way to accomplish this is to provided an assessment which is weighted for the "ease of implementation" for new features. For example, a system or product may not have done much to support [[dido:public:ra:1.4_req:2_nonfunc:25_security:confidentiality]], but the vendor of the product must determine that it is an easy upgrade to add it to the product. On the other hand, the support for [[dido:public:ra:xapend:xapend.a_glossary:c:confidentiality|confidentiality]] might be extremely difficult. Sometimes, the feature may be easy to solve but requires time and money to accomplish. As a potential stakeholder, they can direct resources to help overcome this shortfall. | + | One way to accomplish this is to provided an assessment which is weighted for the "ease of implementation" for new features. For example, a system or product may not have done much to support [[dido:public:ra:1.4_req:2_nonfunc:25_security:confidentiality]], but the vendor of the product must determine that it is an easy upgrade to add it to the product. On the other hand, the support for [[dido:public:ra:xapend:xapend.a_glossary:c:confidentiality|confidentiality]] might be extremely difficult. Sometimes, the feature may be easy to solve but requires time and money to accomplish. As a potential [[dido:public:ra:xapend:xapend.a_glossary:s:stakeholder|stakeholder]], they can direct resources to help overcome this shortfall. |
dido/public/ra/1.4_req/3_assessment/2_nonfunctional.1628698900.txt.gz ยท Last modified: 2021/08/11 12:21 by murphy
