Abstract
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. © 2009 Springer Berlin Heidelberg.
Author supplied keywords
Cite
CITATION STYLE
Chung, L., & Do Prado Leite, J. C. S. (2009). On non-functional requirements in software engineering. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 5600 LNCS, pp. 363–379). https://doi.org/10.1007/978-3-642-02463-4_19
Register to see more suggestions
Mendeley helps you to discover research relevant for your work.
