Difference between revisions of "Non-Functional Requirements (glossary)"

From SEBoK
Jump to navigation Jump to search
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023")
 
(16 intermediate revisions by 5 users not shown)
Line 1: Line 1:
''<blockquote>Requirements under which the system is required to operate or exist or system properties and define how a system is supposed to be.</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====
+
===Source===
This definition was developed for the SEBoK version 0.5. ''Note to reviewers '':  If you are aware of a more authoritative definition, please provide this information in your review.  
+
This definition was developed for the SEBoK.
  
 
===Discussion===
 
===Discussion===
There is currently no discussion for this termThis will be completed for SEBoK version 1.0.
+
Non-functional requirements contrast with functional requirements that define what the system must be able to do or performTypical non-functional requirements include availability, reliability, maintainability, safety, and security.
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
{{DISQUS}}
+
<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.

SEBoK v. 2.9, released 20 November 2023