More Web Proxy on the site http://driver.im/

research-article

An investigation into the notion of non-functional requirements

Authors:

Nurie NurmulianiAuthors Info & Claims

SAC '10: Proceedings of the 2010 ACM Symposium on Applied Computing

Pages 311 - 317

https://doi.org/10.1145/1774088.1774153

Published: 22 March 2010 Publication 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.

[2]

D. Firesmith, "Using quality models to engineer quality requirements," Journal of Object Technology, vol. 2, pp. 67--75, 2003.

[3]

C. Ebert, "Putting requirement management into praxis: dealing with nonfunctional requirements," Information and Software Technology, vol. 40, pp. 175--185, 1998.

[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.

[5]

G. Kotonya and I. Sommerville, Non-functional requirements, 1998.

[6]

R. N. Charette, Applications strategies for risk analysis. New York: McGraw-Hill, 1990.

Digital Library

[7]

K. E. Wiegers, Software requirements, 2nd ed. Washington: Microsoft Press, 2003.

Digital Library

[8]

I. Sommerville, Software Engineering, 7 ed. Essex, England: Pearson Education Limited, 2004.

Digital 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.

[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.

[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.

Digital Library

[12]

D. R. Lindstrom, "Five ways to destroy a development project," IEEE Software, vol. 10, pp. 55--58, 1993.

Digital Library

[13]

B. Boehm and H. In, "Identifying quality-requirements conflict," IEEE Software, vol. 13, pp. 25--35, 1996.

Digital Library

[14]

N. G. Leveson and C. S. Turner, "An investigation of the Therac-25 accidents," IEEE Computer, vol. 26, pp. 18--41, 1993.

Digital 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.

Digital 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.

[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.

[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.

[19]

G.-C. Roman, "A taxonomy of current issues in requirements engineering," Computer, vol. 18, pp. 14--23, 1985.

Digital 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.

Digital 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.

Digital Library

[22]

S. Lauesen, Software requirements: styles and techniques: Addison-Wesley, 2002.

Digital 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.

[24]

M. Glinz, "Rethinking the notion of non-functional requirements," in Third World Congress for Software Quality, Munich, Germany, 2005, pp. 55--64.

[25]

M. Glinz, "On non-functional requirements," in 15th IEEE International Requirements Engineering Conference (RE '07), 2007, pp. 21--26.

[26]

K. Krippendorff, Content analysis: and introduction to its methodology, Second ed. Thousand Oaks, USA: Sage Publications, Inc., 2004.

[27]

R. P. Weber, Basic content analysis: Sage Publications, Inc., 1989.

[28]

S. Stemler, "An overview of content analysis," Practical Assessment, Research & Evaluation, vol. 7, 2001.

[29]

K. A. Neuendorf, The content analysis guidebook, First ed.: Sage Publications, Inc., 2001.

[30]

D. E. Corporation, VAX VMS Software Source Book: Maynard, Mass, 1991.

[31]

R. L. Glass and I. Vessey, "Contemporary application-domain taxonomies," IEEE Software, vol. 12, pp. 63--76, 1995.

Digital Library

[32]

D. Firesmith, "Security use cases," Journal of Object Technology, vol. 2, pp. 53--64, 2003.

[33]

D. Firesmith, "Engineering safety requirements, safety constraints, and safety-critical requirements," Journal of Object Technology, vol. 3, pp. 27--42, 2004.

[34]

D. Firesmith, "Specifying reusable security requirements," Journal of Object Technology, vol. 3, pp. 61--75, 2004.

Cited By

Yu LAlégroth EChatzipetrou PGorschek T(2024)A Roadmap for Using Continuous Integration EnvironmentsCommunications of the ACM10.1145/363151967:6(82-90)Online publication date: 12-Apr-2024
https://dl.acm.org/doi/10.1145/3631519
Kiomba Kambilo EHerbaut NRychkova ISouveyet C(2024)Configuration of Software Product Lines Driven by the Softgoals: The TEAEM ApproachThe Practice of Enterprise Modeling10.1007/978-3-031-77908-4_16(262-278)Online publication date: 30-Nov-2024
https://doi.org/10.1007/978-3-031-77908-4_16
Romera LGonzález JLezcano ACarruthers JIrrazábal E(2024)Towards Optimal Non-functional Requirements Elicitation and Documentation in Agile Software Development: A Case StudyComputer Science – CACIC 202310.1007/978-3-031-62245-8_11(151-164)Online publication date: 23-Jun-2024
https://doi.org/10.1007/978-3-031-62245-8_11
Show More Cited By

Index Terms

An investigation into the notion of non-functional requirements
1. Software and its engineering
  1. Software creation and management
    1. Designing software
      1. Requirements analysis

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 Engineering

Non-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
Abstract
This 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 Analysis

It 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

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

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

Conference Chairs:
Sung Y. Shin
South Dakota State University
,
Sascha Ossowski
University Rey Juan Carlos, Spain
,
Michael Schumacher
University of Applied Sciences Western Switzerland, Switzerland
,
Program Chairs:
Mathew J. Palakal
Indiana University Purdue University
,
Chih-Cheng Hung
Southern Polytechnic State University

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]

Sponsors

SIGAPP: ACM Special Interest Group on Applied Computing

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 22 March 2010

Permissions

Request permissions for this article.

Request Permissions

Check for updates

Author Tags

Qualifiers

Research-article

Conference

SAC'10

Sponsor:

SIGAPP

SAC'10: The 2010 ACM Symposium on Applied Computing

March 22 - 26, 2010

Sierre, Switzerland

Acceptance Rates

SAC '10 Paper Acceptance Rate 364 of 1,353 submissions, 27%;

Overall Acceptance Rate 1,650 of 6,669 submissions, 25%

Upcoming Conference

SAC '25

Sponsor:
sigapp

The 40th ACM/SIGAPP Symposium on Applied Computing

March 31 - April 4, 2025

Catania , Italy

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

73
Total Citations
View Citations
1,982
Total Downloads

Downloads (Last 12 months)170
Downloads (Last 6 weeks)20

Reflects downloads up to 21 Dec 2024

Other Metrics

View Author Metrics

Citations

Cited By

Yu LAlégroth EChatzipetrou PGorschek T(2024)A Roadmap for Using Continuous Integration EnvironmentsCommunications of the ACM10.1145/363151967:6(82-90)Online publication date: 12-Apr-2024
https://dl.acm.org/doi/10.1145/3631519
Kiomba Kambilo EHerbaut NRychkova ISouveyet C(2024)Configuration of Software Product Lines Driven by the Softgoals: The TEAEM ApproachThe Practice of Enterprise Modeling10.1007/978-3-031-77908-4_16(262-278)Online publication date: 30-Nov-2024
https://doi.org/10.1007/978-3-031-77908-4_16
Romera LGonzález JLezcano ACarruthers JIrrazábal E(2024)Towards Optimal Non-functional Requirements Elicitation and Documentation in Agile Software Development: A Case StudyComputer Science – CACIC 202310.1007/978-3-031-62245-8_11(151-164)Online publication date: 23-Jun-2024
https://doi.org/10.1007/978-3-031-62245-8_11
Lessa LEtoribussi A(2023)Usability of Security Mechanisms of E-Health ApplicationsFraud Prevention, Confidentiality, and Data Security for Modern Businesses10.4018/978-1-6684-6581-3.ch002(37-56)Online publication date: 20-Jan-2023
https://doi.org/10.4018/978-1-6684-6581-3.ch002
Costa LCastro JKelner JJeronimo BLencastre MPastor Ó(2023)On The Quest of Trust Requirements for Socially Assistive Robots2023 IEEE 31st International Requirements Engineering Conference Workshops (REW)10.1109/REW57809.2023.00051(252-261)Online publication date: Sep-2023
https://doi.org/10.1109/REW57809.2023.00051
Rolwes AStellbauer PLungershausen UČubela DBöhm KNeis P(2023)MAATSE: Prototyping and Evaluating an Open and Modular E-Assessment Tool for STEM Education2023 IEEE 2nd German Education Conference (GECon)10.1109/GECon58119.2023.10295151(1-6)Online publication date: 2-Aug-2023
https://doi.org/10.1109/GECon58119.2023.10295151
Sherif EHelmy WGalal-Edeen G(2023)Proposed Framework to Manage Non-Functional Requirements in AgileIEEE Access10.1109/ACCESS.2023.328119511(53995-54005)Online publication date: 2023
https://doi.org/10.1109/ACCESS.2023.3281195
Monaco RLiu XMurino TCheng XNielsen P(2023)A non-functional requirements-based ontology for supporting the development of industrial energy management systemsJournal of Cleaner Production10.1016/j.jclepro.2023.137614414(137614)Online publication date: Aug-2023
https://doi.org/10.1016/j.jclepro.2023.137614
Yu LAlégroth EChatzipetrou PGorschek T(2023)Automated NFR testing in continuous integration environments: a multi-case study of Nordic companiesEmpirical Software Engineering10.1007/s10664-023-10356-128:6Online publication date: 24-Oct-2023
https://doi.org/10.1007/s10664-023-10356-1
Nurwidyantoro AShahin MChaudron MHussain WPerera HShams RWhittle J(2023)Integrating human values in software development using a human values dashboardEmpirical Software Engineering10.1007/s10664-023-10305-y28:3Online publication date: 18-Apr-2023
https://dl.acm.org/doi/10.1007/s10664-023-10305-y
Show More Cited By

View Options

Login options

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

Full Access

Get this Publication

View options

PDF

View or Download as a PDF file.

eReader

View online with eReader.

Media

Figures

Other

Tables

View Table of Contents