1. Enterprise Architecture for Successful Projects
Richard Freggi
Senior supply chain architect
Hewlett-Packard Company

2. What do you need to KNOW to make sure a Project can succeed?
Refer to: https://en.wikipedia.org/wiki/Zachman_Framework
Program code
John A. Zachman, Zachman International (810) 231-0531
DATA
what
FUNCTION
how
NETWORK
where
PEOPLE
who
TIME
when
MOTIVATION
why
CONTEXT
General
M anager
Things
important for
the business
Business
Functions
List of
business
locations
Organization
structure
Business
strategy
timeline
List of
business
priorities
CONCEPT
Line
M anager
Semantic data
dictionary
Business
Process
Business
Logistic
System
Roles and
responsibilities
Business event
timeline
Business Plan
and Budget
LOGICAL
Architect
Project M anager
Logical Data
Model
Application
Architecture
Distributed
System
Architecture
Software
interface
Processing
timing and
sequencing
Business Role
Model
PHYSICAL
IT M anager
Database
Schema
Software
Specification /
Configuration
Hardware and
network
infrastructure
Presentation
Architecture
Control
structure
System Role
Design
OUT OF CONTEXT
Subcontractor
Implementor
Database
Definition
Language
System
components
Access and
security system
Timing
definition
System Role
Configuration

3. Small Projects may require only one Box
…..Where there is no dependency on other boxes
Program code
John A. Zachman, Zachman International (810) 231-0531
DATA
what
FUNCTION
how
NETWORK
where
PEOPLE
who
TIME
when
MOTIVATION
why
CONTEXT
General
M anager
Things
important for
the business
Business
Functions
List of
business
locations
Organization
structure
Business
strategy
timeline
List of
business
priorities
CONCEPT
Line
M anager
Semantic data
dictionary
Business
Process
Business
Logistic
System
Roles and
responsibilities
Business event
timeline
Business Plan
and Budget
LOGICAL
Architect
Project M anager
Logical Data
Model
Application
Architecture
Distributed
System
Architecture
Software
interface
Processing
timing and
sequencing
Business Role
Model
PHYSICAL
IT M anager
Database
Schema
Software
Specification /
Configuration
Hardware and
network
infrastructure
Presentation
Architecture
Control
structure
System Role
Design
OUT OF CONTEXT
Subcontractor
Implementor
Database
Definition
Language
System
components
Access and
security system
Timing
definition
System Role
Configuration
Example: making a small enhancement to an Application: no need to review boxes for Context, Concept, ecc...
Domain is well understood and there
are no dependencies on other boxes

4. Why do Projects fail?
Many larger Projects ignore information essential for success
Program code
John A. Zachman, Zachman International (810) 231-0531
DATA
what
FUNCTION
how
NETWORK
where
PEOPLE
who
TIME
when
MOTIVATION
why
CONTEXT
General
M anager
Things
important for
the business
Business
Functions
List of
business
locations
Organization
structure
Business
strategy
timeline
List of
business
priorities
CONCEPT
Line
M anager
Semantic data
dictionary
Business
Process
Business
Logistic
System
Roles and
responsibilities
Business event
timeline
Business Plan
and Budget
LOGICAL
Architect
Project M anager
Logical Data
Model
Application
Architecture
Distributed
System
Architecture
Software
interface
Processing
timing and
sequencing
Business Role
Model
PHYSICAL
IT M anager
Database
Schema
Software
Specification /
Configuration
Hardware and
network
infrastructure
Presentation
Architecture
Control
structure
System Role
Design
OUT OF CONTEXT
Subcontractor
Implementor
Database
Definition
Language
System
components
Access and
security system
Timing
definition
System Role
Configuration
Typical path of failed Project
Why does this happen?
Business Processes are not defined, or
they are not aligned with IT Systems
Most of Project work focuses on
software development or technology

