business modeling with uml rational rose
Download
Skip this Video
Download Presentation
Business Modeling with UML & Rational Rose

Loading in 2 Seconds...

play fullscreen
1 / 30

Business Modeling - PowerPoint PPT Presentation


  • 237 Views
  • Uploaded on

Business Modeling with UML & Rational Rose Robert C. Chi [email protected] Academia Sinica Agenda What is Business Modeling Skills of Gathering Information Notation of Business Modeling Business Use Case Diagrams Activity Diagrams Conceptual Models Summary

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Business Modeling' - adamdaniel


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
agenda
Agenda
  • What is Business Modeling
  • Skills of Gathering Information
  • Notation of Business Modeling
  • Business Use Case Diagrams
  • Activity Diagrams
  • Conceptual Models
  • Summary
what is business modeling
What is Business Modeling

Understand the Current Situation

skills of gathering information

Forms &

Documents

Legacy

System

Problem to

be Solved

Current

Workflow

Customer’s

Expectation

Skills of Gathering Information
  • Gathering What?

E.W.P.D.S.

skills of gathering information5

C.A.K.E.

Has Domain

Knowledge

Easy to

Communicate

Careful

Active

Skills of Gathering Information
  • Who is Qualified?
skills of gathering information6
Skills of Gathering Information
  • How to Gather?
    • Interviews
    • Survey
    • Document Review
    • Observation
    • Brainstorming

O.B.S.I.D.

skills of gathering information7
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
      • Don’t 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.
skills of gathering information8
Skills of Gathering Information
  • Survey
    • Before
      • Prepare the questionnaire
      • Identify respondents
    • During
      • Explain the objectives of this survey
      • Distribute the questionnaire
    • After
      • Analyze respondent’s answers
skills of gathering information9
Skills of Gathering Information
  • Document Review
    • Before
      • Collect the following documents: Forms, Guidelines, Standard of Procedures (SOP), Rules, Policies…etc.
    • During
      • Analyze the documents and gather the facts
    • After
      • Document the result of review
skills of gathering information10
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.
      • Don’t comment on customer’s 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
skills of gathering information11
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 don’t lose the focus
    • After
      • Document the results
      • Consolidate the results
      • Analyze the consolidate results
notation of business modeling
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)
notation of business modeling13
Notation of Business Modeling
  • UML in Business Modeling
    • Business Use Cases Diagram
    • Activity Diagram
notation of business modeling14
Notation of Business Modeling
  • Business Use Case Diagram
    • Example:
notation of business modeling15
Notation of Business Modeling
  • Activity Diagram
    • Example:
business use case diagram
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
business use case diagram17

Business

Actor

Business

Worker

Organization

Unit

Business

Entity

Business

Use Case

Business Use Case Diagram
  • Icons Introduction
business use case diagram18
Business Use Case Diagram
  • Purpose
    • Present the Big Picture of workflow
    • Divide the workflow as smaller units(Divide & Conquer Technique)
business use case diagram19
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.
business use case diagram20
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.
business use case diagram22
Business Use Case Diagram
  • Best Practice
    • Use Rational Rose™ to do the Business Use Case Diagram of “Mr. Delay Software Company”
activity diagram

State

Activity

Start State

Object

General State

End State

Branch

Activity Diagram
  • Purpose
    • To detail the flow of one business use case
  • Icons Introduction
activity diagram24
Activity Diagram
  • What is Activity Diagram, Actually?
activity diagram25
Activity Diagram
  • Best Practice
    • Use Rational Rose™ to describe the flow of the business use case “Request Project”.
conceptual models
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
conceptual models28
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
conceptual models29
Conceptual Models
  • Best Practices
    • Use Rational Rose™ to construct the conceptual models of “Mr. Delay Software Company”
summary
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
ad