Beruflich Dokumente
Kultur Dokumente
Guruprasad R
rgp1981@gmail.com
+91-8971050233
What is Business Analysis?
Model the
Organization
Realize Understand
Needed
Benefits Capabilities
• Requirements Analyst
• Systems Analyst
• Data Analyst
Guruprasad R
rgp1981@gmail.com
+91-8971050233
Categories of Requirements
• The product must track recipes down the ingredient and quantity level
• The product must track ingredients including their cost, vendors, and quantity in
inventory
• The product must interact with the current Point of Sale system
Non-Functional Requirements
• The product shall only allow bakers and administrators to view recipes
• Best Practices
Business Rules Explained
Definition:
A business rule is a rule that defines or constrains some aspect
of business and always resolves to either true or false.
Purpose:
Business rules are intended to assert business structure or to control or
influence the behavior of the business.
Business Rules Examples
Rule:
• Each course must have at least one instructor
Possible Requirements:
• Able to create an instructor
Rule:
• Customers must have a valid driver’s license to rent a vehicle
Possible Requirements:
• Employee to inspect driver’s license (if it is in a database)
Rule:
• A quote must be completed prior to an invoice being generated
Possible Requirements:
• Capability to enter a quote
• What is a stakeholder?
• Project team members
• Customer
• Suppliers
• Employees/Unions
• Regulators Eg: FDA in Pharma
• Any individual impacted by the project
• Any individual to support the project
Identifying Stakeholders
• Additional ideas
• Varied perspectives
• Gains buy-in
Identifying Stakeholders
• Government officials
President
Dough-C-Dough
Vice President
Executive Suppliers Bake Goods R Us
Head of Operations Management
Dough-Licious
System
Cashier
Order Placer
Customers Employees
Baker
Goods Consumer
Shopper
Store Management
Organizational Chart
CEO
Executive
x5555
Homer Owner
Responsible
Accountable
Consulted
Informed
RACI Matrix: An Overview
RACI Matrix: R.A.C.I.
Responsible
• Who’s head will roll if this goes wrong?
Accountable
• Who has the authority to sign off the
Consulted work?
Informed
RACI Matrix: R.A.C.I.
Responsible
Accountable
• Who can tell me more about this task?
Consulted
• Who are the Subject Matter Experts?
Informed
RACI Matrix: R.A.C.I.
Responsible
Accountable
Consulted
• Who’s work depends on this task?
Informed
• Who has to be kept update about the
progress?
RACI Matrix: Breakdown
RACI Matrix: Breakdown
RACI Matrix: Breakdown
Phases of the Requirements Process
1. Requirement Elicitation
2. Requirement Analysis
3. Requirement Specification
4. Requirements Approval
Sub disciplines of software requirements
engineering
Requirement development process
Business Analysis-
Requirements Elicitation
Guruprasad R
rgp1981@gmail.com
+91-8971050233
Phases of the Requirements Process
1. Requirement Elicitation
2. Requirement Analysis
3. Requirement Specification
4. Requirements Approval
Questioning
1 Questioning Skill’s
o A good question is always based on some assumptions about the person being
questioned.
o A good question is framed such that the person being questioned is clear about
the information required.
Questioning
Open-Ended Questions - Such questions do not restrict responses to
specifics.
• Personal interviews
• Scripted questions – interviewee’s answers are documented
• Exploratory questions to clarify and validate requirements, while removing assumptions
• Job shadowing/Customer site visits
• Walk through a work day with a user or user group observing them
• Understand operational environment to discover prerequisites for job success
• Task analysis
• Ask end-users to walk through their current jobs
• Show as-is process in order to identify essential and frequent tasks
• Interviewer asks questions to understand what works well and what doesn’t
Interviewing: Best Practices
• One person conducts interview while the other documents the answers.
Always record the interview.
Interviewing: Best Practices (continued)
• Interview two to three users for each user category you are targeting
• Be sure to interview end-users, not just managers who think they know how the
process/system is used
• Allow time in the schedule to debrief and finish documentation after each
interview
Interviewing: Interview Questions
• Allow the questions to flow naturally so they can be put into conversation
rather than a survey
Requirement Workshops
Requirement Workshop: What is it?
3G
3. To ask a correct question, you must keep the situation, the context
and the intent in mind.