PMISV Symposium Presentation

Business Process
Implementation Challenges in
Large Enterprises

Presented By
Ivars Lenss, PMP, CSM
Ivars@Lenss.us

Copyright ©2010 by Ivars Lenss, PMP, CSM

THE “SILO EFFECT”

• The “Silo Effect” is an impediment to
communication because it isolates
individual processes.
• The “Silo Effect” can produce multiple
interpretations of the same requirement.
• Process improvement can break down the
walls that are erected by the “Silo Effect”.


• An enterprise is a set of related elements
that perform functions not performable by
the elements alone.

• A system produces things (products or
services) that are delivered to elements in
the enterprise.

• A business process is a set of activities
that respond to a business event and
produces a business response.

PURCHASING A BOOK ONLINE

BUYER

PLACE RECEIVE CONFIRM MAKE RECEIVE RECEIVE
ORDER PRICE ORDER PAYMENT RECEIPT BOOK

SELLER

RECEIVE CONFIRM CALCULATE RECEIVE SEND
SHIP BOOK
ORDER INVENTORY PRICE PAYMENT RECEIPT


Black-Box System Model
(Functional Perspective)

• Addresses external behavior of the system.

• Models the using and controlling of the system.

• Models the interpretation of a requirement.

• The behavior of the system is brought about by
manipulating its inputs.


White-Box System Model
(Constructional Perspective)

• Addresses internal behavior of the system.

• Models the construction and operation of the
system.

• Models the implementation of a requirement.

• The behavior of a system is brought about, and
consequently explained, by its construction and
operation.


BASIC SYSTEM DESIGN PROCESS

construction determine devise construction
function of
of the US of the OS
requirements the OS specifications

using system object system
(US) New business requirements specify (OS)
processes to be implemented in the OS

These requirements create a need in the using system (US)
of an object system (OS) to implement the requirements

Portions ©2008 ACM
Used by permission


First, one analyzes the business requirements of the OS
in terms of a white-box model of the of the US

function of
of the US of the OS

(US) (OS)

Portions ©2008 ACM
Used by permission


The next basic design step is to devise specifications for the
construction and operation of the OS, in terms of a white-box
model of the OS (construction design).

function of
of the US of the OS

(US) (OS)

Portions ©2008 ACM
Used by permission


The US business requirements refer to the function and the behavior
of the OS, and are thus in terms of a black-box model of the OS

function of
of the US of the OS

(US) (OS)

Portions ©2008 ACM
Used by permission


BUSINESS REQUIREMENTS ARE
BUSINESS RULES

• Business requirements are either
business rules, or they become rules
once implemented.

• Business requirements define what
shall occur in response to a given
business event.


TOP-DOWN SYSTEM VIEW
VIEWS A SYSTEM IN TERMS OF BUSINESS EVENTS AND BUSINESS PROCESSES

EXPECTED RESULTS ARE
REPRESENTED IN THE OUTPUT DATA

3
SYSTEM OUTPUT DATA
INPUT DATA
(BUSINESS PROCESS)

2
DETERMINE WHAT BUSINESS EVENTS TRIGGER
THE BUSINESS PROCESSES OF INTEREST.
1
CHOOSE THE BUSINESS
DETERMINE HOW THESE EVENTS ARE
PROCESSES OF INTEREST
REPRESENTED IN THE INPUT DATA.


BOTTOM-UP SYSTEM VIEW
VIEWS A SYSTEM IN TERMS OF BUSINESS RESPONSES TO BUSINESS PROCESSES

EXPECTED RESULTS ARE
REPRESENTED IN THE INPUT DATA

3
SYSTEM OUTPUT DATA
INPUT DATA
(BUSINESS PROCESS)

1
CHOOSE THE BUSINESS
DETERMINE WHAT BUSINESS
2 RESPONSES OF INTEREST
PROCESSES PRODUCE THE
BUSINESS RESPONSES OF INTEREST


PRODUCING INFORMATION FROM DATA

I
N
T
E
R
SYSTEM P
INPUT DATA OUTPUT DATA
OUTPUT R INFORMATION
(BUSINESS PROCESS) E
T
A
T
I
O
N

OBJECTIVE, OBJECTIVE, SUBJECTIVE
UNAMBIGUOUS UNAMBIGUOUS


CROSS-SYSTEM DATA AND INFORMATION

SYSTEM I/P DATA SYSTEM
O/P DATA
A B



