Business Modeling with UML

1
Business Modeling with UML Rational Rose

• Robert C. Chi
• cnchi_at_iis.sinica.edu.tw
• Academia Sinica

2
Agenda

• What is Business Modeling
• Skills of Gathering Information
• Notation of Business Modeling
• Business Use Case Diagrams
• Activity Diagrams
• Conceptual Models
• Summary

3
What is Business Modeling
Understand the Current Situation
4
Skills of Gathering Information

• Gathering What?

E.W.P.D.S.
5
Skills of Gathering Information

• Who is Qualified?

6
Skills of Gathering Information

• How to Gather?
• Interviews
• Survey
• Document Review
• Observation
• Brainstorming

O.B.S.I.D.
7
Skills of Gathering Information

• Interview
• Before
• Identify the Objectives
• Schedule the Interview earlier
• Identify the position responsibilities of
  interviewees
• During
• Explain the objectives of interview
• Record / Take notes during the interview
• Dont take more than 1 hour
• After
• Document all the relevant points that were
  gathered
• Send the documentation to interviewee
• Schedule another interview if it is needed.

8
Skills of Gathering Information

• Survey
• Before
• Prepare the questionnaire
• Identify respondents
• During
• Explain the objectives of this survey
• Distribute the questionnaire
• After
• Analyze respondents answers

9
Skills of Gathering Information

• Document Review
• Before
• Collect the following documents Forms,
  Guidelines, Standard of Procedures (SOP), Rules,
  Policiesetc.
• During
• Analyze the documents and gather the facts
• After
• Document the result of review

10
Skills of Gathering Information

• Observation
• Before
• Identify the user areas and processes to be
  observed
• Obtain the proper management approval to carry
  out the observation
• Obtain the names and titles of the key people
  that involved in the observation
• Explain the purpose of the study
• During
• Familiarize yourself with the workplace being
  observed
• Not the current organizational groupings
• Observe the current manual and facilities in use.
• Get the frequencies of each job duty.
• Dont comment on customers mode of operation
  currently
• Observe the normal business operations
  exceptions
• Thanks people after the observations are
  completed
• After
• Document the results
• Consolidate the results
• Review the consolidated results with individual
  observed their managers

11
Skills of Gathering Information

• Brain Storming
• Before
• Identify the objectives of brain storming
  meetings
• Schedule the meeting and invite the relative
  persons
• Prepare all the documentations for discussion
• During
• Explain the objectives of this meeting
• Show explain all the documents we have
• Hold the meeting and dont lose the focus
• After
• Document the results
• Consolidate the results
• Analyze the consolidate results

12
Notation of Business Modeling

• Types of Business Modeling Notation
• Traditional Flow Chart
• Total Quality Management (TQM) Diagram
• Process Workflow Diagram
• Data Flow Diagram (DFD)
• Unify Modeling Language (UML)

13
Notation of Business Modeling

• UML in Business Modeling
• Business Use Cases Diagram
• Activity Diagram

14
Notation of Business Modeling

• Business Use Case Diagram
• Example

15
Notation of Business Modeling

• Activity Diagram
• Example

16
Business Use Case Diagram

• What to be modeled?
• People (Customer, Staff)
• Group of People (Organization)
• Things (Objects, Forms, Facilities)
• Process
• How to model
• People Customer ? Business Actor
• People Staff ? Business Worker
• Group ? Organization Unit
• Things ? Business Entity
• Process ? Business Use Case

17
Business Use Case Diagram

• Icons Introduction

18
Business Use Case Diagram

• Purpose
• Present the Big Picture of workflow
• Divide the workflow as smaller units(Divide
  Conquer Technique)

19
Business Use Case Diagram

• Case Study
• Mr. Delay Software Company
• Core Business
• Accept the requests of customized software
  projects from customers
• Problems
• Lack of better faster way to accept the
  requests from customers, dispatch tasks, and
  monitor the status
• Expectations
• A project managing system, which is a web-based
  system that can accept the request from Internet,
  manage the tasks, and check status any time.

20
Business Use Case Diagram

• Interview with the Stakeholders
• Customer will call Project Manager to request a
  new project
• Project Manager will create the project, and the
  tasks list of the project.
• Then project manager will schedule the tasks and
  assign proper workers to finish the tasks of
  project
• The workers should report the status to project
  manager.
• The customer, project manager and the workers can
  check tasks status any time.

21
Business Use Case Diagram

• Results

22
Business Use Case Diagram

• Best Practice
• Use Rational Rose to do the Business Use Case
  Diagram of Mr. Delay Software Company

23
Activity Diagram

• Purpose
• To detail the flow of one business use case
• Icons Introduction

24
Activity Diagram

• What is Activity Diagram, Actually?

25
Activity Diagram

• Best Practice
• Use Rational Rose to describe the flow of the
  business use case Request Project.

26
Conceptual Models

• What is Conceptual Models
• The model that illustrates meaningful concepts in
  a problem domain.
• Provide a model to understand the problem domain
  quickly and easily

27
Conceptual Models

• Example

28
Conceptual Models

• Purpose
• Provide a quick understand of the objects in the
  system
• Note
• Conceptual Model is a set of static structure
  diagrams in which no operations are defined
• Conceptual Model is not formal constructive
  models
• Conceptual Models can be done by Flow Analyst or
  System Analyst
• Conceptual Model is not always required in
  developing cycle, it only needs when the concepts
  in the system are complex

29
Conceptual Models

• Best Practices
• Use Rational Rose to construct the conceptual
  models of Mr. Delay Software Company

30
Summary

• The way to gather the workflow
• Interview
• Survey
• Document Review
• Observation
• Brain Storming
• Business Use Case Diagrams
• The diagrams to divide the workflow as smaller
  units for better analysis
• Activity Diagrams
• The diagrams to detail the workflow of one use
  case
• Conceptual Models
• The models providing quick understand of system
  vocabularies