Business Requirements

statements of goals, objectives, and outcomes that describe why a change has been initiated.

• “We need to improve our Marketing effectiveness through data capabilities”

Stakeholder Requirements

describe the needs of stakeholders that must be met in order to achieve the business requirements.

• “The Non technically Marketing team will need to be able to access the data to help inform decisions”

Solution Requirements

describe the capabilities and qualities of a solution that meets the business and stakeholder requirements.

Solution Requirements are divided into two sub categories. Solution requirements are details and the formality and detail they hold is appropriate for delivery and implementation of the solution.

[!tip] Thought… A potentially useful way to think about functional vs non-functional requirements is to ask what to solution does vs what is has. The solution has functional requirements is does non-functional requirements. For instance;

My computer

• has a graphics card (functional requirement)
• does allow me to play games (non-functional requirement)

This Government program

• has a login page (Functional)
• does meet code of ethics (non-functional)

Functional Requirements

describe the capabilities that a solution must have in terms of the behaviour and information that the solution will manage

An example of functional requirement might be;

• solution has a login page
• solution has a connection to ethernet
• solution has a sugar content lower then 0.12 grams

Non-functional Requirements

do not relate directly to the behaviour of functionality of the solution, but rather describe conditions under which a solution must remain effective or qualities that a solution must have.

An example of a non-functional requirement might be;

• Solution must work in a capacity which is in accordance with government regulation.
• Solution must maintain 95% uptime during peak loads
• Solution must work given 65% staffing reduction

Transition Requirement

describe the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete.

• “We will need a training program for the marketing team to get them up to speed on the solution”

[!tip] In practice A company wants to rework an old piano midi controller into a new electric piano which perfectly mimic a church organ. (for some reason)

Business Requirement

• We want to move to a new design for our current product which better performs in the market.
• We want a to have a product in our catalogue which perfectly mimics a church organ.

Stakeholder Requirement

• Users will feel like they are playing a church organ right in there living room
• Users will have assess to all the knobs and buttons they would if they were a professional organist.

Functional Requirement

• Product must have 154 actuated key inputs.
• Product must have 32 floor pedals and 2 61 key keyboards
• Product must be portable

Non-Functional Requirement

• Product must sound great in a home living room
• Product must last 50 years (so we can have a great warranty)
• Product must be manufactured in the current production facility.

Transition Requirement

• A consultant will be hired to work out how to update the tooling
• A Rep will be Hired to work with retailer on the new product launch