||This article includes a list of references, but its sources remain unclear because it has insufficient inline citations. (May 2012) (Learn how and when to remove this template message)|
Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describing all the cases where the system uses the functional requirements are captured in use cases. Functional requirements are supported by non-functional requirements (also known as quality requirements), which impose constraints on the design or implementation (such as performance requirements, security, or reliability). Generally, functional requirements are expressed in the form "system must do <requirement>", while non-functional requirements are "system shall be <requirement>". The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture.
As defined in requirements engineering, functional requirements specify particular results of a system. This should be contrasted with non-functional requirements which specify overall characteristics such as cost and reliability. Functional requirements drive the application architecture of a system, while non-functional requirements drive the technical architecture of a system.
In some cases a requirements analyst generates use cases after gathering and validating a set of functional requirements. The hierarchy of functional requirements is: user/stakeholder request → feature → use case → business rule. Each use case illustrates behavioral scenarios through one or more functional requirements. Often, though, an analyst will begin by eliciting a set of use cases, from which the analyst can derive the functional requirements that must be implemented to allow a user to perform each use case.
A typical functional requirement will contain a unique name and number, a brief summary, and a rationale. This information is used to help the reader understand why the requirement is needed, and to track the requirement through the development of the system.
The crux of the requirement is the description of the required behavior, which must be clear and readable. The described behavior may come from organizational or business rules, or it may be discovered through elicitation sessions with users, stakeholders, and other experts within the organization. Many requirements may be uncovered during the use case development. When this happens, the requirements analyst may create a placeholder requirement with a name and summary, and research the details later, to be filled in when they are better known.
- Function (computer science)
- Function (engineering)
- Function (mathematics)
- Function point
- Functional decomposition
- Functional design
- Functional model
- Separation of concerns
- Roman, G.-C. (1985) "A taxonomy of current issues in requirements engineering" Computer, April 1985 Volume: 18 Issue: 4, pp. 14–23, ISSN 0018-9162.
- R. T. Yeh (1982) "Requirements Analysis- A Management Perspective," Proc. COMPSAC '82, Nov. 1982, pp. 410–416.
- Wiegers, Karl E. (2003). Software Requirements (2nd ed.). Redmond: Microsoft Press. ISBN 978-0-7356-1879-4.
- Stellman, Andrew; Greene, Jennifer (2005). Applied Software Project Management (1st ed.). Cambridge, MA: O'Reilly Media. ISBN 978-0-596-00948-9.
- Sommerville, Ian (2006). Software Engineering (8th ed.). ISBN 978-0-321-31379-9.