dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq [2020/11/13 02:49] nick ↷ Page moved from dido:public:ra:xapend:xapend.glossary:n:nonfuncreq to dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq |
dido:public:ra:xapend:xapend.a_glossary:n:nonfuncreq [2021/10/04 11:24] (current) 85.208.98.29 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Non-Functional Requirements ===== | ===== Non-Functional Requirements ===== | ||
| - | [[dido:public:ra:xapend.glossary| Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| **Non-Functional Requirements** specify how the system should do it. Non-functional requirements do not affect the basic functionality of the system (hence the name, non-functional requirements). Even if the non-functional requirements are not met, the system will still perform its basic purpose. | **Non-Functional Requirements** specify how the system should do it. Non-functional requirements do not affect the basic functionality of the system (hence the name, non-functional requirements). Even if the non-functional requirements are not met, the system will still perform its basic purpose. | ||
| - | If a system will still perform without meeting the non-functional requirements, why are they important? The answer is usability. Non-functional requirements define system behavior, features, and general characteristics that affect the user experience. How well non-functional requirements are defined and executed determines how easy the system is to use, and is used to judge system [[dido:public:ra:xapend:xapend.glossary:p:performance|performance]]. Non-functional requirements are product properties and focus on user expectations. | + | If a system will still perform without meeting the non-functional requirements, why are they important? The answer is [[dido:public:ra:xapend:xapend.a_glossary:u:usability|usability]]. Non-functional requirements define system behavior, features, and general characteristics that affect the user experience. How well non-functional requirements are defined and executed determines how easy the system is to use, and is used to judge system [[dido:public:ra:xapend:xapend.a_glossary:p:performance|performance]]. Non-functional requirements are product properties and focus on user expectations. |
| - | See also [[dido:public:ra:xapend:xapend.glossary:f:funcreq]]. | + | See also [[dido:public:ra:xapend:xapend.a_glossary:f:funcreq]]. |
| Source: [[https://qracorp.com/functional-vs-non-functional-requirements/ | Non-Functional Requirements ]] | Source: [[https://qracorp.com/functional-vs-non-functional-requirements/ | Non-Functional Requirements ]] | ||
dido/public/ra/xapend/xapend.a_glossary/n/nonfuncreq.1605253776.txt.gz · Last modified: 2020/11/13 02:49 by nick
