Requirements are broadly dived in to six types.
- Business Requirement
- Stakeholder Requirement
- Solution Requirement
- Functional Requirement
- Non-Functional Requirement
- Transaction requirement
Business Requirement are higher-level statements of the goals, objectives and needs of the enterprise. They describe the reasons why a project has been initiated, the objectives that the project will achieve, and the metrics that will be used to measure its success. Business requirements describe needs of the organization as a whole, and not groups or stakeholders within it. They are developed and defined through enterprise analysis.
Stakeholder Requirements are statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Stakeholder requirements serve as a bridge between business requirements and the various classes of solution requirements. They are developed and defined through requirements analysis.
Solution requirement describe the characteristics of a solution that meet business requirements and stakeholder requirements.
They are developed and defined through requirements analysis.
They are frequently divided into sub-categories, particularly when the requirements describe a software solution1.Functional Requirement and 2.Non-Functional Requirement:
Functional Requirements describe the behavior and information that the solution will manage. They describe capabilities the system will be able to perform in terms of behaviors or operations.
Non-functional Requirements/ Quality or Supplementary requirements
Non-functional Requirements does not directly relate to the behavior or functionality of the solution, but rather describe environmental conditions under which the solution must remain effective or qualities that the systems must have. They are also known as quality or supplementary requirements. These can include requirements related to capacity, speed, security, availability and the information architecture and presentation of the user interface.
Transition Requirements describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to a desired future state, but that will not be needed once that transition is complete.
They are differentiated from other requirements types because they are always temporary in nature and because they cannot be developed until both an existing and new solution are defined.
They typically cover data conversion from existing systems, skill gaps that must be addressed, and other related changes to reach the desired future state. They are developed and defined through solution assessment and validation.