1 By Len Silverston, Universal Data Models, LLC Universal Principles and Models Towards Integration

1

By Len Silverston,By Len Silverston,

Universal Data Models, LLCUniversal Data Models, LLC

Universal Principles and Models Towards Integration

Universal Principles and Models Towards Integration

2

What is Needed?What is Needed?Commitment?Commitment?

Resources?Resources?

Expertise?Expertise?

Methodologies?Methodologies?

Tools?Tools?

Technology?Technology?

Connections betweenPEOPLE!???

3

What is Needed?What is Needed?Commitment?Commitment?

Resources?Resources?

Expertise?Expertise?

Methodologies?Methodologies?

Tools?Tools?

Technology?Technology?

Connections betweenPEOPLE!


4

•Define IntegrationDefine Integration•PrinciplesPrinciples•Universal data modelsUniversal data models•ActionsActions

AgendaAgenda

5

What is IntegrationWhat is Integration

““Combining into a whole” Combining into a whole”

6

Versus DisintegrationVersus Disintegration

““To separate into parts”To separate into parts”

7

Integration as a ParadoxIntegration as a Paradox

TWO become ONE TWO become ONE yet remain TWOyet remain TWO

8

Integration as a ParadoxIntegration as a Paradox

MANY become ONE MANY become ONE yet remain INDIVIDUALyet remain INDIVIDUAL

1:M

9

Disparate DatabasesDisparate Databases

•Databases Equal BudgetsDatabases Equal Budgets•Project DrivenProject Driven

10

Planting in Fertile SoilPlanting in Fertile Soil

11

Common Common

GoalsGoals

Integration PrinciplesIntegration Principles

TrustTrust

Appreciate

Appreciate

Perspectives

Perspectives

Re-UseRe-Use

12

Integration Requires TRUST (IRT)

PRINCIPLE #1PRINCIPLE #1Integration Requires TRUST (IRT)Integration Requires TRUST (IRT)

TrustTrust

““Integrity” derived from “To Integrate”Integrity” derived from “To Integrate”

13

TrustTrust

Financial InstitutionFinancial Institution

14

Lack of TrustLack of Trust

Insurance organizationInsurance organization

15

VulnerabilityVulnerability

A Key to TrustA Key to Trust

16

Should we always trust?Should we always trust?

•Continued Mistakes?Continued Mistakes?•Politics?Politics?•Who’s In Charge?Who’s In Charge?

17

Principle #2Principle #2

Keep Sight of the GOALKeep Sight of the GOAL

Common Common

GoalsGoals

18

Keep Big Picture in SightKeep Big Picture in Sight

DataDataWarehouseWarehouse




““If you have more than one data If you have more than one data warehouse, then you don’t have warehouse, then you don’t have

any”any”Bill InmonBill Inmon

19

Keep Sight of the GoalKeep Sight of the Goal

Business GoalsBusiness Goals

Information Technology (IT) Goals

20

Keep Sight of the GoalKeep Sight of the Goal



IT Goals/Systems

IT Goals/Systems

21

ObstaclesObstacles

•Overusing “My”Overusing “My”•BlamestormingBlamestorming•““line of sight”line of sight”

22

Sight of the Goal -Sight of the Goal -Not Attachment To It!Not Attachment To It!

23

PRINCIPLE #3PRINCIPLE #3

APPRECIATE PERSPECTIVESAPPRECIATE PERSPECTIVESVersus Being RightVersus Being Right

Appreciate

Appreciate

Perspectives

Perspectives

24

The“Right”Approach?The“Right”Approach?

““My way is the right way!”My way is the right way!”

25

What Is The Truth?What Is The Truth?

Wholism = truthWholism = truth

Truth is paradoxicalTruth is paradoxical

26

Who’s data is “right”?Who’s data is “right”?

27

PossibilitiesPossibilities

•LeadershipLeadership•Adding to PerspectivesAdding to Perspectives• Including the PositiveIncluding the Positive

28

PRINCIPLE #4PRINCIPLE #4

Learn from the PASTLearn from the PAST

Re-UseRe-Use

29

Learn From the PastLearn From the PastRoles?Roles? StatusesStatuses

Product?Product? Work efforts?Work efforts?

Contact Info?Contact Info?

TransactionsTransactions

Communications?Communications?

30

Two type of RolesTwo type of Roles

Declarative rolesDeclarative roles

Contextual rolesContextual roles

31

Roles - DeclarativeRoles - Declarative

