Professional Documents
Culture Documents
Method
SETLabs
1
De 201 / De Bridge (OOAD) - Framework
2-2
2
Objectives
• Go through the Purpose of Business modeling/analysis
• Learn the concept of business modeling and its technique.
• Learn techniques to derive requirements from business models.
2-3
3
Business Requirements – Where do they come
from?
• Most IT development projects are meant to automate business activities and
business transactions
• In the end, the IT solution developed would wholly or partially change the
existing business behavior of an organization
2-4
4
InFlux Business Requirements – Principles &
Lifecycle
Basic Principles
2-5
5
Step 1 : As-Is Business Behavior
2-6
6
Step 1 : As-Is Business Behavior
• For any IT solution development
– Helps understand the problem space
– Know what is the behaviour that you want to change
– Understand the scope of change
– Determine the extent of change
2-7
7
Step 2 : Business Analysis
2-8
8
Step 2 : Business Analysis
2-9
9
Step 3 : To-Be Business Behavior
2 - 10
10
Step 3 : To-Be Business Behavior
• For any IT solution development
– Defines the solution at the business process level
– Understand the scope of the solution
– Represent the net result of the solution
2 - 11
11
Method 1 : Business Modeling
Why Modeling?
• Helps capture the right level and right amount of information in the right way –
template for elicitation and representation
• Represents the problem space and the solution space using the same levels of
abstraction
2 - 12
12
Method 1 : Business Modeling
What aspects do we capture through Modeling?
Who? Where?
Organization Location
Located at
Model Model
Performed by Performed by
What? How?
Collaboration Realized by
Workflow
Model Model
2 - 13
13
Business Modeling : Organization Model
• Represents the business participants in terms of various organization units for
the business behavior in scope
• Represents the stakeholders of an IT solution and how they are mapped to the
organization – Potential business users, solution business owners, solution IT
owners
• Benefits
– Single snapshot of all stakeholders
– Helps Indicate what requirement will come from which stakeholder – based on the
organization area and level they map to
– Relationship between stakeholders is an input to determine access and security
levels of potential users
2 - 14
14
Business Modeling : Organization Model
• What information is captured and How is it depicted in an Organization Model
2 - 15
15
Business Modeling : Organization Model
Context :
Business Stakeholders of an order fulfillment process for a catalogue sale retail company
Organization
Department
Relationships
(Belongs To, Reports To)
Roles
2 - 16
16
Exercise 1 :
• Objective : Create an Organization Model based on the following situation
2 - 17
17
Exercise 1 : Solution!
2 - 18
18
Exercise 1 :
• Objective : Create an Organization Model based on the following situation
2 - 19
19
Exercise 1 : Solution!
Information implied in
the write-up
2 - 20
20
Organization Model - Extensions
• Policies : Different levels of organization
• Privacy and Access Levels : Different levels of organization
• Staff Requirements : Different levels of organization
2 - 21
21
Creating Models – Key Lessons
• Iterative Creation : It is hardly possible to find all the information required to
populate a model in a single discussion. Multiple pieces of information
collected at different times through different stakeholders can come together to
give the big picture
• Graphical and Textual: Models may not be entirely graphical. You may
represent the key elements and their relationships in a graphical manner but
qualify this information using textual documentation
• Topic for Elicitation Discussion : Specific Models can become really good
topics for elicitation discussion with stakeholders. It ensures that the
discussions are focused on getting information to complete as much as
possible a few logically connected models.
• This does not mean that one should not capture information provided outside
the scope of a model – in fact this extraneous information can help qualify the
modeled information or extend the scope of modeling!
2 - 22
22
Business Modeling : Location Model
• Represents the geographical locations where an enterprise or its part operates,
and the departments that operate out of these locations. This model is created
in order to map department level entities to the physical location they are
operating at.
• Benefits
– a single snapshot view of how the stakeholder groups in an enterprise are disbursed
across various physical locations
– helps in eliciting location-specific needs of the organization such as localization and
customization
– helps to derive the deployment view of an IT solution based on the usage of the
solution functionalities in various physical locations by different departmental
stakeholders
2 - 23
23
Business Modeling : Location Model
• What information is captured and How is it depicted in a Location Model
2 - 24
24
Business Modeling : Location Model
Context :
Business Locations of the stakeholder groups of an order fulfillment process for a catalogue sale retail
company
Region
Locations
Offices
Departments
2 - 25
25
Exercise 7 :
• Objective : Create a Location Model based on the situation in exercise 6 and the
following additional information
2 - 26
26
Exercise 7 : Solution
2 - 27
27
Business Modeling : Collaboration Model
• Profiles a business area or function and the transactions performed therein by
showing interactions among business participants (role, department,
organization and systems) within a given scope – Represents interactions
between the internal and external participants for the business area under
consideration
• Benefits
– Helps scope out the problem and the solution space
– Helps in determining the business process catalog for detailing out
business behaviour
– Starting point for depicting information model and EAI scenario
2 - 28
28
Business Modeling : Collaboration Model
• What information is captured and How is it depicted in a Collaboration Model
2 - 29
29
Business Modeling : Collaboration Model
• What information is captured and How is it depicted in a Collaboration Model
Definitions
2 - 30
30
Business Modeling : Collaboration Model
Context :
Business collaboration of participants of an order fulfillment process for a catalogue sale retail company
Interaction
Work Product
Business Participants
Segment
Example of a Collaboration Model
2 - 31
31
Exercise 8 :
• Objective : Create a Collaboration Model based on the situation below
• Situation : The cash manager liaisons with a customer to get a product service
agreement signed. The product service agreement is stored in a hard copy by the
Business Service Center group in the back-end. The cash manager also collects
activation information from the customer in a client setup form that covers the basic
demographic details about the client. This information is collected in a paper form and
faxed or mailed to a booking coordinator. Apart from this the cash manager also fills up
other customer details in the communication profile form and the billing input form that
are also sent over to the booking coordinator. The booking coordinator is a user of the
call center system and internally interacts with the enrollment officer and the cash
manager. This role is responsible for validating the customer activation information with
the customer, sending these details to the enrollment office and entering customer
demographic information and product information in the call center application.
Enrollment officer also updates the call center application with status to denote
completion of the process. Before that, this role will create acronym for the customer and
update it in call center app. It will also update client details and product details in the
product system to enroll the client
2 - 32
32
Exercise 8 : Solution
2 - 33
33
Method 2 : Business Process Catalog Identification
Business Process Catalog represents a list of processes where each process
represents a series of activities with a clear starting and ending points for fulfillment
of a business transaction
2a Business Interactions
2 - 34
34
Method 2 : Business Process Catalog Identification
Business Process Catalog represents a list of processes where each process
represents a series of activities with a clear starting and ending points for fulfillment
of a business transaction
2a Business Interactions
2 - 35
35
Method 2a : Business Process Catalog Identification
2a : How to identify a catalog of business processes from business interactions
Input Required : Business interactions are mapped out in a high level collaboration
model
• Algorithm
– Step 1 : Select among the list of participants, those participants who trigger an
interaction for fulfillment of a well defined need leading to a meaningful end result for
the participant
– Step 2 : Starting from the trigger interaction, identify all interactions through various
participants that are directly required to fulfill the need.
– Step 3 : List down the process for this need fulfillment as a process in the catalog
– Step 4 : Eliminate the interactions that have been identified under this process from
the collaboration model
– Step 5 : Repeat step 1 till all interactions in the collaboration model are exhausted.
Interactions that depict exception scenarios may be ignored.
2 - 36
36
Method 2a : Example
Input : A high level collaboration model for Travel business area
Step 1 : Select among the list of participants, those participants who trigger an interaction
for fulfillment of a well defined need leading to a meaningful end result for the participant
Triggers an
interaction for
obtaining tickets
2 - 37
37
Method 2a : Example
Input : A high level collaboration model for Travel business area
Step 2 : Starting from the trigger interaction, identify all interactions through various
participants that are directly required to fulfill the need
Triggers an
interaction for
obtaining tickets
2 - 38
38
Method 2a : Example
Input : A high level collaboration model for Travel business area
Step 3 : List down the process for this need fulfillment as a process in the catalog
Triggers an
interaction for
obtaining tickets
PROCESS CATALOG
1. Travel Request to Ticket Issuance
2 - 39
39
Method 2a : Example
Input : A high level collaboration model for Travel business area
Step 4 : Eliminate the interactions that have been identified under this process from the
collaboration model
2 - 40
40
Method 2a : Example
Input : A high level collaboration model for Travel business area
Step 5 : Repeat step 1 till all interactions in the collaboration model are exhausted.
Interactions that depict exception scenarios may be ignored
Triggers an
interaction for
obtaining
payment
2 - 41
41
Method 2a : Example
Input : A high level collaboration model for Travel business area
Step 5 : Repeat step 1 till all interactions in the collaboration model are exhausted.
Interactions that depict exception scenarios may be ignored
PROCESS CATALOG
1. Travel Request to Ticket Issuance
2. Travel Invoice to Payment
Triggers an
interaction for
obtaining
payment
2 - 42
42
Method 2 : Business Process Catalog Identification
Business Process Catalog represents a list of processes where each process
represents a series of activities with a clear starting and ending points for fulfillment
of a business transaction
2a Business Interactions
2 - 43
43
Method 2b : Business Process Catalog Identification
2b : How to identify a catalog of business processes from process architecture
decomposition
Input Required : Identification of the Line of Business for process decomposition
• Algorithm
2 - 44
44
Method 2b : Example
2b : How to identify a catalog of business processes from process architecture
decomposition
Input Required : Identification of the Line of Business for process decomposition
Infosys
Finacle IBUs
2 - 45
45
Method 2b : Example
2b : How to identify a catalog of business processes from process architecture
decomposition
Input Required : Identification of the Line of Business for process decomposition
Infosys
Finacle IBUs
2 - 46
46
Method 2b : Example
2b : How to identify a catalog of business processes from process architecture
decomposition
Input Required : Identification of the Line of Business for process decomposition
Sales
Internal Stakeholders
1. Sales Head
2. Bus Dev Mgr
2 - 47
47
Method 2b : Example
2b : How to identify a catalog of business processes from process architecture
decomposition
Input Required : Identification of the Line of Business for process decomposition
Field
Survey
Sales Results
Prospect
Internal Stakeholders
Conversion
1. Sales Head
Ratio
2. Bus Dev Mgr
2 - 48
48
Method 2b : Example
2b : How to identify a catalog of business processes from process architecture
decomposition
Input Required : Identification of the Line of Business for process decomposition
Field
Survey
Sales Results
Prospect
Internal Stakeholders
Conversion
1. Sales Head
Ratio
2. Bus Dev Mgr
PROCESS CATALOG
1. Field Survey Request to Report Field Survey
2. Convert Prospect to Customer
2 - 49
49
Business Modeling : Workflow Model
• Represents the business behavior by capturing the business activities
flow for each process (end-to-end lifecycle of a transaction) showing
the business participants, their activities, the sequence of these
activities and the interactions between various participants.
• Benefits
– helps maintain a common depth of understanding of the problem
space and the solution space between the business and IT
stakeholders
– Support of IT systems at a process level is clearly visible as part of
the workflow depiction
– Various stakeholders (eg : Business process owners, business
users) can see information pertinent to their role in a single view
2 - 50
50
Business Modeling : Workflow Model
• What information is captured and How is it depicted in a Workflow Model
2 - 51
51
Business Modeling : Workflow Model
• What information is captured and How is it depicted in a Workflow Model
• Workflow Participant: The participants in the workflows can be roles (worker, worker
manager), organizations, departments (finance department, inventory), or systems
(service center system, order entry system).
– Systems execute automated business activities (for example, "Generate Paychecks").
• Activity is a task or a unit of work performed by a participant.
• Transition is a link between two activities. Three types of activities can be considered
from the automation perspective.
– Manual activities are activities performed by human effort, unaided by systems, for example,
"Ship Goods."
– Interactive activities are activities done by humans that involve usage of systems, for example,
"Enter Order." Such activities should be shown in the swim-lane of the human using the system.
– Automated activities are activities done by systems with no manual involvement, for example,
"Retrieve Orders." Such activities should be shown in the swim-lane of the system.
• Swim-lane - A region that encloses a set of activities done by a participant in a workflow
Definitions
2 - 52
52
Business Modeling : Workflow Model
Context :
Business workflow of participants of an order fulfillment process for a catalogue sale retail company
2 - 53
Activity guidelines:
•Activity should be able to repeat itself immediately after its completion. Eg. Logon
can not be an activity.
•Activity should:
•Transfer information
•Extract information
•Change data
•Decision point is not an activity, it is an outcome. It has to be preceded by an
activity.
•Is “check customer type” an activity? Strictly, it is not, since before checking next
customer status, we should transmit. This is an exception.
53
Business Modeling : Workflow Model
• Very Important Considerations
2 - 54
54
Exercise 9 :
• Objective : Create a Workflow Model based on the situation in exercise 8 and
the additional information below
2 - 55
55
Exercise 9 : Solution How do I name it?
2 - 56
56
Exercise 10 on Business Modeling
• Objective : Review the Workflow Model given for correctness of modeling standards
2 - 57
57
Exercise 11 on Business Modeling
• Objective : Create a collaboration model from the given workflow model
2 - 58
58
Exercise 11 on Business Modeling
• Solution:
2 - 59
59
Review – Business Modeling
• What is the need to create business models?
• What are the models used to capture business behaviour?
• Which model should be drawn first? Are all models required in all
situations?
• Is there a limit to how may models of each type can be drawn?
• What is the significance of business process catalogue?
• Give an example of a business transaction trigger that can be
described in a workflow
• Give an example of a business transaction that is not a workflow
2 - 60
60
Method 3 : Business Analysis
• Systematic analysis of the problem space to build recommendations for the
solution space
Input for
2 - 61
61
Business Analysis : Issue Elicitation & Analysis
• Benefits
2 - 62
62
Business Analysis : Issue Identification/Elicitation
• How to Do It?
2 - 63
63
Business Analysis : Issue Analysis
• ‘Issues’ are analyzed in the following Root Cause and Impact (RCI) Model
¾ What is the distribution of total issue impact across root causes – determines the high
priority root causes to tackle
¾ What is the distribution of total issue impact across business areas – determines the high
priority problem areas to tackle
2 - 64
64
Exercise 10 : Issue Identification using Static process
analysis
65
Exercise 10 : Solution
66
Process Modeling : Recommendations Formulation
• This is the first step into the solution space
• Ideas (What) can be represented in this stage without going into the exact specifics
(How)
• A high level prioritization of ideas can be done based on criticality of issues resolved
2 - 67
67
Process Modeling : Recommendations Formulation
2 - 68
68
Exercise 11 : Process Improvement Pattern Recognition
Solution
2 - 69
69
Exercise 11: Possible To-Be Model on application of recommendations
2 - 70
70
Review – Business Analysis
• Why do we analyze issues?
• What are patterns? What is their use?
• How can recommendations be formulated?
• How can recommendations be prioritized?
• What is done based on recommendations?
2 - 71
71
Review – What have we done so far?
Activities (What) Methods (How to carry out the Activities) Outputs (What you create in the Activities)
2 - 72
72
Review – InFlux BPE Methodology
• Does it bring enough value in requirements engineering?
• Does the structure and formalism make life easier?
• Does it bring a common language between business and IT
2 - 73
73
Summary
• Business process is the key unit of analysis to identify and depict software
requirements
• Business modeling technique is used to depict business behaviour in the
problem space (As-Is) and in the solution space (To-Be)
• Movement of As-Is to To-Be in business behaviour is facilitated by a formal
technique of process analysis
• Movement from business behaviour to system behaviour is facilitated by
Enactment Definition
• Use-case are the standard for representing system behaviour
2 - 74
74