0% found this document useful (0 votes)
33 views35 pages

Business Analysis for RPA Workbook

This document appears to be a student workbook for a course on business analysis for robotic process automation. It contains 4 modules that cover topics such as domain analysis, requirements elicitation, stakeholder analysis, and facilitation techniques. The modules include key questions, glossaries, and activities to help students apply business analysis practices and understand how they enable intelligent automation solutions.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views35 pages

Business Analysis for RPA Workbook

This document appears to be a student workbook for a course on business analysis for robotic process automation. It contains 4 modules that cover topics such as domain analysis, requirements elicitation, stakeholder analysis, and facilitation techniques. The modules include key questions, glossaries, and activities to help students apply business analysis practices and understand how they enable intelligent automation solutions.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Business

Analysis for
Robotic Process
Automation
Student
Workbook

© 2005–2021 UiPath Academy. All rights reserved.


Table of Contents
Table of Contents.........................................................................................................................2
Module 1: Domain Analysis..........................................................................................................4
1.1 Key Questions.....................................................................................................................4
1.2 Glossary..............................................................................................................................5
1.3 Activity 1: Journal................................................................................................................6
1.4 Activity 2: Requirement Types............................................................................................7
1.5 Activity 3: Requirement vs. Design.....................................................................................8
Module 2: Domain Analysis..........................................................................................................9
2.1 Key Questions.....................................................................................................................9
2.2 Glossary............................................................................................................................10
2.3 Activity 1: Analysis Models................................................................................................11
2.4 Activity 2: Planning for Elicitation & Collaboration............................................................12
2.5 Activity 3: Facilitation Guide..............................................................................................13
2.6 Activity 4: Stakeholder Analysis........................................................................................14
2.7 Activity 5: Business Analysis Approach, Tasks, and Risks..............................................16
Module 3: Domain Analysis........................................................................................................18
3.1 Key Questions...................................................................................................................18
3.2 Glossary............................................................................................................................19
3.3 Activity 1: Goals and Objectives Brainstorming................................................................20
3.4 Activity 2: Problem/Opportunity Statements.....................................................................21
3.5 Activity 3: The Importance of Standards: Notation...........................................................22
3.6 Activity 4: The Importance of Standards: Taxonomy........................................................24
3.7 Activity 5: Business Context Diagram: Co-Op Application Portal.....................................25
3.8 Activity 6: Evaluating Requirements Statements..............................................................26
3.9 Activity 7: Creating Requirements Statements.................................................................27
3.10 Activity 8: Adding Non-Functional Considerations/Qualifiers to Requirements
Statements..............................................................................................................................29
Module 4: Domain Analysis........................................................................................................30

© 2005–2021 UiPath Academy. All rights reserved.


4.1 Key Questions...................................................................................................................30
4.2 Glossary............................................................................................................................31
4.3 Activity 1: Evaluating the Use Case Basic Flow...............................................................33
4.4 Activity 2: Evaluating Business Rule Types......................................................................35

© 2005–2021 UiPath Academy. All rights reserved.


Module 1: Domain Analysis
1.1 Key Questions
 What is business analysis?
 What does a Business Analyst (BA) do?
 Where does business analysis occur in business, product, and/or system development
lifecycles?
 How do I apply business analysis practices, and how can they help me, my company, or
my clients?
 How does business analysis enable the design and development of intelligent automation
solutions?

Notes

© 2005–2021 UiPath Academy. All rights reserved.


1.2 Glossary
Throughout this module, define in your own words the terms listed in the table.

Term Definition

Changes

Needs

Solutions

Contexts

Stakeholders

Value

Business Analyst

Requirement

Design Definition

Notes

© 2005–2021 UiPath Academy. All rights reserved.


1.3 Activity 1: Journal
Answer the following questions:
1. My initial reaction to learning about the domain of business analysis is...
2. Based on the first class, I find the following aspects of business analysis interesting
becasue...
3. I am interested in learning more about...