ROLE TYPE

describedby the

descriptionfor

# ROLE TYPE ID* DESCRIPTION

~

PERSON ORGANIZATION

PARTY

PARTY ROLE

# PARTY ID

# PARTY ID# ROLE TYPE ID* FROM DATEo THRU DATE

acting as

for ~

o CURRENT FIRST NAMEo CURRENT LAST NAME o CURRENT ORGANIZATION NAME

CUSTOMER

REGULATORYAGENCY

DISTRIBUTION CHANNELAGENT

FAMILY MEMBERCONTACT

SHAREHOLDER

DISTRIBUTOR

HOUSEHOLD

SUPPLIER

ASSOCIATIONCOMPETITOR

BILL TO CUSTOMER

SHIP TO CUSTOMER

END USER CUSTOMER

WORKER

CONTRACTOR

WEB SITE VISITOR

REFERRER

PARTNERPROSPECT

EMPLOYEE

32

Roles Contextual - SpecificRoles Contextual - Specific

managed by

managing

PROJECTMANAGER

PROJECT

# PROJECT ID* NAME* DESCRIPTIONo SCHEDULED START DATEo SCHEDULED END DATEo SCHEDULED COMPLETION DATEo TOTAL DOLLARS ALLOWEDo TOTAL HOURS ALLOWEDo ESTIMATED HOURSo ACTUAL START DATETIMEo ACTUAL COMPLETION DATETIMEo ACTUAL HOURSo SPECIAL TERMS

~

is sponsoredby

sponsoring

SPONSORPROJECTSPONSOR

~

for

by

owned by

owning

WORKERPROJECTASSIGNMENT ~

~

for

by

lead by

leadingPROJECT LEAD

PROS/CONS?

33

Roles Contextual – AbstractRoles Contextual – Abstract

WORK EFFORT

# WORK EFFORT ID* NAME* DESCRIPTIONo SCHEDULED START DATEo SCHEDULED END DATEo SCHEDULED COMPLETION DATEo TOTAL DOLLARS ALLOWEDo TOTAL HOURS ALLOWEDo ESTIMATED HOURSo ACTUAL START DATETIMEo ACTUAL COMPLETION DATETIMEo ACTUAL HOURSo SPECIAL TERMS

PARTY

# PARTY ID

WORK EFFORT ROLEassignedto

within

describedby

thedescriptionfor

involvedin

~

# WORK EFFORT ID# PARTY ID# ROLE TYPE ID# WORK EFFORT ROLE SEQ ID* FROM DATEo THRU DATE

ROLE TYPE


involving

~~

WORK EFFORT ROLE TYPE

34

Specific Versus AbstractSpecific Versus Abstract

Specific constructsSpecific constructs Understandability Rules Enforcement

Generic constructsGeneric constructs Flexibility

Show both?Show both?

35

Modeling Specific and AbstractModeling Specific and Abstract

PROJECT


owned by

~

is sponsoredby

managed by

lead by

sponsoring

owning

managing

leading

PROJECTSPONSOR

PROJECTASSIGNMENT ~

~

~

~

for

for

by

by

~PROJECTMANAGER

WORKER

SPONSOR

PROJECT LEAD


PARTY ROLE

ROLE TYPE


~

PARTY

# PARTY ID

~

acting as

for describedby

the descriptionfor

~~

~

PROJECT ROLE# PROJECT ID# PARTY ID# ROLE TYPE ID# PROJECT ROLE ID* FROM DATEo THRU DATE

described by

the description for

assigned to

involved in

involving

within

assigned to

PROJECT


owned by

~

is sponsoredby

managed by

lead by

sponsoring

owning

managing

leading

PROJECTSPONSOR

PROJECTASSIGNMENT ~

~

~

~

for

for

by

by

~PROJECTMANAGER

WORKER

SPONSOR

PROJECT LEAD

PROJECT


Roles Versus Roles Versus Involvements?Involvements?

PERSON

ORGANIZATION

PARTY

PARTY ROLE

# PARTY ID


ROLE TYPEacting as

fordescribedby

thedescriptionfor


PARTY ROLE TYPE

~ ~

involving

WORK EFFORT

# WORK EFFORT ID

WORK EFFORT ROLE

# WORK EFFORT ID# PARTY ID# ROLE TYPE ID# WORK EFFORT ROLEID* FROM DATE

o THRU DATE

assigned to

assignedto

involved in describedby the description

for~

