====== 4.4 Assessing Requirements ======
[[dido:public:ra:1.4_req |Return to Requirements ]]

An important part of having functional and non-functional requirements is access a particular effort to determine if the effort complies with the requirements. The approach is slightly different between Functional and non-functional requirements. 

For [[dido:public:ra:xapend:xapend.a_glossary:f:funcreq | Functional Requirements]], it is important to think about what requirements need to be covered for a particular effort. For example, which [[dido:public:ra:1.4_req:1_func:platform:net_arch | Networks]] need to be supported? ([[dido:public:ra:xapend:xapend.a_glossary:w:wired]], [[dido:public:ra:xapend:xapend.a_glossary:w:wireless]]. [[dido:public:ra:xapend:xapend.a_glossary:b:bluetooth]], [[dido:public:ra:xapend:xapend.a_glossary:z:zigbee]], [[dido:public:ra:xapend:xapend.a_glossary:n:nfc]], etc).

[[dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq |Non-functional Requirements]] often have a large impact on the components that are selected as part of the infrastructure. For example, if a component is not [[dido:public:ra:xapend:xapend.a_glossary:s:scalable|scalable]], the product built using that component is probably also not scalable. 

The following sections are meant as aids in helping evaluate a project Functional and Non-FUnctional Requirements.

  * [[dido:public:ra:1.4_req:3_assessment:1_functional:start]]
  * [[dido:public:ra:1.4_req:3_assessment:2_nonfunctional]]

/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says 
  ~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~