Business Analysis

Types of Requirements, Prioritizing Business Requirements,

Documenting Business Requirements,
What is a Requirement?
BABoK A condition or capability needed by a stakeholder to be met
or possessed by a solution to solve a problem or achieve an objective

Wikipedia A singular documented need of a necessary attribute,

capability, characteristic or quality of a product or service in order for
it to have value and usability to the user.
Types of Requirements
Business Requirements
High-level statements of the goals, objectives, or needs of the
enterprise

It is NOT an indication of what the solution is.

Eg :- Ability to create a pension scheme before the payment comes in

Stakeholder Requirements
Statements of the needs of a particular Stakeholder or class of
Stakeholders

How a stakeholder will interact with the Solution

Eg :- Ability to type in the requirements of the pension scheme

Solution Requirements - Functional
Describes the behavior and information that the solution will manage

Eg :- Create an input screen for the needs of the scheme

Solution Requirements Non-Functional
The conditions under which the solution must remain effective or
qualities that the systems must have.

Performance, Usability, Reliability, Security, Availability, Scalability, etc.

are all types of Non Functional Requirements

Eg :- Ability to support a minimum of 15 systems creating schemes at

the same time
Solution Requirements Transition
The 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 typically cover data conversion from existing system, skill gaps
that must be addressed, and other related changes to reach the
desired future state

Eg :- Ability to enter 0 in the pension fields, before they are taken off.
List out the Requirements
At ABC pizza parlor, there are an average of 15 tables booked every
evening. To ensure quicker service to our customers and the ability to
service more customers at the same time, we want the ability to
ensure that the ordering process is sped up. The waiters take the
orders, which are then passed on to the kitchen on a kitchen order
ticket (kot). The kots are then processed and the order is then
furnished to the customer. The bill is made as the customers order is
processed.
Characteristics of a good requirement
Requirements MUST
be written in simple English
be complete sentences
have proper grammar, spelling and punctuation
be short and have direct sentences
be in active voice
adhere to the C4MUFT principle
1. Complete
2. Correct
3. Cohesive
4. Consistent
5. Modifiable
6. Unambiguous
7. Feasible
8. Testable
Requirements Attributes
Rather Metadata about Requirement
Descriptive property associated with the Requirement
Assists in Requirements Management
Typical Attributes:
Absolute Reference / ID
Author the Analyst who wrote the requirement
Source the Stakeholder who gave the requirement
Status the Status of the requirement
Risk the Risk to the solution/project associated with the requirement
Iteration the release/iteration in which the requirement will be considered for
implementation
Priority the priority of the requirement