WORK EFFORT ROLE TYPE

Roles Versus Roles Versus Involvements?Involvements?

PERSON

ORGANIZATION

PARTY

PARTY ROLE

# PARTY ID


ROLE TYPEacting as

fordescribedby

thedescriptionfor


~ ~

involving

WORK EFFORT

# WORK EFFORT ID

WORK EFFORT INVOLVEMENT

# WORK EFFORT ID# PARTY ID# INVOLVEMENT TYPE ID# WORK EFFORT INVOLVEMENT ID* FROM DATE

o THRU DATE

assigned to

assignedto

involved in

~INVOLVEMENT TYPE

# INVOLVEMENT TYPE ID* DESCRIPTION

WORK EFFORTINVOLVEMENTTYPE

thedescriptionfor

describedby ~

SHIPMENTINVOLVEMENTTYPE

38

StatusesStatuses

As attributesAs attributes

As entitiesAs entities

Generic entitiesGeneric entities

39

Statuses as attributesStatuses as attributes

ORDER

# ORDER ID* ORDER RECEIVED DATEo ORDER ENTRY DATEo CONFIRMATION DATEo EXPECTED SHIPMENT DATEo APPROVED DATEo CANCELLATION DATEo SHIPPED DATEo FULFILLMENT DATEo INVOICED DATE

40

Statuses as entitiesStatuses as entities

ORDER STATUS

# ORDER ID# STATUS TYPE ID# ORDER STATUS ID* STATUS DATETIME

a status for

in the state of

ORDER

# ORDER ID

the description for

described by

ORDER STATUS TYPE

STATUS TYPE

# STATUS TYPE ID* DESCRIPTION

RECEIVEDENTEREDCONFIRMEDEXPECTED SHIPMENTAPPROVEDCANCELLED DATE

Roles and Statuses Occur for Roles and Statuses Occur for Many Types of TransactionsMany Types of Transactions

INVOICESHIPMENT PAYMENT GENERAL LEDGER TRANSACTION

ORDERCOMMUNICATION EVENT

INVOICEROLE

SHIPMENTROLE

PAYMENTROLE

GENERAL LEDGER TRANSACTION ROLE

ORDER ROLE

COMMUNICATION EVENT ROLE

PARTY

WORK EFFORT

WORK EFFORTROLE

SHIPMENT

INVOICESTATUS

PAYMENTSTATUS

GENERALLEDGERTRANSACTIONSTATUS

WORK EFFORTSTATUS

SHIPMENTSTATUS

ORDERSTATUS

COMMUNICATION EVENTSTATUS

Generic Status (and Roles)Generic Status (and Roles)

TRANSACTION

# TRANSACTION ID

COMMUNICATIONEVENT

OTHERTRANSACTION

REQUEST

QUOTE

ORDER

SHIPMENT WORKEFFORT

INVOICEPAYMENT ACCOUNTING

TRANSACTION

RECEIVED

ENTEREDCONFIRMEDEXPECTED SHIPMENTAPPROVEDCANCELLED DATE

TRANSACTION STATUS

# TRANSACTION ID# STATUS TYPE ID# TRANSACTION STATUS ID* STATUS DATETIME

the descriptionfor

described bya statusfor

in thestate of

STATUS TYPE

# STATUS TYPE ID* DESCRIPTION

PARTY

# PARTY IDTRANSACTION ROLE

assignedto

assignedto

describedby

thedescriptionfor

involvedin

~~

~

# TRANSACTION ID# PARTY ID# ROLE TYPE ID# TRANSACTION ROLE SEQ ID* FROM DATEo THRU DATE

ROLE TYPE# ROLE TYPE ID* DESCRIPTION

involving

43

PARTY CONTACT INFORMATIONPARTY CONTACT INFORMATION

PhonePhoneFaxFaxCellCellPagerPagerEmailEmailAddressAddress

44

Party Contact MechanismsParty Contact Mechanisms

specified via

used by

the mechanism to contact

contacted via

~~

PARTY CONTACT MECHANISM

PARTY# PARTY ID

# PARTY ID# CONTACT MECHANISM ID* FROM DATEo THRU DATE

Phone,Fax,Cell,Pager

# CONTACT MECHANISM ID

CONTACT MECHANISM

TELECOM NUMBER* AREA CODE* CONTACT NUMBERo COUNTRY CODE

ELECTRONIC ADDRESS* ELECTRONIC ADDRESS STRING