Notes

© 2005–2021 UiPath Academy. All rights reserved.


1.4 Activity 2: Requirement Types
Using the requirements architecture, identify the most appropriate type of requirement for each
of the statements listed in the table.

Requirements Type

1. Account Manager must view six-months sales data


across multiple organizational units in a single view.

2. The goal is to reduce the amount of time needed to


pick and pack customer orders.

3. Display information in English and French.

4. Medical Office Administrator must be able to record


and access a medical patient’s history.

5. New users must receive hands-on instructions when


using the system.

Notes

© 2005–2021 UiPath Academy. All rights reserved.


1.5 Activity 3: Requirement vs. Design
Using the requirements architecture, identify the most appropriate type of requirement for each
of the statements in the table.

Requirements Design

1. Account Manager must view six-months sales data


across multiple organizational units in a single view.

2. The goal is to reduce the amount of time needed to


pick and pack customer orders.

3. Display information in English and French.

4. Medical Office Administrator must be able to record


and access a medical patient’s history.

Notes

© 2005–2021 UiPath Academy. All rights reserved.


Module 2: Domain Analysis
2.1 Key Questions
 How do we begin the process for eliciting requirements?
 How do we ensure they are correct?
 When do we use appropriate techniques, or produce models, that ensure our stakeholders
can use the outcome of our work?

Notes

© 2005–2021 UiPath Academy. All rights reserved.


2.2 Glossary
Throughout this module, define in your own words the terms listed in the table.

Term Definition

Analysis

Techniques

Models

Framework

Elicitation

Collaboration

Workshops

Approach

Stakeholder
Analysis

Notes

© 2005–2021 UiPath Academy. All rights reserved.


2.3 Activity 1: Analysis Models
For your academic institution, develop one of the following models: Domain Model, Process
Model, Interface Model. Use your Student Workbook to complete the table.

Model Type Model Example

Domain Model

Process Model

Interface Model

Notes

© 2005–2021 UiPath Academy. All rights reserved.


2.4 Activity 2: Planning for Elicitation & Collaboration
Based on the models produced for the academic institution in Unit 1, plan for and conduct an
elicitation session to verify and validate the model produced.

Step Specific Tasks/Techniques Notes/Results

1. Prepare

2. Conduct

3. Analyze/Synthesize

4. Verify & Validate

5. Communicate & Manage

Notes

© 2005–2021 UiPath Academy. All rights reserved.


2.5 Activity 3: Facilitation Guide
Using Activity 2 as an example, how could you better prepare to conduct a workshop session?
Create a plan to detail key considerations for each phase of your facilitated workshop/session.

Workshop Purpose

Workshop Objectives

Workshop Agenda

Time Focus/Questions Results/Findings

Next Steps/To-Do

Notes

© 2005–2021 UiPath Academy. All rights reserved.


2.6 Activity 4: Stakeholder Analysis
How could you identify and classify different types of stakeholders?
Determine the techniques you could apply to source stakeholder information when starting a
new initiative.

Types of Stakeholders

Stakeholder Purpose Types and Examples

Stakeholder Analysis Sources and Techniques

Sources and Techniques Notes

1.

2.

3.

4.

© 2005–2021 UiPath Academy. All rights reserved.


Notes

© 2005–2021 UiPath Academy. All rights reserved.


2.7 Activity 5: Business Analysis Approach, Tasks, and
Risks
How can you identify and classify different types of stakeholders? Determine the techniques
you could apply to source stakeholder information when starting a new initiative.

Approach Section Approach Details & Tasks Notes

Requirements Approach

Elicitation Approach

Review Approach

Approval Approach

Identify and define key business analysis risks that you have to consider prior to starting any
business analysis initiative. For each type of risk, identify approaches that could be used to
mitigate these risks.

Risk Types Risk Type Definitions Risk Type Mitigation


Approach

Requirements
Assumptions

Requirements
Constraints

