Objectives Models Business Objectives Model

Goals  qualitative statements

Business problem  either increasing revenue or reducing costs
Business objectives measurable statements

When to Use
Project that has new functionality that can be mapped to business value: enhancements, new
custom development projects, Commercial Off the Shelf (COTS) deployments that have significant
customizations.

When Not to Use

Legacy conversions: implementing a new system to replace an old one to maintain existing key
performance indicators (KPIs) with existing business processes. Key Performance Indicator Model
(KPIM) is more useful.
 Objectives Key Performance Indicator Model

KPIM mechanism to identify, organize, and document the business outcomes across
business process to ensure that any changes to the system maintain the existing business
outcomes at or above the current level.

When to Use
upgrading existing systems and automating business processes
can be used to derive non-functional requirements
When Not to Use
implementing all-new functionality

Identify the KPI for the step

How much volume will go through this step?
■How do we determine the quality of the step?
• How many errors are acceptable?
• How often is manual intervention required?
• How large of an error is acceptable?
■ How long does it take to complete the step?
■ How many people does it take to complete the step?
■ How many people in the company execute this step?
 Data Models Business Data Diagram
BDD describes how users think about their data.
• Conceptual data models
• BDD does not imply a database design
• show business data objects from a business stakeholder’s perspective  -->
• whereas ERDs show the actual implementation of objects in a database schema

When to Use
Any project that has databases will use BDDs, just for the major business data objects
the business cares about
When Not to Use
stateless calculations (computations) but that does not store anything or
that just passes data straight through (such as an API)

■■ Business data object 1 relates to zero or one of business data object 5.

■■ Business data object 5 relates to one or more of business data object
1.
If an object relates to more than one object or has fields itself, then it is an
object; otherwise it is a field.