On Non-Functional Requirements

Although the term 'non-functional requirement' has been in use for more than 20 years, there is still no consensus in the requirements engineering community what non-functional requirements are and how we should elicit, document, and validate them. On the other hand, there is a unanimous consensus that non-functional requirements are important and can be critical for the success of a project. This paper surveys the existing definitions of the term, highlights and discusses the problems with the current definitions, and contributes concepts for overcoming these problems.

[1]  M. Glinz,et al.  Modeling and Evolving Crosscutting Concerns in ADORA , 2007, Early Aspects at ICSE: Workshops in Aspect-Oriented Requirements Engineering and Architecture Design (EARLYASPECTS'07).

[2]  John Mylopoulos,et al.  Goal-Oriented Requirements Engineering, Part II , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

[3]  João Araújo,et al.  Multi-dimensional separation of concerns in requirements engineering , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[4]  Francisca Losavio,et al.  Characterizing a data model for software measurement , 2005, J. Syst. Softw..

[5]  A. V. Lamsweerde.  Goal-oriented requirements engineering: a guided tour , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[6]  Cornelius Ncube,et al.  A requirements engineering method for COTS-based systems development , 2000 .

[7]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[8]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[9]  Xavier Franch,et al.  Systematic formulation of non-functional characteristics of software , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[10]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[11]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[12]  Barry W. Boehm,et al.  Quantitative evaluation of software quality , 1976, ICSE '76.

[13]  Martin Glinz,et al.  Aspect-Oriented Modeling with Integrated Object Models , 2006, Modellierung.

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

[15]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[16]  J. M. Singer,et al.  IEEE Recommended Practice for Software Requirements SpeciÞcations , 1993 .

[17]  Standard Glossary of Software Engineering Terminology , 1990 .