An investigation into the notion of non-functional requirements

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.

[1]  T. Longstaff,et al.  Quality Attributes , 1995 .

[2]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[3]  Chris Ford,et al.  Non-Functional Requirements , 2007 .

[4]  Donald Firesmith,et al.  Using Quality Models to Engineer Quality Requirements , 2003, J. Object Technol..

[5]  Robert N. Charette,et al.  Applications Strategies for Risk Analysis , 1990 .

[6]  Ian Sommerville,et al.  Software Engineering (7th Edition) , 2004 .

[7]  Martin Glinz,et al.  On Non-Functional Requirements , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[8]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .

[9]  Steven E. Stemler,et al.  An Overview of Content Analysis. , 2001 .

[10]  Julio Cesar Sampaio do Prado Leite,et al.  Nonfunctional requirements: from elicitation to conceptual models , 2004, IEEE Transactions on Software Engineering.

[11]  Donald Firesmith,et al.  Engineering Safety Requirements, Safety Constraints, and Safety-Critical Requirements , 2004, J. Object Technol..

[12]  Donald Firesmith,et al.  Specifying Reusable Security Requirements , 2004, J. Object Technol..

[13]  David J Grimshaw,et al.  Non-functional requirements analysis: deficiencies in structured methods , 2001, Inf. Softw. Technol..

[14]  Julio Cesar Sampaio do Prado Leite,et al.  The world?s a stage: a survey on requirements engineering using a real-life case study , 1999, J. Braz. Comput. Soc..

[15]  Norazlin Yusop,et al.  The impacts of non-functional requirements in web system projects , 2008 .

[16]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[17]  Mark T True,et al.  Software Requirements , 2005 .

[18]  A. Finkelstein,et al.  A comedy of errors: the London Ambulance Service case study , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[19]  Kimberly A. Neuendorf,et al.  The Content Analysis Guidebook , 2001 .

[20]  Donald Firesmith,et al.  Security Use Cases , 2003, J. Object Technol..

[21]  Robert L. Glass,et al.  Contemporary Application-Domain Taxonomies , 1995, IEEE Softw..

[22]  David R. Lindstrom.  Five Ways to Destroy a Development Project , 1993, IEEE Softw..

[23]  Gruia-Catalin Roman,et al.  A taxonomy of current issues in requirements engineering , 1985, Computer.

[24]  C. Ebert.  Putting requirement management into praxis: dealing with nonfunctional requirements , 1998, Inf. Softw. Technol..

[25]  Hoh In,et al.  Conflict identification and resolution for software attribute requirements , 1998 .

[26]  S. Lauesen.  Software Requirements Styles and Techniques , 2001 .

[27]  R. Weber.  Basic Content Analysis , 1986 .

[28]  Martin Glinz,et al.  Rethinking the Notion of Non-Functional Requirements , 2005 .

[29]  Raymond T. Yeh,et al.  Modern Software Engineering: Foundations and Current Perspectives , 1989 .

[30]  Oussama Ben Khadra,et al.  Goal-centric traceability for managing non-functional requirements , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[31]  Klaus Krippendorff,et al.  Content Analysis: An Introduction to Its Methodology , 1980 .

[32]  Nancy G. Leveson,et al.  An investigation of the Therac-25 accidents , 1993, Computer.

[33]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..