LEVEL 2 TRAINING

Oracle Unified Method

OUM Use Case Overview
Business Analysis, Scoping, and
Requirements Gathering
Slide1

Copyright 2009, Oracle. All rights reserved.

Learning Objectives:
Business Processes and Use Cases and in OUM
By the end of this module you will be able to:
Describe the OUM artifacts used to analyze business
requirements, establish project scope, and define functionality
for a software system to support those requirements
Describe the difference between a business use case and a
system use case
Describe how OUM supports the use of context models, process
models, and use cases for capturing functional requirements
Describe the relationship between business process models and
use cases
Describe how system use cases lead directly to the system
design, test cases, and system documentation

Slide2

Copyright 2009, Oracle. All rights reserved.

Two Types of Use Cases (Business, System)

OUM includes support for
Business use cases
System use cases

Business use cases

Define business goals and functions
Describe behavior of the business for achieving those goals

System use cases

Define actors goals for using a system
Describe behavior of system to achieve the goal

In OUM use case and system use case are synonymous

use case = system use case

Slide3

Copyright 2009, Oracle. All rights reserved.

Develop System

Trace Requirements

From Business Context to System Design,

Test Cases, and System Documentation

Develop System

Trace Requirements

Business Context Diagram

Develop System

Trace Requirements

Business Use Case Model

Develop System

Trace Requirements

Business Process Models

Develop System

Trace Requirements

System Context Diagram

Develop System
Trace Requirements

Use Case Model

Develop System

Trace Requirements

System Design, Test Cases, System Documentation

Develop System

Trace Requirements

Business Context Diagram

Understand the Business Context

Its important to define the boundary of the business or business area
before defining its processes.
A Business Context Diagram is useful for showing business actors
who interact with a business area and their key information flows
Includes both human and non-human actors
Useful for understanding the as-is or the to-be business

Business Actor

Key Information

Business Area

Business Context Diagram

Business Context Diagram

Purchase Order
Approval

Ski-NOW

Procurement Data

Purchase Order
Order Confirmation

Paid Invoice
Fulfillment Statistics

Bid
Requisition
Vendor Info

Procurement
Request
Reject Notification

Procurement
Manager

Buyer

Slide13

Order Request

Copyright 2009, Oracle. All rights reserved.

Purchase Order
Order Confirmation
Invoice
Product Shipment

Customer

Supplier

Develop System

Trace Requirements

Business Use Case Model

Business Use Cases

A business use case describes:

The goals of the business
What the business does (business processes and functions)
Who does it (customers, employees, vendors)

A business use case also can be used as a starting

point for defining the purpose and scope of an
information system that will support the business.

Procurement
Manager

Slide15

Analyze
Procurement

Copyright 2009, Oracle. All rights reserved.

Business Use Case Diagram

A view of the functions of a business and of the actors
which require those functions
Ski-NOW
Buyer

Procurement
Manager

Supplier

Analyze
Procurement
Receiving
Agent

Settle
Payment
A/P Specialist

Slide16

Copyright 2009, Oracle. All rights reserved.

Most Important OUM Business Use Case Details

Slide17

Name
Brief Description
Actors
Goals
Basic Flow
Alternative Flows
Activity-Diagram
Pre-Conditions
Post-Conditions

Copyright 2009, Oracle. All rights reserved.

Develop System

Trace Requirements

Business Process Models

A Business Process
A true business process only concerns business level actors like
people, or organization units, and totally abstracts from any
system supporting it.

Slide19

Copyright 2009, Oracle. All rights reserved.

Business Processes are used to

Identify processes that normally occur in the type of
industry with-in which the business operates
Help identify subject matter experts and other
stakeholders that should be a part of the analysis
and/or review processes in a project
Understand the workflow that may be needed to
support a business process
Identify key performance indicators

Slide20

Copyright 2009, Oracle. All rights reserved.

Oracle Business Process Models

Oracle Business Process Models are represented
using 5 hierarchical levels of decomposition.

Top three levels are conceptual

Services can be observed at the third level
Fourth level is implementation specific
Process integration points appear
on lowest level

Develop System

Trace Requirements

System Context Diagram

System Context Diagram

Product Type
Performance
Request
Data Range
Vendor Type

Procurement
Manager

