I have recently revisited the definition of a “Requirement”. Traditionally it is area for almost endless debate and argument, But the categorisation below seems to work for me…

Business Requirements

High-level statements of the goals, objectives, or 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

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 Requirements

Describe the characteristics of the solution. The solution must meet business requirements and stakeholder requirements.

Within Solution Requirements, we have:

    Functional Requirements: Which 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—specific information technology application actions or responses.
    Non-functional Requirements: Capture conditions that do 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

As I understand it, transition requirements describe capabilities an organisation must have in order to facilitate transition from the current state of the enterprise to a desired future state. Theoretically, this isn’t long-term. It is only needed to do the transition. They are different 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. Training and development is an obvious example.

« »