I I
N N
T T
E E
R
SYSTEM INFORMATION
R
I/P DATA SYSTEM
O/P DATA P P
A R B
R
E E
T T
A A
T T
I I
O O
N N

BUSINESS REQUIREMENTS ADDRESS INFORMATION. DATA MUST BE
INTERPRETED TO PRODUCE THIS INFORMATION.
THE INTERPRETATIONS MUST BE RECONCILED FOR THE REQUIREMENT
TO BE UNDERSTOOD AND IMPLEMENTED CORRECTLY IN BOTH SYSTEMS.


I I
N N
T T
E E
R
SYSTEM INFORMATION
R
I/P DATA SYSTEM
O/P DATA P P
A R B
R
E E
T T
A A
T T
I I
O O
N N

IDEALLY, THE TWO INTERPRETATIONS ARE IDENTICAL WITH RESPECT
TO THE INFORMATION FLOWING FROM SYSTEM ‘A’ TO SYSTEM ‘B’.
THIS IS NOT ALWAYS THE CASE, AND IS A SOURCE OF DEFECTS AS
NEW BUSINESS REQUIREMENTS ARE IMPLEMENTED.


Business Requirements Workflow Loop
A REQUIREMENT
IS NEGOTIATED

REQUEST NEGOTIATE

A REQUIREMENT
A REQUIREMENT DEFINE
IS AGREED TO BE
IS STATED BY THE REQUIREMENT
IMPLEMENTED
CUSTOMER

A VALIDATED
REQUIREMENT IS
DELIVERED TO
THE CUSTOMER

AN IMPLEMENTATION IMPLEMENT A REQUIREMENT
OF THE REQUIREMENT REQUIREMENT IS IMPLEMENTED
IS ACCEPTED BY THE
CUSTOMER

COMPLETE PERFORM
AN IMPLEMENTED AN IMPLEMENTED
REQUIREMENT IS REQUIREMENT IS
VALIDATED PRESENTED FOR
VALIDATION



REQUEST

A REQUIREMENT
IS STATED BY THE
CUSTOMER


A REQUIREMENT
IS NEGOTIATED

REQUEST NEGOTIATE

A REQUIREMENT
IS AGREED TO BE
IMPLEMENTED
CUSTOMER


A REQUIREMENT
IS NEGOTIATED

REQUEST NEGOTIATE

A REQUIREMENT
IS AGREED TO BE
IMPLEMENTED
CUSTOMER

IMPLEMENT A REQUIREMENT
REQUIREMENT IS IMPLEMENTED

PERFORM


A REQUIREMENT
IS NEGOTIATED

REQUEST NEGOTIATE

A REQUIREMENT
IS AGREED TO BE
IMPLEMENTED
CUSTOMER


PERFORM
AN IMPLEMENTED AN IMPLEMENTED
REQUIREMENT IS REQUIREMENT IS
VALIDATED PRESENTED FOR
VALIDATION


A REQUIREMENT
IS NEGOTIATED

REQUEST NEGOTIATE

A REQUIREMENT
IS AGREED TO BE
IMPLEMENTED
CUSTOMER

AN IMPLEMENTED
REQUIREMENT IS
DELIVERED TO THE
CUSTOMER

AN IMPLEMENTED
REQUIREMENT IS
PERFORM
VALIDATED BY
THE CUSTOMER


A REQUIREMENT
IS NEGOTIATED

REQUEST NEGOTIATE

A REQUIREMENT
IS AGREED TO BE
IMPLEMENTED
CUSTOMER

AN IMPLEMENTED
REQUIREMENT IS
DELIVERED TO
THE CUSTOMER
AN IMPLEMENTATION IMPLEMENT A REQUIREMENT
OF THE REQUIREMENT REQUIREMENT IS IMPLEMENTED
IS ACCEPTED BY THE
CUSTOMER

COMPLETE PERFORM


Quality Assurance from a Business
Requirements Perspective

• End-to-End Verification and Validation
– Simulate Business Events to trigger Business
Responses.
– Verify expected results against Business
Requirements.

• Designed to verify the Business of the Enterprise, that
business events and business responses occur
correctly.

• Focuses exclusively from the end user’s perspective.


Q&A and Comments

Ivars@Lenss.us

Ivars Lenss, PMP, CSM
PMISV Annual Symposium
September 20-21, 2010


PMISV Symposium Presentation

Recommended

Recommended

More Related Content

Similar to PMISV Symposium Presentation

Similar to PMISV Symposium Presentation (20)

PMISV Symposium Presentation