ABSTRACT
Although Non-Functional Requirements (NFRs) are recognized as very important contributors to the success of software projects, studies to date indicate that there is still no general consensus in the software engineering community regarding the notion of NFRs. This paper presents the result of an extensive and systematic analysis of the extant literature over three NFRs dimensions: (1) definition and terminology; (2) types; and (3) relevant NFRs in various types of systems and application domains. Two different perspectives to consider NFRs are described. A comprehensive catalogue of NFRs types as well as the top five NFRs that are frequently considered are presented. This paper also offers a novel classification of NFRs based on types of systems and application domains. This classification could assist software developers in identifying which NFRs are important in a particular application domain and for specific systems.
- L. Chung, B. A. Nixon, E. Yu, and J. Mylopoulos, Non-functional requirements in software engineering. Massachusetts: Kluwer Academic Publishers, 2000.Google ScholarCross Ref
- D. Firesmith, "Using quality models to engineer quality requirements," Journal of Object Technology, vol. 2, pp. 67--75, 2003.Google ScholarCross Ref
- C. Ebert, "Putting requirement management into praxis: dealing with nonfunctional requirements," Information and Software Technology, vol. 40, pp. 175--185, 1998.Google ScholarCross Ref
- R. T. Mittermeir, N. Roussopoulos, R. T. Yeh, and P. A. Ng, Modern software engineering, foundations and current perspectives. New York, NY, USA: Van Nostrand Reinhold Co, 1989.Google Scholar
- G. Kotonya and I. Sommerville, Non-functional requirements, 1998.Google Scholar
- R. N. Charette, Applications strategies for risk analysis. New York: McGraw-Hill, 1990. Google ScholarDigital Library
- K. E. Wiegers, Software requirements, 2nd ed. Washington: Microsoft Press, 2003. Google ScholarDigital Library
- I. Sommerville, Software Engineering, 7 ed. Essex, England: Pearson Education Limited, 2004. Google ScholarDigital Library
- M. Barbacci, M. H. Klein, T. A. Longstaff, and C. B. Weinstock, "Quality Attributes," CMU/SEI-95-TR-021 ESC-TR-95-021 1995.Google Scholar
- K. K. Breitman, J. C. S. Prado Leite, and A. Finkelstein, "The world's a stage: a survey on requirements engineering using a real-life case study," Journal of the Brazilian Computer Society, vol. 6, pp. 1--57, 1999.Google ScholarCross Ref
- A. Finkelstein and J. Dowell, "A comedy of errors: the London ambulance service case study," in Eigth International Workshop Software Specification and Design, 1996, pp. 2--5. Google ScholarDigital Library
- D. R. Lindstrom, "Five ways to destroy a development project," IEEE Software, vol. 10, pp. 55--58, 1993. Google ScholarDigital Library
- B. Boehm and H. In, "Identifying quality-requirements conflict," IEEE Software, vol. 13, pp. 25--35, 1996. Google ScholarDigital Library
- N. G. Leveson and C. S. Turner, "An investigation of the Therac-25 accidents," IEEE Computer, vol. 26, pp. 18--41, 1993. Google ScholarDigital Library
- H. In, "Conflict identification and resolution for software attribute requirements," in Faculty of the Graduate School vol. Doctor of Philosophy: University of Southern California, 1998. Google ScholarDigital Library
- D. J. Grimshaw and G. W. Draper, "Non-functional requirements analysis: deficiencies in structured methods," Information and Software Technology, vol. 43, pp. 629--634, 2001.Google ScholarCross Ref
- N. Heumesser, A. Trendowicz, D. Kerkow, H. Gross, and L. Loomans, "Essential and requisites for the management of evolution - requirements and incremental validation," Information Technology for European Advancement, ITEA-EMPRESS consortium 2003.Google Scholar
- N. Yusop, D. Zowghi, and D. Lowe, "The impacts of non-functional requirements in web system projects," International Journal of Value Chain Management vol. 2, pp. 18--32, 2008.Google ScholarCross Ref
- G.-C. Roman, "A taxonomy of current issues in requirements engineering," Computer, vol. 18, pp. 14--23, 1985. Google ScholarDigital Library
- J. Cleland-Huang, R. Settimi, O. B. Khadra, E. Berezhanskaya, and S. Cristina, "Goal-centric traceability for managing non-functional requirements," in ICSE 2005 St. Louis, Missouri, USA: ACM, 2005. Google ScholarDigital Library
- L. M. Cysneiros and J. C. S. do Prado Leite, "Nonfunctional requirements: from elicitation to conceptual models," IEEE Transaction on Software Engineering, vol. 30, pp. 328--350, 2004. Google ScholarDigital Library
- S. Lauesen, Software requirements: styles and techniques: Addison-Wesley, 2002. Google ScholarDigital Library
- B. Paech and D. Kerkow, "Non-functional requirements engineering - quality is essential," in 10th International Workshop on Requirements Engineering: Foundation for Software Quality, 2004, pp. 27--40.Google Scholar
- M. Glinz, "Rethinking the notion of non-functional requirements," in Third World Congress for Software Quality, Munich, Germany, 2005, pp. 55--64.Google Scholar
- M. Glinz, "On non-functional requirements," in 15th IEEE International Requirements Engineering Conference (RE '07), 2007, pp. 21--26.Google ScholarCross Ref
- K. Krippendorff, Content analysis: and introduction to its methodology, Second ed. Thousand Oaks, USA: Sage Publications, Inc., 2004.Google Scholar
- R. P. Weber, Basic content analysis: Sage Publications, Inc., 1989.Google Scholar
- S. Stemler, "An overview of content analysis," Practical Assessment, Research & Evaluation, vol. 7, 2001.Google Scholar
- K. A. Neuendorf, The content analysis guidebook, First ed.: Sage Publications, Inc., 2001.Google Scholar
- D. E. Corporation, VAX VMS Software Source Book: Maynard, Mass, 1991.Google Scholar
- R. L. Glass and I. Vessey, "Contemporary application-domain taxonomies," IEEE Software, vol. 12, pp. 63--76, 1995. Google ScholarDigital Library
- D. Firesmith, "Security use cases," Journal of Object Technology, vol. 2, pp. 53--64, 2003.Google Scholar
- D. Firesmith, "Engineering safety requirements, safety constraints, and safety-critical requirements," Journal of Object Technology, vol. 3, pp. 27--42, 2004.Google ScholarCross Ref
- D. Firesmith, "Specifying reusable security requirements," Journal of Object Technology, vol. 3, pp. 61--75, 2004.Google ScholarCross Ref
Index Terms
- An investigation into the notion of non-functional requirements
Recommendations
Are "non-functional" requirements really non-functional?: an investigation of non-functional requirements in practice
ICSE '16: Proceedings of the 38th International Conference on Software EngineeringNon-functional requirements (NFRs) are commonly distinguished from functional requirements by differentiating how the system shall do something in contrast to what the system shall do. This distinction is not only prevalent in research, but also ...
Automated classification of non-functional requirements
AbstractThis paper describes a technique for automating the detection and classification of non-functional requirements related to properties such as security, performance, and usability. Early detection of non-functional requirements enables them to be ...
An Ontological Approach to Specify Conflicts among Non-Functional Requirements
ICGDA '19: Proceedings of the 2019 2nd International Conference on Geoinformatics and Data AnalysisIt is a usual practice for a user to narrate the Non-Functional Requirements (NFRs) in natural language and the requirements engineers manually try to express the same, using semi-formal or formal language notations. However, inaccurate and the ...
Comments