Business System Analyst workbook created for requirement analysis. Business analyst can use the the workbook sequentially to progress through various requirements stages and get it to their agile team. Any suggestions for improvement or requires a scenario building mail me at the address listed in the last slide.

1. Business System Analyst
Workbook
From
Pawan Kharbanda
(ITIL, Google Analytics Certified, CSM)

2. Preface
• This power point is created as a placeholder to construct business
requirements document.
• If we follow the sequence of events and fill the placeholders, we should be
able to capture requirements and plug in all loop holes.
• Each slide has a placeholder to edit and write what’s intended.
• Table of content is drawn in a “Use Case Model”. If you click on any link, it
would take you to relevant section
• General persona’s in any agile model are stakeholders,
developers/architects, QA and the creative team.
• Assignment of use case to persona’s may be debatable. This is just a
thought and may change on scenario to scenario.
4/29/2016
Web Shared – Template
Pawan Kharbanda
2

3. Table of Content – System Analysis
4/29/2016
Web Shared – Template
Pawan Kharbanda
3
Define Problem
Statement
Critical Success
Factor
Define Personas
Use Case
Scenarios
Activity Diagram
Business Requirements
Stakeholder
Creative/Design
Delivery Team
QA Team
Technical System Requirement
Transaction Requirement
Sequence
Diagram
Class Diagram
Deployment
diagram

4. Problem Statement
• Define the problem statement
4/29/2016
Web Shared – Template
Pawan Kharbanda
4

5. Critical Success Factors
• Write CSF for the pain area described
4/29/2016
Web Shared – Template
Pawan Kharbanda
5

6. Define Personas/Actors
4/29/2016
Web Shared – Template
Pawan Kharbanda
6
Persona’s Name Role of Each Persona Image if any
User Define role and access system

7. Use Case Scenarios
Use Case No. Use Case Description Participating Personas
US-XXX-YYY-<date>
4/29/2016
Web Shared – Template
Pawan Kharbanda
7
Please move on to next Page for “USE CASE CONSTRUCT MODEL Depiction”

8. Use Case Construct Model
4/29/2016
Web Shared – Template
Pawan Kharbanda
8
• Activities
System Name : 1
• Activities
System Name : 2
• Activities
System Name : 3
Extends

9. Use Case – Activity Diagram
4/29/2016
Web Shared – Template
Pawan Kharbanda
9
Include the data flow based on persona interaction
Personas Activity Diagram
Persona 1
Persona 2
Activities at micro level will
need to be defined based
on each use case
Its not necessary to use
persona wise activity
diagram however to show
parallel processing I would
recommend a swim lane
activity diagram with
defined persona’s
Label each of the box and
describe the activity of the
box in separate sheet

10. Sequence Diagram
• Not a mandatory requirement but good to have in the kitty
• Describe the sequence of events in a vertical manner showing each
interactions with a form elements.
• Acts as a guide to static wireframe. Good to have post redlines for
user interactions.
4/29/2016
Web Shared – Template
Pawan Kharbanda
10

11. Class Diagram
• I have generally used when working with data architects showing all
attributes of data flow.
4/29/2016
Web Shared – Template
Pawan Kharbanda
11
<Class Name>
Attributes
Methods
<Class Name>
Attributes
Methods
Interaction

12. Deployment Diagram
• Shows how would you would deploy the application.
• Typical components would be like web server, app server, database,
firewalls, cloud services.
4/29/2016
Web Shared – Template
Pawan Kharbanda
12

13. Contact me
If you have any questions contact me at pkharbanda@gmail.com
My blog address: pkharbanda.blogspot.com
4/29/2016
Web Shared – Template
Pawan Kharbanda
13