5. How can Projects succeed?
Make sure you understand all necessary information in detail!
Program code
John A. Zachman, Zachman International (810) 231-0531
DATA
what
FUNCTION
how
NETWORK
where
PEOPLE
who
TIME
when
MOTIVATION
why
CONTEXT
General
M anager
Things
important for
the business
Business
Functions
List of
business
locations
Organization
structure
Business
strategy
timeline
List of
business
priorities
CONCEPT
Line
M anager
Semantic data
dictionary
Business
Process
Business
Logistic
System
Roles and
responsibilities
Business event
timeline
Business Plan
and Budget
LOGICAL
Architect
Project M anager
Logical Data
Model
Application
Architecture
Distributed
System
Architecture
Software
interface
Processing
timing and
sequencing
Business Role
Model
PHYSICAL
IT M anager
Database
Schema
Software
Specification /
Configuration
Hardware and
network
infrastructure
Presentation
Architecture
Control
structure
System Role
Design
OUT OF CONTEXT
Subcontractor
Implementor
Database
Definition
Language
System
components
Access and
security system
Timing
definition
System Role
Configuration
A better Project path

6. Case Study: Reduction of Inventory Cost
Summary of a failed Project
Background:
◦ High inventory caused very high storage and transportation costs and forced goods sale below cost
Corrective action:
◦ Started Inventory Management program
◦ Assembled key Stakeholders, gathered requirements, hired consultant to configure the system
Result:
◦ 12 months Project
◦ High Project expenses
◦ System changes implemented, but no benefit
◦ No changes in operating procedure; root causes of high inventory remain

7. Path of the failed Project
Program code
John A. Zachman, Zachman International (810) 231-0531
DATA
what
FUNCTION
how
NETWORK
where
PEOPLE
who
TIME
when
MOTIVATION
why
CONTEXT
General
M anager
Things
important for
the business
Business
Functions
List of
business
locations
Organization
structure
Business
strategy
timeline
List of
business
priorities
CONCEPT
Line
M anager
Semantic data
dictionary
Business
Process
Business
Logistic
System
Roles and
responsibilities
Business event
timeline
Business Plan
and Budget
LOGICAL
Architect
Project M anager
Logical Data
Model
Application
Architecture
Distributed
System
Architecture
Software
interface
Processing
timing and
sequencing
Business Role
Model
PHYSICAL
IT M anager
Database
Schema
Software
Specification /
Configuration
Hardware and
network
infrastructure
Presentation
Architecture
Control
structure
System Role
Design
OUT OF CONTEXT
Subcontractor
Implementor
Database
Definition
Language
System
components
Access and
security system
Timing
definition
System Role
Configuration

8. Actual Schedule of the failed Project
Requirement gathering focuses on 'wish
list' and ignores Business Processes
Discussions do not have a common language – users
confuse each other using different names for the same
things
Final Requirement Document is based on mutually
conflicting user requirements and ignores feasibility
and usability
Development work starts without spec validation or
signoff by a Sponsor
Demo does not fully satisfy any user; users
submit new 'wish lists'
The Project 'restarts' with a new look at user
requirements
Development work continues anyway
Project Stops without achieving business benefit

9. Try again with a different approach!
Program code
John A. Zachman, Zachman International (810) 231-0531
DATA
what
FUNCTION
how
NETWORK
where
PEOPLE
who
TIME
when
MOTIVATION
why
CONTEXT
General
M anager
Things
important for
the business
Business
Functions
List of
business
locations
Organization
structure
Business
strategy
timeline
List of
business
priorities
CONCEPT
Line
M anager
Semantic data
dictionary
Business
Process
Business
Logistic
System
Roles and
responsibilities
Business event
timeline
Business Plan
and Budget
LOGICAL
Architect
Project M anager
Logical Data
Model
Application
Architecture
Distributed
System
Architecture
Software
interface
Processing
timing and
sequencing
Business Role
Model
PHYSICAL
IT M anager
Database
Schema
Software
Specification /
Configuration
Hardware and
network
infrastructure
Presentation
Architecture
Control
structure
System Role
Design
OUT OF CONTEXT
Subcontractor
Implementor
Database
Definition
Language
System
components
Access and
security system
Timing
definition
System Role
Configuration

10. Actual schedule of the new approach
Quick generation of Functional Model using Process
Modelling software tools. Conflicting Processes are
resolved.
Application Architecture based on Business
Process support and cost
Smooth rollout because Business Process support
is verified
Semantic Data Dictionary available from
Functional Models. All users share same
language: fast, productive discussions
User Requirements are based on the Business
Processes
Testing routines based generated from the
Business Processes
Use Reference Functional Models
available in the market
Users and Managers formally commit to the new
Processes. Role of IT is to build a system to support the
agreed Processes.