You are on page 1of 30

<Insert Picture Here>

Oracle Unified Method (OUM)


Level 2: Implement Focus Area Overview
Module: OUM Principles

Learning Objectives
OUM Principles

By the end of this module, you should be able to:


Describe the 5 main principles of the Oracle Unified Method
(OUM).
Understand how these principles have influenced OUM
development.

2008, 2010 Oracle and/or its affiliates. All rights reserved.

OUM Principles

Business Process
& Use Case-Driven
OUM

Flexible
& Scalable

Envision Implemen
t

Iterative &
Incremental

Manage

Risk-Focused

2008, 2010 Oracle and/or its affiliates. All rights reserved.

Architecture-Centric

Business Process and Use Case-Driven


Business processes and use cases are the primary
mechanisms for gathering functional requirements
Requirements are documented through
Business Process Models
Use Cases
Written Supplemental and Quality of Service Requirements

2008, 2010 Oracle and/or its affiliates. All rights reserved.

Business Process

1. A series of linked tasks designed to produce a


product, service or major business deliverable
2. A collection of inter-related tasks which solve a
particular issue

Manage Logistics
and Warehousing

Define Logistics
Strategy

Plan Inbound
Material Flow

2008, 2010 Oracle and/or its affiliates. All rights reserved.

Operate
Warehousing

Operate
Outbound
Transportation

Manage Returns
and Reverse
Logistics

Business Process Models

Used to document and


understand business
processes
Also used to understand
how software supports a
business process
Software solutions are
frequently documented
using process models

2008, 2010 Oracle and/or its affiliates. All rights reserved.

Use Case
Technique for eliciting, analyzing, documenting, and
communicating functional requirements
Links requirements to Design and Test
Bridges gap between business modeling, business
processes, and software system functionality
Identify implicit or unstated requirements
Enable traceability of requirements through testing

UML
UMLicon
iconfor
foraause
usecase
case

2008, 2010 Oracle and/or its affiliates. All rights reserved.

A Use Case
Describes the behavior of a business or system
Describes how actors use business or system to
accomplish goals
Is expressed by sequences of exchanges
Does not reveal internal structure
Bundles together a set of related scenarios
Use Case Diagram

Use Case Details


Use Case Details: Order Skis
Actor Does
1. The customer
selects the skis
that he wishes to
order.

Customer

System Does
2. The system
checks the
availability of

Add learning check point


OUM Principles

2008, 2010 Oracle and/or its affiliates. All rights reserved.

Iterative and Incremental


Break down phases into iterations.
Allow for more frequent checkpoints and tollgates.

Overall
Project
Plan

Overall
OverallProject
Project

Implementation
Plan

Iteration
Plan
Increasing
Abstraction
& Horizon

2008, 2010 Oracle and/or its affiliates. All rights reserved.

Increasing
Detail &
Precision

10

Add interaction

2008, 2010 Oracle and/or its affiliates. All rights reserved.

11

Iterations, Increments, Releases


OUM employs an iterative and incremental approach.
The result of an iteration is an increment.
A release does not necessarily include a software
build

2008, 2010 Oracle and/or its affiliates. All rights reserved.

12

Learning Checkpoint
OUM Principles

2008, 2010 Oracle and/or its affiliates. All rights reserved.

13

Iterative Development

2008, 2010 Oracle and/or its affiliates. All rights reserved.

14

A Project is a Series of Mini-Projects


Inception

Iteration 1

Elaboration

Iteration 1
LO
LO

15

Construction

Iteration 1

Iteration 2
LA
LA

Iteration 2

Transition

Production

Iteration 1

Iteration 1

Iteration 3
IOC
IOC

SP
SP

SO
SO

15

Release

Inception
Iterations

Elaboration

Construction

Transition

Production

10

time

Releases
2008, 2010 Oracle and/or its affiliates. All rights reserved.

16

Concepts of Iterations and Increments


Register Employees

Assess Service
Requests

Register Customer
Plan Customer
Visits

Replan Customer
Visits
Register Suppliers

Invoice Service
Requests

Log Service
Request by
Customer

Pay Suppliers

Automatic Sign-Off
Service Requests
Order Parts

Accept Service
Requests

Notify Parts
Available
Restock Service
Cars

2008, 2010 Oracle and/or its affiliates. All rights reserved.

Update Services
Requests

Log Service
Request by
Helpdesk

Sign-Off Service
Requests

17

Concepts of Iterations and Increments

2008, 2010 Oracle and/or its affiliates. All rights reserved.

18

Use Cases Group by Priority into Iteration Groups


Iteration Group 1

Increment
Increment 11

Iteration Group 2

Iteration Group 3

Change
Change
Requests
Requests for
for
Increment
Increment 11

Change
Change
Requests
Requests for
for
Increment
Increment 22

Increment
Increment 22

Increment
Increment 33
19

Architecture
More than just technical architecture
Set of significant decisions about the organization of a
software system
Collection of models that describe the system
Includes structural elements and interfaces, and their
behavior

2008, 2010 Oracle and/or its affiliates. All rights reserved.

20

Architecture-Centric
The systems architecture is used as a primary artifact
for conceptualizing, constructing, managing, and
evolving the system
The Architecture Description is a key work product of
Elaboration.

2008, 2010 Oracle and/or its affiliates. All rights reserved.

21

Learning Checkpoint
OUM Principles

2008, 2010 Oracle and/or its affiliates. All rights reserved.

22

Risk-Focused

A key focus of each iteration in OUM is to identify


and reduce the most significant project risks.
This ensures that the project team addresses the
most critical risks as early a possible.

2008, 2010 Oracle and/or its affiliates. All rights reserved.

23

Flexible and Scalable

Tailor to Appropriate Level of Ceremony


Guidance provided for

Minimum Set of Tasks


Tailoring Workplan
Iterative Project Planning
Timeboxing and Prioritization
Agile Techniques

2008, 2010 Oracle and/or its affiliates. All rights reserved.

24

Flexible and Scalable: Fit-for-Purpose

Adapted from Dynamic Systems Development


Method (DSDM)
Focused on delivering necessary functionality
within the required timebox
Also refers to defining level of rigor
and ceremony appropriate to project

2008, 2010 Oracle and/or its affiliates. All rights reserved.

25

Learning Checkpoint
OUM Principles

2008, 2010 Oracle and/or its affiliates. All rights reserved.

26

OUMs Application Implementation Approach


Similar to legacy methods in these areas:
Business Processes
Future Business Processes Fit/Gap
Key Business Architecture Structures
Application Setups
Leading Practices from Oracles Legacy Methods
Supports:
Requirements-Driven (AIM Foundation, Compass Standard)
Solution-Driven (AIM for Business Flows, Compass Accelerated)
Software Upgrade

2008, 2010 Oracle and/or its affiliates. All rights reserved.

27

Oracle Unified Method Approach


OUMs implementation approach differs from legacy
methods in these areas:
Standards-based Unified Process
More comprehensive
Supports both enterprise and project-level activities
Tighter integration across disciplines
Tighter integration with sales cycle
Increased emphasis on Architecture

2008, 2010 Oracle and/or its affiliates. All rights reserved.

28

Conclusion
OUM Principles

Now that you have completed this module, you should


be able to:
Describe the 5 main principles of the Oracle Unified Method
(OUM).
Understand how these principles have influenced OUM
development.

2008, 2010 Oracle and/or its affiliates. All rights reserved.

29

2008, 2010 Oracle and/or its affiliates. All rights reserved.

30

You might also like