Requirements
Dependencies

© 2005–2021 UiPath Academy. All rights reserved.


Notes

© 2005–2021 UiPath Academy. All rights reserved.


Module 3: Domain Analysis
3.1 Key Questions
 What is expected of me as a BA while working on a project?
 How do I begin analysis? What should I do when I am first assigned to a new initiative?
 How do I know what this initiative needs to address? How do I know I’m doing the right
thing?
 What is the impact of this initiative? How complex is the process?
 What is scope? What is the difference between project scope and requirements scope?

Notes

© 2005–2021 UiPath Academy. All rights reserved.


3.2 Glossary
Throughout this module, define in your own words the terms listed in the table.

Term Definition

Discovery Analysis

Vision

SIPOC Model

Business
Requirements

Process

Process Analysis

Requirements
Scope

Stakeholder
Requirements

Business Context
Diagram (BCD)

Notes

© 2005–2021 UiPath Academy. All rights reserved.


3.3 Activity 1: Goals and Objectives Brainstorming
Based on your course/program of study, create goals that the program may seek to achieve.
For each goal identified, consider objectives that will enable the quantification and specificity of
that goal.

Goals Objectives

1.

2.

3.

4.

Notes

© 2005–2021 UiPath Academy. All rights reserved.


3.4 Activity 2: Problem/Opportunity Statements
Review the problem/opportunity statements provided. Are either of these statements
acceptable starting point for an initiative? What issues do they pose? What may it be missing?

Problem/Opportunity Issues or missing Enhanced Statements


elements?
Statement

1. Student accounts and


academic performance
information cannot be accessed
on smart phones or tablets.

2. We need to comply with Bill C-


28, Canada’s Anti-Spam
Legislation (CASL).

Notes

© 2005–2021 UiPath Academy. All rights reserved.


3.5 Activity 3: The Importance of Standards: Notation
Take time to review the map presented and consider the given questions.

Questions Notes

1. What is happening in this process?

2. What problems to do you identify with the


notation?

3. As a BA, what would you have to do if


using this as an input for your analysis?

© 2005–2021 UiPath Academy. All rights reserved.


Notes

© 2005–2021 UiPath Academy. All rights reserved.


3.6 Activity 4: The Importance of Standards: Taxonomy
Take time to review the map presented and consider the given questions.

Questions Notes

1. What level is this map?

2. What problems do you identify with the


level?

3. As a BA, what would you have to do if


using this as an input for your analysis?

Notes

© 2005–2021 UiPath Academy. All rights reserved.


3.7 Activity 5: Business Context Diagram: Co-Op
Application Portal
Using the description provided, create a BCD (DFD L0). To do this, identify the elements
(center/scope, external entities, and data flows) to inlcude in the context diagram from the
summary.

Summary BCD

George Brown College would like to


create a Co-Op Application Management
Portal. This portal will enable employers
to submit co-op job postings, allow co-op
office staff to review and decision
(approve, decline) postings, and provide
students with the opportunity to search,
view, and apply to approved co-op job
postings. Student applications will be
submitted via the portal and sent directly
to employers. Application metrics will be
captured and send to co-op office staff
and college management in the form of a
report.

Notes

© 2005–2021 UiPath Academy. All rights reserved.


3.8 Activity 6: Evaluating Requirements Statements
Review the High-level/Requirements Scope statements. Are they acceptable? What issues do
they pose? What may they be missing?

Requirements Issues or missing Enhanced Statements


Statement elements?

1. The system must


generate weekly MIS
reports.

2. Vendors must be able to


access records, reports,
etc.

3. Interfaces between
systems will provide
information to ERP
application.

4. An audit log shall be


available showing who
did what and when.

Notes

© 2005–2021 UiPath Academy. All rights reserved.


3.9 Activity 7: Creating Requirements Statements
Review the BCD for the proposed Co-Op Application Management Portal. Based on the
human entities identified in the BCD, use the information flows to help in creating
High-level/Requirements Scope statements. One sample statement has been created in the
diagram.

