On Non-Functional Requirements
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.
- University of Zurich Switzerland
1712 Software, 10009 Department of Informatics, 2207 Control and Systems Engineering, 000 Computer science, knowledge & systems
1712 Software, 10009 Department of Informatics, 2207 Control and Systems Engineering, 000 Computer science, knowledge & systems
selected citations These citations are derived from selected sources.This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).392 popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.Top 1% influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).Top 0.1% impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.Top 1%
Citations provided by BIP!Popularity provided by BIP!