ddsf:public:guidebook:06_append: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 | ||
|
ddsf:public:guidebook:06_append:glossary:n:nonfuncreq [2021/03/17 16:24] admin ↷ Links adapted because of a move operation |
ddsf:public:guidebook:06_append:glossary:n:nonfuncreq [2021/07/14 16:43] (current) murphy ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Non-Functional Requirements ===== | ===== Non-Functional Requirements ===== | ||
| - | [[ddsf:private:guidebook:06_append:glossary| Return to Glossary ]] | + | [[ddsf:public:guidebook:06_append: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 [[ddsf:private:guidebook:06_append: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 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 [[ddsf:public:guidebook:06_append:glossary:p:performance|performance]]. Non-functional requirements are product properties and focus on user expectations. |
| - | See also [[ddsf:private:guidebook:06_append:glossary:f:funcreq]]. | + | See also [[ddsf:public:guidebook:06_append: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 ]] | ||
ddsf/public/guidebook/06_append/glossary/n/nonfuncreq.1616012653.txt.gz · Last modified: 2021/03/17 16:24 by admin