EMAIL ADDRESS

WEB ADDRESS

IP ADDRESS

POSTAL ADDRESS* ADDRESS1o ADDRESS2o DIRECTIONS

* FROM DATEo THRU DATE

PARTY CONTACT MECHANISM PURPOSE

~for the purpose of

the purpose of

specifiedfor

used to specify

ROLE TYPE# ROLE TYPE ID* DESCRIPTION

45

COMMUNICATION EVENTSCOMMUNICATION EVENTS

Phone callsPhone calls

MeetingsMeetings

InquiriesInquiries

Follow up appointmentsFollow up appointments

EmailsEmails

Web site visitsWeb site visits

46

Communication EventCommunication Event

COMMUNICATION EVENT

# COMMUNICATION EVENT ID* DATETIME STARTED

o NOTE

o DATETIME ENDED

PHONECOMMUNICATION

FAXCOMMUNICATION

FACE TO FACECOMMUNICATION

EMAILCOMMUNICATION

LETTERCORRESPONDENCE

WEB VISITCOMMUNICATION

~

COMMUNICATIONEVENT ROLE

COMMUNICATIONEVENT ROLETYPE

PARTY

involving

of


describedby

thedescriptionfor

involvedin

for

~~

categorized by

the category for

COMMUNICATION EVENT PURPOSE

~

o DESCRIPTION

SUPPORT CALL INQUIRY

SALES FOLLOW UPCUSTOMER SERVICECALL CONFERENCE

SEMINARACTIVITY REQUEST

MEETING

# COMMUNICATION EVENT PURPOSE ID

in the context of

contacted via

* FROM DATEo THRU DATEo COMMENT

PARTY RELATIONSHIP

47

Product Product

ITEM# ITEM ID

SERIALIZED ITEM NON SERIALIZEDITEM* QUANTITY ON HAND

ITEM COMPOSITION

# PARENT INV ITEM ID# CHILD INV ITEM ID* ITEM COMPOSITION TYPE ID

madeup of used in

forin

thephysicaloccurrenceof

thedescriptionof

* SERIAL NUMBER

located at

thelocationfor

FACILITY

WAREHOUSE

PLANT

CUSTOMER FACILITY

# FACILITY ID* DESCRIPTION

~~

associated

# PRODUCT ID* NAMEo DESCRIPTION

SERVICE

GOOD

PRODUCT ASSOCIATION

# PRODUCT ID PARENT# PRODUCT ID CHILD* PRODUCT ASSOCIATION TYPE ID

from to

associatedwith

with

~~

PRODUCT

SOLUTION

# PART ID* NAME

for madeup of

PART COMPOSITION

in

used in

# PARENT PART ID# CHILD PART ID* PART ASSOCIATION TYPE ID

~~

offered using

provide

RAW MATERIAL

SUBASSEMBLY

FINISHED GOOD

PART

used to

48

Product Product FeaturesFeatures

available

PRODUCT FEATUREAPPLICABILITY

PRODUCT

# PRODUCT ID* NAMEo INTRODUCTION DATEo SALES DISCONTINUATION DATEo SUPPORT DISCONTINUATION DATEo COMMENT

used todefine

describedby

availablewith

for* FROM DATEo THRU DATE

~

~

GOOD

SERVICE

FEATURE TYPE# FEATURE TYPE ID* DESCRIPTION

NAME

COLOR

BRAND

SOFTWARE FEATURE

HARDWARE FEATURE

BILLING FEATURE

OTHER FEATURE

PRODUCT QUALITY

DIMENSION

SIZE

* NUMBER SPECIFIED

REQUIRED FEATURE

STANDARD FEATURE

OPTIONAL FEATURE

SELECTABLE FEATURE

dependent onselection of

~ ~afactorin

of

selectedin

PRODUCT FEATURE INTERACTION

FEATURE INTERACTION INCOMPATIBILITY

FEATURE INTERACTION DEPENDENCY

applicable withinthe context of

used to define

49

related to

associatedwith

Object Object Content Content ManagementManagement

OBJECT PURPOSE

PURPOSE TYPE

described by thedescription for

usedfor

for~

# PURPOSE TYPE ID* DESCRIPTION

~

OBJECT

# OBJECT ID* OBJECT NAMEo DESCRIPTIONo OBJECT CONTENTo LOCATION

IMAGE OBJECT

ELECTRONIC TEXT

o IMAGE

OTHER ELECTRONIC OBJECT

VERSION

