Difference between revisions of "Non-Functional Requirements (glossary)"
Jump to navigation
Jump to search
(Created page with '''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow ...') |
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023") |
||
| (22 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
| − | ''<blockquote> | + | ''<blockquote>Quality attributes or characteristics that are desired in a system, that define how a system is supposed to be.'' (Created for SEBoK)</blockquote> |
| − | + | ===Source=== | |
| − | + | This definition was developed for the SEBoK. | |
===Discussion=== | ===Discussion=== | ||
| − | + | Non-functional requirements contrast with functional requirements that define what the system must be able to do or perform. Typical non-functional requirements include availability, reliability, maintainability, safety, and security. | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| + | <center>'''SEBoK v. 2.9, released 20 November 2023'''</center> | ||
Latest revision as of 23:18, 18 November 2023
Quality attributes or characteristics that are desired in a system, that define how a system is supposed to be. (Created for SEBoK)
Source
This definition was developed for the SEBoK.
Discussion
Non-functional requirements contrast with functional requirements that define what the system must be able to do or perform. Typical non-functional requirements include availability, reliability, maintainability, safety, and security.