Login / Sign Up
Presentations Process Analysis
Contributed on March 24, 2016
Loading 1.5K
3.4K

Business Analysis Process Model

Description

Business Analysis Process Model

Transcript

Business Analysis Process Model
© Lonsdale Systems 1
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Analyse
Needs
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
Evaluate
Options
• Solution
Options
• Feasibility
• Selected
Solution
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Selected
Solution
Analyse
Needs
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
Consider
Perspectives
• Stakeholders
• Business
Scope
• Application
Scope
Investigate
the Situation
• Initial Scope
Business Analysis Process Model
• Workflows
Model Business Processes
• Components
• Features
Model Software Applications
This is intended to be an “essential” process.
This means that removing anything from the model, except perhaps Model Business Processes,
will almost certainly cause problems and likely lead to failure.
The process consists of five stages and two techniques. Each of the stages and techniques have a
number of deliverables. For example, the Define Requirements stage delivers Formal
Requirements, Usage Scenarios and a Data Dictionary.
It is possible to establish a deliverable before the process stage it is delivered in. For example, it
is possible to identify some key Business Rules during Investigate the Situation or establish a
Data Dictionary during Analyse Needs.
The model was derived from the British Computer Society’s (BCS) book Business Analysis.
Business Analysis Process Model
© Lonsdale Systems 2
Investigate
the Situation
Consider
Perspectives
Analyse
Needs
Evaluate
Options
Define
Requirements
• Workflows
• Components
• Features
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
• Solution
Options
• Feasibility
• Selected
Solution
• Initial Scope • Stakeholders
• Business
Scope
• Application
Scope
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Model Software Applications
Model Business Processes
Business Analysis
Roles
Business Analyst
Business Analyst
System
s
A
nalyst
Business
A
nalyst
System
s
A
nalyst
Solution
A
rchitect
Separation of roles into Business Analyst, Systems Analyst and Solution Architect is more
common in larger organisations.
Business Analysis Process Model
© Lonsdale Systems 3
Investigate the
Situation
Rich Pictures
Mind Maps
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
Consider
Perspectives
• Stakeholders
• Business
Scope
• Application
Scope
Investigate
the Situation
• Initial Scope
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Selected
Solution
Analyse
Needs
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
• Workflows
Model Business Processes
• Components
• Features
Model Software Applications
Unstructured techniques work best during this stage. See
http://www.slideshare.net/lonsdalesystems/visual-communication-28395424.
It can be useful to establish a glossary of terms during this stage. See
http://blog.lonsdalesystems.com/post/creating-a-glossary-of-terms.
Business Analysis Process Model
© Lonsdale Systems 4
CompetitorsSuppliers
None
Employees
Hotel owner
Partners
Guests
Duty manager
Some
Subject Matter Knowledge
ControlOverScope
SomeHigh
HighNone
Back office clerk
Front desk clerk
Call centre
operator
Function
customers
Coffee shop
customers
Health
department
Fire department
CompetitorsSuppliers
None
Employees
Hotel owner
Partners
Guests
Duty manager
Some
Subject Matter Knowledge
ControlOverScope
SomeHigh
HighNone
Back office clerk
Front desk clerk
Call centre
operator
Function
customers
Coffee shop
customers
Health
department
Fire department
Stakeholder
Analysis
Consider
Perspectives
Functional
Analysis
Hotel
Management
System
Smart Card
Programmer
Duty ManagerBack Office Clerk
Front Desk Clerk
Call Centre Operator
Stay details
Accommodation Report
Bill
Billing Details
Check In Details
Check Out Details
Reservation
Context Diagram
Hotel
Management
System
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
Consider
Perspectives
• Stakeholders
• Business
Scope
• Application
Scope
Investigate
the Situation
• Initial Scope
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Selected
Solution
Analyse
Needs
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
• Workflows
Model Business Processes
• Components
• Features
Model Software Applications
It is essential to know who are the subject matter experts (SMEs) and who ultimately controls the
scope (this may be a project sponsor, product owner or steering committee).
Business scope is a consolidated view of the “work” of the stakeholders.
Application scope defines how the stakeholders will the application as a “tool” to support their
work.
Functional Analysis and Context Diagrams are typical techniques used during this stage.
However, actual techniques are not mandated here in contrast to the specific techniques
described in Modelling Processes and Modelling Applications.
Business Analysis Process Model
© Lonsdale Systems 5
Modelling Business Process and
Software Applications
Physical
(How?)
Logical
(What?)
Future (“To-Be”)Current (“As-Is”)
Understanding
Needs
Solution
Concepts
Modelling current physical business processes are great for understanding but can often lead to a
lot of wasted time. See http://blog.lonsdalesystems.com/post/business-analysis-and-process-
modelling for a more detailed discussion of how this slide relates to process modelling.
The Functional Analysis performed during Consider Perspectives can often substitute for the
current logical process model and bypass the current physical model.
Frequently BAs find that a current physical model of the application already exists. Current
logical models are much less common but very important in understanding how the application is
used as a “tool”.
The difference between the current and future logical models represent a needs “gap”.
More than one future physical process and application model may be created for different
solution options.
Business Analysis Process Model
© Lonsdale Systems 6
Model Business
Processes
KioskGuestHotelManagementSystem
Swipe credit
card
Read credit card
Retrieve guest
reservation
Display guest
details
Confirm guest
details
Allocate room
Display room
allocation
Display available
rooms
Dispense key
card
Retrieve
available rooms
Select room Remove key
card
[change room]
[accept allocated room]
Retrieve
reservation
Allocate
room
Record guest
details
Check
identity
document
Authorise
credit card
Accept cash
deposit
No acceptable
method of
payment
Record stay
details
[walk in]
[acceptable
credit card]
Process
Models
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
Consider
Perspectives
• Stakeholders
• Business
Scope
• Application
Scope
Investigate
the Situation
• Initial Scope
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Selected
Solution
Analyse
Needs
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
• Workflows
Model Business Processes
• Components
• Features
Model Software Applications
Process models model the “work” performed by the stakeholders.
Two models are produced:
•a model of the current or “as-is” business processes during Analyse Needs; and
•a model of the proposed or “to-be” business processes during Evaluate Options.
UML Activity diagrams are shown here but other notations such as BPMN or Achimate could be
used.
Business Analysis Process Model
© Lonsdale Systems 7
Model Software
Applications
Hotel Management System
Front Desk Back Office Housekeeping
Debtors Ledger General Ledger
Shift Management
Mobile App
Check out times
Minibar, Laundry
Staff details
Corporate sales
Corporate sales
Cash sales
Components
Mobile App
Enter Laundry Items
Record Laundry
Return
Housekeeper
Record Minibar
Usage
«actor,secondary»
Hotel Management
System
Record Make Up
Room
«actor»
Housekeeping
Features
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
Consider
Perspectives
• Stakeholders
• Business
Scope
• Application
Scope
Investigate
the Situation
• Initial Scope
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Selected
Solution
Analyse
Needs
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
• Workflows
Model Business Processes
• Components
• Features
Model Software Applications
These model the “tools” that support the stakeholder’s “work”.
Three models are produced:
•a model of the current software application(s) during Analyse Needs;
•a model of several alternative solutions proposed during Evaluate Options; and
•a model of the required software application during Define Requirements.
Components are the physical view and features are the logical view of an application.
Business Analysis Process Model
© Lonsdale Systems 8
Analyse Needs
• Strategic needs
– Improve a process to build on a strength or
exploit an opportunity
– Mitigate a risk to preserve a strength or avoid a
threat
– Remedy the underlying cause of a weakness
• Operational needs
– Managing information
– Enforcing business rules
• Identify “gaps”
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
Consider
Perspectives
• Stakeholders
• Business
Scope
• Application
Scope
Investigate
the Situation
• Initial Scope
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Selected
Solution
Analyse
Needs
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
• Workflows
Model Business Processes
• Components
• Features
Model Software Applications
Strategic Needs are identified as part of a SWOT analysis.
Operational Needs represents the routine automation of “work”.
It is common for the Information Requirements to be defined in a Data Dictionary.
Business Analysis Process Model
© Lonsdale Systems 9
Evaluate Options
• Identify solution options
• Investigate feasibility
– Technical
– Economic (business case)
– Schedule (estimate and plan)
– Compliance
– Operational
• Selected solution
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
Consider
Perspectives
• Stakeholders
• Business
Scope
• Application
Scope
Investigate
the Situation
• Initial Scope
Define
Requirements
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Selected
Solution
Analyse
Needs
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
• Workflows
Model Business Processes
• Components
• Features
Model Software Applications
The “TESCO” mnemonic is a great way to remember the different types of feasibility.
Feasibility can sometimes become a “show-stopper”. For example it is often mandatory to
comply with laws and regulations.
Schedule feasibility should be considered before economic feasibility as it identifies some of the
costs associated with the application.
It is common to select a solution option based on its economic feasibility (cost-benefit or
business case).
Business Analysis Process Model
© Lonsdale Systems 10
Define
Requirements
Define
Requirements
Analyse
Needs
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
Analyse
Needs
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
Consider
Perspectives
• Stakeholders
• Business
Scope
• Application
Scope
Investigate
the Situation
• Initial Scope
• Formal
Requirements
• Usage
Scenarios
• Data Dictionary
Evaluate
Options
• Solution
Options
• Feasibility
• Selected
Solution
• Strategic Needs
• Information
Requirements
• Business Rules
• Gap Analysis
• Workflows
Model Business Processes
• Components
• Features
Model Software Applications
• List of guests
– Surname 30 alphabetic
– First name 30 alphabetic
– Address 3 x 40 alphanumeric
• List of reservations
– Check in date DD/MM/YYYY
– Check out date DD/MM/YYYY
• Reservation details
– Room type [Standard|Deluxe|Suite]
– Number of guests 1 numeric
– Check in date DD/MM/YYYY
– Arrival flight number 10 alphanemeric
…
Data
Dictionary
Formal
Requirements
Scenarios
Formal requirements describe requirements from the perspective of the application.
They are most often described using mandatory statements such as “The application must…”.
Scenarios describe requirements from the perspective of the user of the application and
applications that use its services.
They are most often described using structured scenarios that define how the user (or application)
will interact with the application.
For example:
1. The user selects a transaction type
2. The application requests the transaction amount
3. …
Data dictionaries provide a structured way of defining interface and storage requirements.
Business Analysis Process Model
© Lonsdale Systems 11
Analyse
Needs
Investigate
Situation
Consider
Perspectives
Evaluate
Options
Define
Requirements
Backtracking
and Iteration
In practice, business analysis does not proceed smoothly through the five stages of the process
model.
Learning about a business area and the software applications that support it inevitably requires
BAs to “backtrack” to previous stages of the process as they learn more.
For example, some previously unknown stakeholders may be discovered during Analyse Needs.
This would require a BA to backtrack to the Consider Perspectives stage and revise the
Stakeholder Analysis (and possibly the Business Scope) to include the new stakeholder.
While some degree of backtracking is inevitable, excessive backtracking can lead to inefficient
repetition of work already performed (rework).
In situations where very little is known about the business area and its applications, a planned
iterative approach can provide a better approach.

Comments (1)

  1. Very interesting stuff to read. all contents related to business analyst are very clearly define. business process management is subject for my final semester. so this information really helps me for exam preparation
    you are doing great job, keep it up.i hope you will post more updates.

Leave a Comment

Get the BPI Web Feed

Using the HTML code below, you can display this Business Process Incubator page content with the current filter and sorting inside your web site for FREE.

Copy/Paste this code in your website html code:

<iframe src="https://www.businessprocessincubator.com/content/business-analysis-process-model/?feed=html" frameborder="0" scrolling="auto" width="100%" height="700">

Customizing your BPI Web Feed

You can click on the Get the BPI Web Feed link on any of our page to create the best possible feed for your site. Here are a few tips to customize your BPI Web Feed.

Customizing the Content Filter
On any page, you can add filter criteria using the MORE FILTERS interface:

Customizing the Content Filter

Customizing the Content Sorting
Clicking on the sorting options will also change the way your BPI Web Feed will be ordered on your site:

Get the BPI Web Feed

Some integration examples

BPMN.org

XPDL.org

×