skip to main content
10.1145/1774088.1774153acmconferencesArticle/Chapter ViewAbstractPublication PagessacConference Proceedingsconference-collections
research-article

An investigation into the notion of non-functional requirements

Authors Info & Claims
Published:22 March 2010Publication History

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.

References

  1. L. Chung, B. A. Nixon, E. Yu, and J. Mylopoulos, Non-functional requirements in software engineering. Massachusetts: Kluwer Academic Publishers, 2000.Google ScholarGoogle ScholarCross RefCross Ref
  2. D. Firesmith, "Using quality models to engineer quality requirements," Journal of Object Technology, vol. 2, pp. 67--75, 2003.Google ScholarGoogle ScholarCross RefCross Ref
  3. C. Ebert, "Putting requirement management into praxis: dealing with nonfunctional requirements," Information and Software Technology, vol. 40, pp. 175--185, 1998.Google ScholarGoogle ScholarCross RefCross Ref
  4. 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 ScholarGoogle Scholar
  5. G. Kotonya and I. Sommerville, Non-functional requirements, 1998.Google ScholarGoogle Scholar
  6. R. N. Charette, Applications strategies for risk analysis. New York: McGraw-Hill, 1990. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. K. E. Wiegers, Software requirements, 2nd ed. Washington: Microsoft Press, 2003. Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. I. Sommerville, Software Engineering, 7 ed. Essex, England: Pearson Education Limited, 2004. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. 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 ScholarGoogle Scholar
  10. 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 ScholarGoogle ScholarCross RefCross Ref
  11. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  12. D. R. Lindstrom, "Five ways to destroy a development project," IEEE Software, vol. 10, pp. 55--58, 1993. Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. B. Boehm and H. In, "Identifying quality-requirements conflict," IEEE Software, vol. 13, pp. 25--35, 1996. Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. N. G. Leveson and C. S. Turner, "An investigation of the Therac-25 accidents," IEEE Computer, vol. 26, pp. 18--41, 1993. Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  16. 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 ScholarGoogle ScholarCross RefCross Ref
  17. 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 ScholarGoogle Scholar
  18. 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 ScholarGoogle ScholarCross RefCross Ref
  19. G.-C. Roman, "A taxonomy of current issues in requirements engineering," Computer, vol. 18, pp. 14--23, 1985. Google ScholarGoogle ScholarDigital LibraryDigital Library
  20. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  21. 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 ScholarGoogle ScholarDigital LibraryDigital Library
  22. S. Lauesen, Software requirements: styles and techniques: Addison-Wesley, 2002. Google ScholarGoogle ScholarDigital LibraryDigital Library
  23. 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 ScholarGoogle Scholar
  24. M. Glinz, "Rethinking the notion of non-functional requirements," in Third World Congress for Software Quality, Munich, Germany, 2005, pp. 55--64.Google ScholarGoogle Scholar
  25. M. Glinz, "On non-functional requirements," in 15th IEEE International Requirements Engineering Conference (RE '07), 2007, pp. 21--26.Google ScholarGoogle ScholarCross RefCross Ref
  26. K. Krippendorff, Content analysis: and introduction to its methodology, Second ed. Thousand Oaks, USA: Sage Publications, Inc., 2004.Google ScholarGoogle Scholar
  27. R. P. Weber, Basic content analysis: Sage Publications, Inc., 1989.Google ScholarGoogle Scholar
  28. S. Stemler, "An overview of content analysis," Practical Assessment, Research & Evaluation, vol. 7, 2001.Google ScholarGoogle Scholar
  29. K. A. Neuendorf, The content analysis guidebook, First ed.: Sage Publications, Inc., 2001.Google ScholarGoogle Scholar
  30. D. E. Corporation, VAX VMS Software Source Book: Maynard, Mass, 1991.Google ScholarGoogle Scholar
  31. R. L. Glass and I. Vessey, "Contemporary application-domain taxonomies," IEEE Software, vol. 12, pp. 63--76, 1995. Google ScholarGoogle ScholarDigital LibraryDigital Library
  32. D. Firesmith, "Security use cases," Journal of Object Technology, vol. 2, pp. 53--64, 2003.Google ScholarGoogle Scholar
  33. D. Firesmith, "Engineering safety requirements, safety constraints, and safety-critical requirements," Journal of Object Technology, vol. 3, pp. 27--42, 2004.Google ScholarGoogle ScholarCross RefCross Ref
  34. D. Firesmith, "Specifying reusable security requirements," Journal of Object Technology, vol. 3, pp. 61--75, 2004.Google ScholarGoogle ScholarCross RefCross Ref

Index Terms

  1. An investigation into the notion of non-functional requirements

    Recommendations

    Comments

    Login options

    Check if you have access through your login credentials or your institution to get full access on this article.

    Sign in
    • Published in

      cover image ACM Conferences
      SAC '10: Proceedings of the 2010 ACM Symposium on Applied Computing
      March 2010
      2712 pages
      ISBN:9781605586397
      DOI:10.1145/1774088

      Copyright © 2010 ACM

      Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      • Published: 22 March 2010

      Permissions

      Request permissions about this article.

      Request Permissions

      Check for updates

      Qualifiers

      • research-article

      Acceptance Rates

      SAC '10 Paper Acceptance Rate364of1,353submissions,27%Overall Acceptance Rate1,650of6,669submissions,25%

    PDF Format

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader