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 t
On Non-Functional Requirements
Martin Glinz
Department of Informatics, University of Zurich, Switzerland
glinz@ifi.uzh.ch
requirements concerning the functionality of a system Abstract
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 over-coming these problems.
1. Introduction
If you want to trigger a hot debate among a group of requirements engineering people, just let them talk about non-functional requirements. Although this term has been in use for more than two decades, there is still no consensus about the nature of non-functional re-quirements and how to document them in requirements specifications.
This paper is an attempt to work out and discuss the problems that we have with the notion of non-func-tional requirements and to contribute concepts for overcoming these problems. The focus is on system (or product) requirements; the role of non-functional re-quirements in the software process is not discussed [16].
The paper is organized as follows. Section 2 sur-veys typical definitions for the terms ‘functional re-quirement’ and ‘non-functional requirement’. The problems with these definitions are discussed in Sec-tion 3. Section 4 presents concepts about how these problems can be overcome or at least alleviated. The paper ends with a discussion of these concepts.
and other requirements.
There is a rather broad consensus about how to de-fine the term ‘functional requirements’. The existing definitions follow two threads that coincide to a large extent. In the first thread, the emphasis is on functions: a functional requirement specifies “a function that a system (...) must be able to perform” [6], “what the product must do” [18], “what the system should do” [20]. The second thread emphasizes behavior: func-tional requirements “describe the behavioral aspects of a system” [1]; behavioral requirements are “those re-quirements that specify the inputs (stimuli) to the sys-tem, the outputs (responses) from the system, and be-havioral relationships between them; also called func-tional or operational requirements.” [3].
Wiegers as well as Jacobson, Rumbaugh and Booch try a synthesis: “A statement of a piece of required functionality or a behavior that a system will exhibit under specific conditions.” [21]; “A requirement that specifies an action that a system must be able to per-form, without considering physical constraints; a re-quirement that specifies input/output behavior of a system.” [10].
There is only one semantic difference that may arise between the different definitions: timing requirements may be viewed as behavioral, while they are not func-tional. However, most publications in RE consider timing requirements to be performance requirements which in turn are classified as non-functional require-ments.
On the other hand, there is no such consensus for non-functional requirements. Table 1 gives an over-view of selected definitions from the literature or the web, which – in my opinion – are representative of the definitions that exist.
3. Where is the problem?
The problems that we currently have with the notion of non-functional requirements can be divided into definition problems, classification problems and repre-sentation problems.
2. Defining the term
In every current requirements classification (for ex-ample [7], [11], [12]), we find a distinction between
Proceedings of the 15th IEEE International Requirements Engineering Conference, Delhi, India.
A fact that end-user has no or very little influence on component’ functionality promoted nons functional requirements which are getting more attention ...
Using Non-Functional Requirements to Systematically Select Among Alternatives in Architectu Non-functional requirements, such as modifiability, performance, ...
(MOP) is a powerful mechanism to control the behavior of an application and to implement non-functional requirements such as fault-tolerance and distributed...
On Non-Functional Requir... 6页 免费 Pontis 5.0 Functional Re... 82...12/21/2004 GlobalPlatform Smart Card Management System Functional Requirements ...
Functional vs. non-functional requirements H Functional requirements: ? output...H Power consumption: Should run for 8 hours on four AA batteries. GPS ...
? ? Focus on understanding the solution Operations and Attributes Performance Close to real code Object lifecycles Non-functional requirements A large model ...
Non-Functional Requirements (NFR) (1) ? Non-functional requirements are ...May be new functional requirements, constraints on existing requirements, or ...
The requirements are written first so that we and our customers agree on ...non-functional requirements Functional: describes an interaction between the ...
10.Describe four types of non-functional requirements that may be placed on a system. Give examples of each of these types of requirement. A:There ...
Functional safety Engineering - Safety Requirement Specification Extended ...on loss of power to the SIS Response time requirements for the SIS to ...
热门文档