NON-FUNCTIONAL REQUIREMENT

Systems Engineering Glossary

Systems Engineering — Systems Engineering — Requirements Engineering — Requirements Management — Non-Functional Requirement

 

 

 

 

 

 

Argos Home

 

 		 
 


Information on Non-Functional Requirement

While a functional requirement defines the services and functions that the system should provide, a non-functional requirement describes the qualities or attributes that it must posses. A non-functional requirement may also describe the constraints under which the system should operate, and on the way in which the system is to be developed. A non-functional requirement could also provide definitions of system interfaces and information about the application domain of the system (for example, how to carry out particular types of computation).


Other topics in our resources on Systems Engineering related to Non-Functional Requirement include: 
 
  • Constraint
  • Verification Requirement
  • Requirements Elicitation
    		•
  • Requirements Traceability
  • Functional Requirement
  • Requirements Allocation
    		•
  • Derived Requirement
  • Performance Requirement
  • Requirements Negotiation

    •  

    If you would like to suggest related entries to be added to the glossary, please contact Argos Press. Please also contact Argos Press to request permission to reproduce, broadcast, adapt and communicate our content (including this glossary entry on Non-Functional Requirement). © Argos Press Pty Ltd, Canberra, 2003-2004. All rights reserved.