By:

Deepali Bhardwaj



7/6/2014 2 Understanding Requirements
7/6/2014 3 Understanding Requirements
Set of tasks and techniques to liaison with the stakeholders
to understand the operations, policies, structure of an
organization and to recommend solutions that enable
organizations to achieve their goals
A solution is a set of changes to the current state of an
organization that are made in order to enable that
organization to meet a business need, solve a problem, or
take advantage of an opportunity
Most solutions are a system of interacting solution
components, each of which are potentially solutions in
their own right
What is Business Analysis
7/6/2014 4 Understanding Requirements
Bridge between User and Solutioning (Technical) Team
Must know Customers industry and domain
Business processes
Laws and policies
Competition
Technical solutions and products
Must have the technical know-how to affectively
communicate with the technical team and ensure the
customers needs are met
Business Analyst
7/6/2014 5 Understanding Requirements
Scoping the project: Through project proposal and
initiation understand the high level scope and objectives of
the project
Req. Analysis: Play a key role in establishing
Requirements(functional and non-functional) during
Analysis
Communication: Clearly and accurately communicate the
requirements to the technical team ensure minimum gap
between expectations of end users and the deliverable from
the technical team
Documentation: Analysis and documentation of
requirements to be precise and clearly understandable by
all

R&R For Business Analyst
7/6/2014 6 Understanding Requirements
Validation and Review: Regular interactions with the leads
and development teams to ensure correct knowledge
transfer and understanding by the technical team
Req. Traceability: Responsible for requirements traceability
to ensure no gaps in requirements analysis during
development phase
Testing: Key role in testing phase where BA does the
systems testing (black box testing) and provides support
during user acceptance testing
Change Management: Plays a key role in change
management during and after implementation of the
system

R&R For Business Analyst
7/6/2014 7 Understanding Requirements
Analytical thinking and problem solving
Behavioral characteristics to enable effective working
relationships with stakeholders like trustworthiness, ethics
etc
Business knowledge
Techniques to gather and understand requirements
Use Case Analysis, Process flows, Data flows, ERD
Ability to understand and capture both, data and process flows
Communication skills
Facilitation skills


Competencies Required
7/6/2014 8 Understanding Requirements
Condition or a capability needed by the stakeholder to
either solve a problem or achieve an objective

A condition or capability that must be met or
possessed by a solution or solution component to
satisfy a contract, standard, specification

Requirement may be explicit or implicit, unstated or
derived from other requirements
What Is A Requirement?
7/6/2014 9 Understanding Requirements
Business requirement
Describe the objectives that the project will achieve and
the metrics that will be used to measure its success
Objectives can also cover constraints on time-to-market,
compliance with regulatory and governance frameworks ,
compatibility with organizational processes etc
Through Enterprise Analysis
Stakeholder requirement
Needs that every stakeholder has and how each
stakeholder will interact with a solution
Through Requirement Analysis

Dimensions Of Is A Requirement?
7/6/2014 10 Understanding Requirements
Solution requirement
Describes the characteristics of the solution
Through Requirement Analysis
Solution requirements will have
Functional
Related to business functionality of the solution
Non-Functional
Environmental conditions under which the solution
must remain effective or the qualities that the system
must have
Include requirement related to capacity, security, speed,
availability, information architecture and UI
presentation
Solution Requirement
7/6/2014 11 Understanding Requirements
Capabilities that the system must have to transition
from the current to the desired future state
Will not be needed once the transition is complete e.g.
Data conversion, skill gaps and other changes needed
to get to the desired state
Defined through solution assessment and validation
Transition Requirement
7/6/2014 12 Understanding Requirements
Limited access to stakeholders
Conflicting priorities
Customers dont know what they want
Customers change their mind
Getting the RIGHT SMEs
Missing requirements
Not separating the What from the How


Challenges With Requirements
7/6/2014 13 Understanding Requirements
Jumping into the details too early
Not thinking outside the current box
Too much focus on one type of requirement
Developers dont understand the problem domain
No clear definition of Done


Challenges With Requirements
7/6/2014 14 Understanding Requirements
Requirements Lifecycle
Identification
of a Need
T
e
c
h
n
o
l
o
g
y

RFP
7/6/2014 15 Understanding Requirements
Requirements And SDLC
7/6/2014 16 Understanding Requirements
Requirement Engineering
Requirement
Definition
Requirement
Specification
Requirement
Validation
Requirement
Management
7/6/2014 17 Understanding Requirements