Module - Business Analysis, Scoping, and Requirements Gathering.ppt

Copyright © 2009, Oracle. All rights reserved.SlideSlide 11SlideSlide 11

LEVEL 2 TRAININGOracle® Unified Method OUM Use Case Overview

Business Analysis, Scoping, and Requirements Gathering


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


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 actor’s 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

From Business Context to System Design,Test Cases, and System Documentation

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts

Business Context Diagram

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts

Business Use Case Model

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts

Business Process Models

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts

System Context Diagram

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts

Use Case Model

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts

System Design, Test Cases, System Documentation

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts


De

velo

p S

ys

temT

race

Re

qu

ire

me

nts

Understand the Business Context

• It’s important to define the boundary of the business or business area before defining it’s 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

Business AreaKey Information

Copyright © 2009, Oracle. All rights reserved.SlideSlide 1313


Customer

Supplier

Ski-NOW

Procurement Manager

Buyer

• Order Request

• Procurement Data • Purchase Order• Order Confirmation• Invoice• Product Shipment

• Bid• Requisition• Vendor Info

• Purchase Order• Order Confirmation

• Purchase Order Approval

• Procurement Request

• Reject Notification

• Paid Invoice• Fulfillment Statistics

Business Use Case Model

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts


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

Analyze Procurement


Business Use Case Diagram

• A view of the functions of a business and of the actors which require those functions

Receiving Agent

BuyerSki-NOW

A/P Specialist

Supplier

Procurement Manager

Settle Payment

Analyze Procurement


Most Important OUM Business Use Case Details

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

Business Process Models

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts


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.


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

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


De

velo

p S

ys

temT

race

Re

qu

ire

me

nts



Ski-NOW Procurement

System

Procurement Manager

A/P Specialist

• Supplier Delivery Performance

• Supplier Quality Performance

• PO Cost v. Invoice Cost

• Bid• Requisition• Vendor Info

• Purchase Order• Order Confirmation

• Product Type• Performance

Request• Data Range• Vendor Type

<<actor>> Supplier

Management

<<actor>>Finance System

• Payment Voucher• Invoice

• Check Number• Check Amount

• Purchase Order

• Order Confirmation• Cost Confirmation• Order Delivery Date• Quantity Promised

Use Case Model

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts


Use Case Model

+Customer

System AdministratorLoan Approver

Transfer Between Accounts

Online Banking SystemCentral

Processing System

XYZ Credit Bureau

Pay a Bill Now

Set Up a Payment Schedule

Manage List of

Payees

Apply for a Loan

Approve a Loan

Select UserPreferences

Manage UserPreferences

Use Case Diagram

Use Case Descriptions+

Use Case Model =

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

ActorUse 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

<<actor>> Material

Management (Inventory)

<<actor>> Supplier

Management

<<actor>> Trading

Community

<<actor>>Finance System

Settle Payment

A/P Specialist

Payment Due Date


Business Use Case vs System Use Case

A Business Use Case…

…has enterprise as its scope.

…defines the goals and functions of a business.

…exists regardless of whether a system exists.

…may cover aspects that are outside the scope of a system.

A System Use Case…

…has system as its scope.

…defines a goal of an actor (user) of the system.

…defines the process for achieving that goal.

…defines functional requirements that are within the scope of the system.

versus

Business Use Case

(System)Use Case

System ActorBusiness Actor

System Design, Test Cases, System Documentation

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts

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.

Another Scenario

De

velo

p S

ys

temT

race

Re

qu

ire

me

nts


Another Scenario


Another Scenario


Another Scenario


Another Scenario


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


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?


Documents

Module - Business Analysis, Scoping, and Requirements Gathering.ppt