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 while non-functional requirements are "system shall be The plan for 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 logistics conference paper In 1953 divided "requirements for data processing equipment Into two groups: functional requirements and performance The concept of functional and non-functional requirements was SIT presented in 1982 at the Computer Software and Application conference by R.
T. Yah. Functional requirements are also addressed in detail by G. C. Roman in April 1 985 edition of Computer titled "A taxonomy of current issues in requirements engineering" In which he addresses attributes of a functional requirement. Process[edit source I ] 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 felicitation 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.