Difference between revisions of "Solution requirement"
(Created page with "400px|thumb|right|[[Solution requirement]]Solution requirement (hereinafter, the ''Requirement'') is a characteristic of a solution that meets the...") |
(No difference)
|
Revision as of 21:56, 22 November 2018
Solution requirement (hereinafter, the Requirement) is a characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Types
- Functional requirement. Any requirement that refers to the product capabilities. In other words, a functional requirement describes what the product must do for its users. In systems engineering, a functional requirement is a particular behavior or metric to judge the operation of a system.
- Non-functional requirement(s). The quality attributes, design and implementation constraints, and external interfaces that the product must have.
- Technical requirement. A set of technical properties that a product must fulfill.
- Transition requirement(s). A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state, but that will not be needed once that transition is complete.