HLR # Definition

HLR001

HLR002

HLR003

© 2005–2021 UiPath Academy. All rights reserved.


HLR004

HLR005

HLR006

HLR007

HLR008

HLR009

HLR010

Notes

© 2005–2021 UiPath Academy. All rights reserved.


3.10 Activity 8: Adding Non-Functional
Considerations/Qualifiers to Requirements Statements
Review the above Co-Op Application Portal Requirements Scope statements. For each,
identify and/or consider potential non-functional qualifiers to enhance these requirements.

HLR # Non-Functional Considerations/Qualifiers

HLR001

HLR002

HLR003

HLR004

HLR005

HLR006

HLR007

HLR008

HLR009

HLR010

Notes

© 2005–2021 UiPath Academy. All rights reserved.


Module 4: Domain Analysis
4.1 Key Questions
 How do we elaborate on the scope that has now been defined?

 How do we ensure that our requirements will be addressed in future state?

 What details are necessary for designers and developers to do their work?

 How detailed do specifications need to be?

Notes

© 2005–2021 UiPath Academy. All rights reserved.


4.2 Glossary
Throughout this module, define in your own words the terms listed in the table.

Term Definition

Solution
Requirement

Functional
Requirements

Non-Functional
Requirements

Use Case Diagram

Use Case
Specification

Business Rule

Data Requirements

Interface Analysis

Report
Requirements

Notes

© 2005–2021 UiPath Academy. All rights reserved.


4.3 Activity 1: Evaluating the Use Case Basic Flow

Use Case
George Brown College would like to create a Co-Op Application Management Portal. This
portal will enable employers to submit co-op job postings, allow co-op office staff to review and
approve eligible postings, and provide students with the opportunity to search, view, and apply
to approved co-op job postings. Student applications will be submitted via the portal and sent
directly to employers. Application metrics will be captured and sent to co-op office staff and
college management in the form of a report.
Review this use case describing the how an employer will submit a job posting to the proposed
Co-Op Application Management Portal. Identify what information and or steps might be
missing. Identify what best practices have not been applied.

Use Case Flow

Step # Step Description Summary of Findings

1 The system presents employer with job


posting landing page.

2 User adds job posting details.

3 System requests job posting attachment if


user details have been successfully added.

4 User opens attachment search.

5 -7 User navigates to folder, selects job posting,


and attaches it.

8 System prompts user to save job posting.

9 Employer can save once satisfied.

© 2005–2021 UiPath Academy. All rights reserved.


Notes

© 2005–2021 UiPath Academy. All rights reserved.


4.4 Activity 2: Evaluating Business Rule Types

Scenario
George Brown College would like to create a Co-Op Application Management Portal. This
portal will enable employers to submit co-op job postings, allow co-op office staff to review and
approve eligible postings, and provide students with the opportunity to search, view, and apply
to approved co-op job postings. Student applications will be submitted via the portal and sent
directly to employers. Application metrics will be captured and sent to co-op office staff and
college management in the form of a report.
Each of the statements is a business rule. For each, determine which type and sub-type best
describes the rule defined.

Business Rule Statement Type Sub-Type

1. A co-op employer is defined as any business


who provide suitable co-op employment to a
student.

2. International students must have a valid co-op


work permit to apply for co-op jobs.

3. Co-op employers must ensure that co-op jobs


will provide with a minimum of 360 working
hours.

4. Employer co-op tax credit will be 50% of


students total compensation through the
duration of co-op.

5. A student must maintain a GPA of 3.0 to apply


for co-op jobs.

6. A student must submit both a resume and


cover letter when applying for a co-op job.

7. Students will be provided with 72 hours to


accept a co-op job offer.

© 2005–2021 UiPath Academy. All rights reserved.


Notes

© 2005–2021 UiPath Academy. All rights reserved.

You might also like