A/P Specialist

Slide23

Ski-NOW
Procurement
System

Order Confirmation
Cost Confirmation
Order Delivery Date
Quantity Promised

<<actor>>
Supplier
Management

Supplier Delivery
Performance
Supplier Quality
Performance
PO Cost v. Invoice Cost

Purchase Order

Purchase Order
Order Confirmation

Check Number
Check Amount

Bid
Requisition
Vendor Info

Payment Voucher
Invoice

Copyright 2009, Oracle. All rights reserved.

<<actor>>
Finance
System

Develop System
Trace Requirements

Use Case Model

Use Case Model

Online Banking System

Central
Processing
System

Transfer
Between
Accounts

Pay a Bill
Now

Set Up a
Payment
Schedule

Customer

Manage
List of
Payees

XYZ Credit
Bureau

Apply for a
Loan

Select User
Preferences

Approve a Loan

Manage User
Preferences

System Administrator

Loan Approver

Use Case
Model

Slide25

Use Case
Diagram

Copyright 2009, Oracle. All rights reserved.

Use Case
Descriptions

System Use Cases

A system use case describes:
One goal for one actor in using the system
Typically completed in one session (or at one sitting)
The system functionality that supports accomplishing the goal

An actor can represent anything with behavior, including

humans and other systems

Order Skis
Customer

Actor

Use Case

System Use Case Diagram

A view of the functions that the system will automate and
the actors which require those functions
Ski-NOW Procurement

Procurement
Manager

View
Procurement
Dashboard

Settle
Payment
A/P Specialist

Payment
Due Date

Slide27

Copyright 2009, Oracle. All rights reserved.

<<actor>>
Material
Management
(Inventory)
<<actor>>
Supplier
Management
<<actor>>
Trading
Community
<<actor>>
Finance
System

Business Use Case vs System Use Case

Business Use
Case

(System)
Use Case
System Actor

Business Actor

A Business Use Case

A System Use Case

has enterprise as its scope.

has system as its scope.

defines the goals and

functions of a business.

defines a goal of an actor

(user) of the system.

exists regardless of
whether a system exists.
may cover aspects that are
outside the scope of a
system.

Slide28

versus

defines the process for

achieving that goal.
defines functional
requirements that are within
the scope of the system.

Copyright 2009, Oracle. All rights reserved.

Develop System

Trace Requirements

System Design, Test Cases, System Documentation

Use Cases are Inputs to Many OUM Processes and

Artifacts
Enterprise Business Analysis (Envision)
Business Requirements (Implement)
Discover business actors, business processes,
high-level business use cases
Requirements Analysis (Implement)
Define business use cases
Define Use Cases (System)
Analysis/Design (Implement)
Refine and detail Use Cases
Analyze Use Cases and Design System
Implementation (Implement)
Develop Software to Support Use Cases
Testing (Implement)
Develop the Scenarios from the Use Cases
Transition (Implement)
Develop training materials based directly on use cases details
Develop user documentation based on use case details.

Develop System
Trace Requirements

Another Scenario

Another Scenario

Slide32

Copyright 2009, Oracle. All rights reserved.

Another Scenario

Slide33

Copyright 2009, Oracle. All rights reserved.

Another Scenario

Slide34

Copyright 2009, Oracle. All rights reserved.

Another Scenario

Slide35

Copyright 2009, Oracle. All rights reserved.

OUM Provides

Templates for each of the artifacts

Guidance for understanding when in the project life
cycle you might use each of these tools
Instructions and techniques for gathering the
information
JAD Sessions, Reviews, etc.

Instructions for determining which artifact(s) you may

need for a specific type of project implementation

Slide36

Copyright 2009, Oracle. All rights reserved.

Conclusion: Use Cases and Processes in OUM

Learning Check: What are five key artifacts that OUM provides
for performing business analysis, defining the scope of a
system or project, and for defining functional requirements?
Learning Check: What is the difference between a Business
Use Case and a Business Process?
Learning Check: What is the difference between a Business
Use Case and a System Use Case?
Learning Check: What roles in a project may be involved with
the writing or reviewing of a System Use Case?

Slide37

Copyright 2009, Oracle. All rights reserved.

Slide38

Copyright 2009, Oracle. All rights reserved.