# VERSION* DESCRIPTION

consistingof

arefinementofversioned via

of

PRODUCT OBJECT

PRODUCT

of

portrayedwith

for

for~

# PRODUCT ID* NAME

~

for ~

usedwithin

OBJECT USAGEused in

containing

# OBJECT USAGE ID* FROM DATEo THRU DATE

WEBCONTENTFRAME

# CONTENT FRAME ID* DESCRIPTION

PRESENTATIONFRAME

BROCHUREFRAME

CONTENT FRAME

50

Work EffortsWork Efforts

ProjectsProjects

ProgramsPrograms

Service deliveryService delivery

Maintenance/repair effortsMaintenance/repair efforts

IT effortsIT efforts

Work breakdown structure (WBS)Work breakdown structure (WBS)

ActivityActivity

IT effortIT effort

51

Common Modeling Common Modeling ApproachApproach

Opinions?Opinions?

How often?How often?

Consequences?Consequences?

PROGRAM

PROJECT

# PROGRAM ID* NAME* DESCRIPTION

# PROJECT ID* NAME* DESCRIPTION

ACTIVITY

# ACTIVITY ID* NAME* DESCRIPTION

TASK# TASK ID* NAME* DESCRIPTION

composed of

part of

composed of

composed of

part of

part of

composed of

partof

WORK EFFORT

# WORK EFFORT ID* NAME* DESCRIPTION

WORK TASK

# WORK TASK ID* NAME* DESCRIPTION

composed of

part of

CAMPAIGN

# CAMPAIGN ID* NAME* DESCRIPTION

ACTIVITY

# ACTIVITY ID* NAME* DESCRIPTION

composed of

part of

WORK ORDER

# WORK ORDER ID* NAME* DESCRIPTION

WORK ACTIVITY

# WORK ACTIVITY ID* NAME* DESCRIPTION

composed of

part of

52

Flexible Work Breakdown StructureFlexible Work Breakdown StructureWORK EFFORT ASSOCIATION

WORK EFFORT DEPENDENCY

associatedwith

associatedwith

from to

~ ~

WORK EFFORTCONCURRENCY

WORK EFFORTPRECEDENCY

WORK EFFORTBREAKDOWN


WORK EFFORT

MAINTENANCE

WORK FLOW RESEARCH

PROGRAM PROJECT

PHASE TASK ACTIVITY

# WORK EFFORT ID* NAME* DESCRIPTIONo SCHEDULED START DATEo SCHEDULED COMPLETION DATEo TOTAL DOLLARS ALLOWEDo TOTAL HOURS ALLOWEDo ESTIMATED HOURS

o ACTUAL HOURSo SPECIAL TERMS

o ACTUAL START DATETIMEo ACTUAL COMPLETION DATETIME

CAMPAIGN

SERVICE DELIVERY

~

PARTY

# PARTY IDWORK EFFORT ROLE

assignedto

describedby

thedescriptionfor

involved in

~

# WORK EFFORT ROLE ID* FROM DATEo THRU DATE

ROLE TYPE


involving

~

assigned

to

theuse of

usedin

WORK EFFORTINVENTORY USAGE

# WE INV ASSIGN IDo QUANTITY

INVENTORY ITEM

# INVENTORY ITEM IDO SERIAL NUMBERo QUANTITY ON HAND

~

~

using

for

FIXED ASSET

# FIXED ASSET ID* NAMEo DESCRIPTION

PROPERTY

VEHICLE

EQUIPMENT

OTHER FIXEDASSET

used toperform

assigned WORK EFFORT FIXEDASSET ASSIGNMENT ~

~

# WE FA ASSIGN ID* FROM DATEo THRU DATE

for

in the state of

the status for

WORK EFFASSET ASSIGNSTATUS TYPE

of

53

Other Universal ModelsOther Universal Models

- Web Information Models- People, organizations, contacts- Products, services- Orders, agreements- Shipments, delivery- Work efforts- Accounting and budgeting

- Sales Analysis - Human resources analysis- Financial Analysis

INDUSTRY DATA MODELSGENERIC DATA MODELS

DATA WAREHOUSE MODELS

- Manufacturing- Telecommunications- Health Care- Insurance- Financial Services- Professional Services- Travel

- Logistics Analysis- Operation Analysis- Industry Data Mart Designs

54

All Types of Re-Usable ModelsAll Types of Re-Usable Models

TM

e.g. DATA

