Conceptual Modeling: Foundations and Applications

Volume 5600 of the series Lecture Notes in Computer Science pp 363-379

On Non-Functional Requirements in Software Engineering

  • Lawrence ChungAffiliated withDepartment of Computer Science, The University of Texas at Dallas
  • , Julio Cesar Sampaio do Prado LeiteAffiliated withDepartamento de Informática, Pontifícia Universidade Católica do Rio de Janeiro

* Final gross prices may vary according to local VAT.

Get Access


Essentially a software system’s utility is determined by both its functionality and its non-functional characteristics, such as usability, flexibility, performance, interoperability and security. Nonetheless, there has been a lop-sided emphasis in the functionality of the software, even though the functionality is not useful or usable without the necessary non-functional characteristics. In this chapter, we review the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.


Non-functional requirements NFRs softgoals satisficing requirements engineering goal-oriented requirements engineering alternatives selection criteria