ENTERPRISE ARCHITECTURE - A FRAMEWORK

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEMMODEL(LOGICAL)

TECHNOLOGYMODEL(PHYSICAL)

DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)

Sub-Contractor

FUNCTIONINGENTERPRISE

DATA FUNCTION NETWORK

e.g. Data Definition

Ent = FieldReln = Address

e.g. Physical Data Model

Ent = Segment/Table/etc.Reln = Pointer/Key/etc.

e.g. Logical Data Model

Ent = Data EntityReln = Data Relationship

e.g. Semantic Model

Ent = Business EntityReln = Business Relationship

List of Things Importantto the Business

ENTITY = Class ofBusiness Thing

List of Processes theBusiness Performs

Function = Class ofBusiness Process

e.g. "Application Architecture"

I/O = User ViewsProc .= Application Function

e.g. "System Design"

I/O = Screen/Device FormatsProc.= Computer Function

e.g. "Program"

I/O = Control BlockProc.= Language Stmt

e.g. FUNCTION

e.g. Business Process Model

Proc. = Business ProcessI/O = Business Resources

List of Locations in which the Business Operates

Node = Major BusinessLocation

e.g. Logistics Network

Node = Business LocationLink = Business Linkage

e.g. "Distributed System

Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics

e.g. "System Architecture"

Node = Hardware/SystemSoftware

Link = Line Specifications

e.g. "Network Architecture"

Node = AddressesLink = Protocols

e.g. NETWORK

Architecture"

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYCONSTRAINED

MODEL(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-

Contractor

FUNCTIONING

MOTIVATIONTIMEPEOPLE

e.g. Rule Specification

End = Sub-conditionMeans = Step

e.g. Rule Design

End = ConditionMeans = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals/Strat

Ends/Means=Major Bus. Goal/Critical Success Factor

List of Events Significant

Time = Major Business Event

e.g. Processing Structure

Cycle = Processing CycleTime = System Event

e.g. Control Structure

Cycle = Component Cycle

Time = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g. SCHEDULE

e.g. Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations

People = Major Organizations

e.g. Work Flow Model

People = Organization UnitWork = Work Product

e.g. Human Interface

People = RoleWork = Deliverable

e.g. Presentation Architecture

People = UserWork = Screen Format

e.g. Security Architecture

People = IdentityWork = Job

e.g. ORGANIZATION

Planner

Owner

to the BusinessImportant to the Business

What How Where Who When Why

Copyright - John A. Zachman, Zachman International

SCOPE(CONTEXTUAL)

Architecture

e.g. STRATEGY ENTERPRISE

e.g. Business Plan

TM

Zachman Institute for Framework Advancement

55

What can we do?What can we do?•AAssess ssess •AAsk sk •AAffectffect•AApplypply•AActct

56

AssessAssess the Environment the Environment•Goals?•Trust?•Approach?

57

AskAsk for What is Needed for What is Needed

•MoneyMoney

•FocusFocus

•RequirementsRequirements

58

AffectAffect Policies Policies

•Time

•Budget

•Requirements

•Integration “NEW”

•Time

•Budget

•Requirements

•Integration (NEW)

Project

Handbook

59

ApplyApply Re-usable Models Re-usable Models

Offers perspectivesOffers perspectives

Doesn’t replace analysisDoesn’t replace analysis

60

ActAct According to According to PrinciplesPrinciples

Common Common

GoalsGoals

TrustTrust

Re-UseRe-Use

Appreciate

Appreciate

Perspectives

Perspectives

61

Common Common

GoalsGoals

TrustTrust

Re-UseRe-Use

Appreciate

Appreciate

Perspectives

Perspectives

Re-applying Re-applying solutions solutions that have that have workedworked

Enabling Environment

Architecture, models, processes, technology

+

Keys to Successful integrationKeys to Successful integration

62

Remember…Remember…



CommitmentCommitment

ResourcesResources

ExpertiseExpertise

MethodologiesMethodologies

ToolsTools

TechnologyTechnology

63

QUESTIONS/COMMENTS?QUESTIONS/COMMENTS?

Len SilverstonLen Silverston

[email protected]@univdata.com

www.universaldatamodels.comwww.universaldatamodels.com

http://silverston.wiley.comhttp://silverston.wiley.com

mailto:[email protected]

http://www.universaldatamodels.com/

http://silverston.wiley.com/

Documents

1 By Len Silverston, Universal Data Models, LLC Universal Principles and Models Towards Integration