Universal Principles and Models Towards Integration By Len Silverston, Universal Data Models, LLC 1
What is Needed? Commitment? Technology? Tools? ? Connections between PEOPLE! Resources? Expertise? Methodologies? 2
What is Needed? Commitment? Resources? Technology? Tools? Connections Expertise? between PEOPLE! Methodologies? 3
Agenda • Define Integration • Principles • Universal data models • Actions 4
What is Integration “Combining into a whole” 5
Versus Disintegration “To separate into parts” 6
Integration as a Paradox TWO become ONE yet remain TWO 7
Integration as a Paradox MANY become ONE yet remain INDIVIDUAL 1: M 8
Disparate Databases • Databases Equal Budgets • Project Driven 9
Planting in Fertile Soil 10
Integration Principles mon Com s Goal t Trus ate s i rec tive App pec ers P e Us Re 11
PRINCIPLE #1 Integration Requires TRUST (IRT) rust T “Integrity” derived from “To Integrate” 12
Trust Financial Institution 13
Lack of Trust Insurance organization 14
Vulnerability A Key to Trust 15
Should we always trust? • Continued Mistakes? • Politics? • Who’s In Charge? 16
Principle #2 Keep Sight of the GOAL mon Com s Goal 17
Keep Big Picture in Sight Data Warehouse “If you have more than one data warehouse, then you don’t have any” Bill Inmon 18
Keep Sight of the Goal Information Technology (IT) Goals Business Goals 19
Keep Sight of the Goal Business Goals IT Business Goals/Systems 20
Obstacles • Overusing “My” • Blamestorming • “line of sight” 21
Sight of the Goal Not Attachment To It! 22
PRINCIPLE #3 APPRECIATE PERSPECTIVES Versus Being Right iate s rec tive App pec ers P 23
The“Right”Approach? “My way is the right way!” 24
What Is The Truth? Wholism = truth Truth is paradoxical 25
Who’s data is “right”? 26
Possibilities • Leadership • Adding to Perspectives • Including the Positive 27
PRINCIPLE #4 Learn from the PAST e Us Re 28
Learn From the Past Roles? Statuses Transactions Contact Info? Communications? Product? Work efforts? 29
Two type of Roles Declarative roles Contextual roles 30
Roles - Declarative PARTY ROLE WORKER # PARTY ID CONTRACTOR # ROLE TYPE ID * FROM DATE o THRU DATE CONTACT DISTRIBUTION CHANNEL AGENT DISTRIBUTOR EMPLOYEE CUSTOMER HOUSEHOLD REGULATORY AGENCY COMPETITOR FAMILY MEMBER ASSOCIATION BILL TO CUSTOMER REFERRER SHIP TO CUSTOMER PROSPECT END USER CUSTOMER for SUPPLIER SHAREHOLDER PARTNER WEB SITE VISITOR described by ~ ~the acting as ROLE TYPE PARTY # PARTY ID PERSON o CURRENT FIRST NAME o CURRENT LAST NAME ORGANIZATION description for # ROLE TYPE ID * DESCRIPTION o CURRENT ORGANIZATION NAME 31
Roles Contextual - Specific PROJECT ~ owned by for PROJECT ASSIGNMENT by SPONSOR ~ for PROJECT SPONSOR sponsoring by WORKER ~ is sponsored by ~ # PROJECT ID * NAME * DESCRIPTION o SCHEDULED START DATE o SCHEDULED END DATE o SCHEDULED COMPLETION DATE o TOTAL DOLLARS ALLOWED o TOTAL HOURS ALLOWED o ESTIMATED HOURS o ACTUAL START DATETIME o ACTUAL COMPLETION DATETIME o ACTUAL HOURS o SPECIAL TERMS owning managed by managing PROJECT MANAGER lead by leading PROJECT LEAD PROS/CONS? 32
Roles Contextual – Abstract assigned to ~ WORK EFFORT ROLE involved in within # PARTY ID ROLE TYPE described by ~ # WORK EFFORT ID # PARTY ID # ROLE TYPE ID # WORK EFFORT ROLE SEQ ID * FROM DATE o THRU DATE PARTY # ROLE TYPE ID * DESCRIPTION WORK EFFORT ROLE TYPE the description for ~ involving WORK EFFORT # WORK EFFORT ID * NAME * DESCRIPTION o SCHEDULED START DATE o SCHEDULED END DATE o SCHEDULED COMPLETION DATE o TOTAL DOLLARS ALLOWED o TOTAL HOURS ALLOWED o ESTIMATED HOURS o ACTUAL START DATETIME o ACTUAL COMPLETION DATETIME o ACTUAL HOURS o SPECIAL TERMS 33
Specific Versus Abstract Specific constructs Understandability Rules Enforcement Generic constructs Flexibility Show both? 34
Modeling Specific and Abstract PARTY ROLE # PARTY ID # ROLE TYPE ID * FROM DATE o THRU DATE PROJECT by SPONSOR ~ PROJECT SPONSOR sponsoring ~ by WORKER owning ~ ~ ~ PROJECT ASSIGNMENT ~ managing leading for within PROJECT LEAD described by acting as the description for PARTY ~ ROLE TYPE # PARTY ID assigned to # ROLE TYPE ID * DESCRIPTION involved in described by ~ ~ PROJECT ROLE # PROJECT ID # PARTY ID # ROLE TYPE ID # PROJECT ROLE ID * FROM DATE o THRU DATE ~ assigned to involving PROJECT MANAGER ~ ~ ~ is sponsored # PROJECT ID by * NAME * DESCRIPTION for o SCHEDULED START DATE o SCHEDULED END DATE owned by o SCHEDULED COMPLETION DATE for o TOTAL DOLLARS ALLOWED o TOTAL HOURS ALLOWED o ESTIMATED HOURS managed by o ACTUAL START DATETIME o ACTUAL COMPLETION DATETIME o ACTUAL HOURS o SPECIAL TERMS lead by the description for 35
PARTY ROLE # PARTY ID # ROLE TYPE ID * FROM DATE o THRU DATE ~ for acting as PARTY # PARTY ID Roles Versus Involvements? ~ the description for ROLE TYPE # ROLE TYPE ID * DESCRIPTION PARTY ROLE TYPE PERSON ORGANIZATION assigned to WORK EFFORT ROLE TYPE described by the description for WORK EFFORT ROLE # WORK EFFORT ID # PARTY ID # ROLE TYPE ID # WORK EFFORT ROLEID * FROM DATE o THRU DATE assigned to ~ involved in described by WORK EFFORT # WORK EFFORT ID involving 36
PARTY ROLE # PARTY ID # ROLE TYPE ID * FROM DATE o THRU DATE for ~ acting as PARTY # PARTY ID described by ~ the description for Roles Versus Involvements? ROLE TYPE # ROLE TYPE ID * DESCRIPTION PERSON INVOLVEMENT TYPE ORGANIZATION # INVOLVEMENT TYPE ID * DESCRIPTION assigned to WORK EFFORT INVOLVEMENT ~ described by # WORK EFFORT ID # PARTY ID # INVOLVEMENT TYPE ID # WORK EFFORT INVOLVEMENT ID * FROM DATE o THRU DATE WORK EFFORT INVOLVEMENT TYPE SHIPMENT INVOLVEMENT TYPE ~ involved in the description WORK EFFORT for assigned # WORK EFFORT ID to involving 37
Statuses As attributes As entities Generic entities 38
Statuses as attributes 39
Statuses as entities ORDER STATUS # ORDER ID # STATUS TYPE ID # ORDER STATUS ID * STATUS DATETIME a status for described by the description for STATUS TYPE in the state of ORDER # ORDER ID # STATUS TYPE ID * DESCRIPTION ORDER STATUS TYPE RECEIVED ENTERED CONFIRMED EXPECTED SHIPMENT APPROVED CANCELLED DATE 40
Roles and Statuses Occur for Many Types of Transactions PARTY COMMUNICATION EVENT ROLE COMMUNICATION EVENT STATUS ORDER ROLE SHIPMENT ROLE WORK EFFORT ROLE INVOICE ROLE ORDER SHIPMENT WORK EFFORT INVOICE ORDER STATUS SHIPMENT STATUS WORK EFFORT STATUS INVOICE STATUS PAYMENT ROLE PAYMENT GENERAL LEDGER TRANSACTION ROLE GENERAL LEDGER TRANSACTION PAYMENT STATUS GENERAL LEDGER TRANSACTION STATUS 41
Generic Status (and Roles) assigned to ~ TRANSACTION ROLE # PARTY ID TRANSACTION STATUS # TRANSACTION ID # STATUS TYPE ID # TRANSACTION STATUS ID * STATUS DATETIME ROLE TYPE # ROLE TYPE ID * DESCRIPTION ~ # TRANSACTION ID involved # PARTY ID in # ROLE TYPE ID # TRANSACTION ROLE SEQ ID * FROM DATE described o THRU DATE by PARTY assigned to ~ the description for described by a status for the description for STATUS TYPE in the state of involving TRANSACTION # TRANSACTION ID COMMUNICATION EVENT QUOTE INVOICE REQUEST SHIPMENT PAYMENT # STATUS TYPE ID * DESCRIPTION RECEIVED ENTERED CONFIRMED EXPECTED SHIPMENT APPROVED CANCELLED DATE ORDER WORK EFFORT ACCOUNTING TRANSACTION OTHER TRANSACTION 42
PARTY CONTACT INFORMATION Phone Fax Cell Pager Email Address 43
Party Contact Mechanisms PARTY CONTACT MECHANISM PURPOSE * FROM DATE o THRU DATE ~ for the purpose of PARTY CONTACT MECHANISM # PARTY ID # CONTACT MECHANISM ID * FROM DATE o THRU DATE the mechanism to contact CONTACT MECHANISM # CONTACT MECHANISM ID ~ specified via ~ the purpose of used by TELECOM NUMBER * AREA CODE * CONTACT NUMBER o COUNTRY CODE Phone, Fax, Cell, Pager ELECTRONIC ADDRESS * ELECTRONIC ADDRESS STRING EMAIL ADDRESS WEB ADDRESS IP ADDRESS contacted via PARTY # PARTY ID POSTAL ADDRESS * ADDRESS 1 o ADDRESS 2 o DIRECTIONS 44
COMMUNICATION EVENTS Phone calls Meetings Inquiries Follow up appointments Emails Web site visits 45
Communication Event COMMUNICATION EVENT PURPOSE CUSTOMER SERVICE CALL MEETING ACTIVITY REQUEST INQUIRY COMMUNICATION EVENT ROLE SALES FOLLOW UP * FROM DATE o THRU DATE CONFERENCE SEMINAR ~ SUPPORT CALL of ~ the category for categorized by COMMUNICATION EVENT # COMMUNICATION EVENT ID * DATETIME STARTED o DATETIME ENDED o NOTE described COMMUNICATION by EVENT ROLE the TYPE description for ~ # COMMUNICATION EVENT PURPOSE ID o DESCRIPTION ~ involved in PARTY involving PHONE COMMUNICATION FAX COMMUNICATION FACE TO FACE COMMUNICATION LETTER CORRESPONDENCE EMAIL COMMUNICATION WEB VISIT COMMUNICATION in the context of contacted via PARTY RELATIONSHIP * FROM DATE o THRU DATE o COMMENT 46
Product ITEM COMPOSITION # PARENT INV ITEM ID # CHILD INV ITEM ID * ITEM COMPOSITION TYPE ID for ~made in PART COMPOSITION ~ up of used in ITEM # ITEM ID SERIALIZED ITEM * SERIAL NUMBER located at the location for FACILITY # FACILITY ID * DESCRIPTION # PARENT PART ID # CHILD PART ID * PART ASSOCIATION TYPE ID the physical for made in occurrence up of of PART the description # PART ID of * NAME ~ NON SERIALIZED ITEM * QUANTITY ON HAND ~used in PLANT FINISHED GOOD # PRODUCT ID PARENT # PRODUCT ID CHILD * PRODUCT ASSOCIATION TYPE ID ~ from to used to provide ~ associated with RAW MATERIAL SUBASSEMBLY WAREHOUSE PRODUCT ASSOCIATION PRODUCT # PRODUCT ID * NAME o DESCRIPTION SERVICE GOOD offered using SOLUTION CUSTOMER FACILITY 47
Product Features PRODUCT FEATURE INTERACTION INCOMPATIBILITY FEATURE INTERACTION DEPENDENCY of applicable within the context of ~ a~ factor PRODUCT FEATURE in APPLICABILITY * FROM DATE o THRU DATE used to define ~ available for REQUIRED FEATURE available with STANDARD FEATURE OPTIONAL FEATURE SELECTABLE FEATURE selected dependent on in selection of FEATURE TYPE # FEATURE TYPE ID * DESCRIPTION ~ described by used to define PRODUCT # PRODUCT ID * NAME o INTRODUCTION DATE o SALES DISCONTINUATION DATE o SUPPORT DISCONTINUATION DATE o COMMENT GOOD SERVICE BRAND NAME PRODUCT QUALITY SOFTWARE FEATURE COLOR HARDWARE FEATURE DIMENSION * NUMBER SPECIFIED BILLING FEATURE SIZE OTHER FEATURE 48
CONTENT FRAME # CONTENT FRAME ID * DESCRIPTION OBJECT USAGE # OBJECT USAGE ID * FROM DATE o THRU DATE for ~ used in containing WEB CONTENT FRAME PRESENTATION FRAME OBJECT PURPOSE for described by ~ ~ the description for PURPOSE TYPE # PURPOSE TYPE ID * DESCRIPTION used within for related to OBJECT # OBJECT ID * OBJECT NAME o DESCRIPTION o OBJECT CONTENT o LOCATION BROCHURE FRAME Object Content Management consisting of associated with VERSION versioned via # VERSION * DESCRIPTION a refinement of of IMAGE OBJECT o IMAGE OTHER ELECTRONIC OBJECT for ~ ELECTRONIC TEXT of PRODUCT OBJECT for ~portrayed with PRODUCT # PRODUCT ID * NAME 49
Work Efforts Projects Programs Service delivery Maintenance/repair efforts IT efforts Work breakdown structure (WBS) Activity IT effort 50
Common Modeling Approach WORK EFFORT # WORK EFFORT ID * NAME * DESCRIPTION WORK TASK # WORK TASK ID * NAME * DESCRIPTION n Opinions? n How often? n Consequences? 51
Flexible Work Breakdown Structure WORK EFFORT ASSOCIATION * FROM DATE o THRU DATE WORK EFFORT DEPENDENCY ~ from ~ to WORK EFFORT ID NAME DESCRIPTION SCHEDULED START DATE SCHEDULED COMPLETION DATE TOTAL DOLLARS ALLOWED TOTAL HOURS ALLOWED ESTIMATED HOURS ACTUAL START DATETIME ACTUAL COMPLETION DATETIME ACTUAL HOURS SPECIAL TERMS assigned to # PARTY ID described by # WORK EFFORT ROLE ID * FROM DATE o THRU DATE ROLE TYPE the description for assigned for WORK EFFORT FIXED ASSET ASSIGNMENT # WE FA ASSIGN ID * FROM DATE o THRU DATE # FIXED ASSET ID * NAME o DESCRIPTION of used to perform OTHER FIXED ASSET in the state of PROJECT the status for CAMPAIGN WORK FLOW PROPERTY EQUIPMENT VEHICLE WORK EFF ASSET ASSIGN STATUS TYPE ACTIVITY RESEARCH SERVICE DELIVERY using for ~ MAINTENANCE TASK WORK EFFORT INVENTORY USAGE # WE INV ASSIGN ID o QUANTITY the use of ~ PHASE # ROLE TYPE ID * DESCRIPTION FIXED ASSET ~ PROGRAM involving PARTY involved in WORK EFFORT ROLE ~ # * * o o o o o assigned to ~ associated with WORK EFFORT CONCURRENCY ~ associated with WORK EFFORT PRECEDENCY ~ WORK EFFORT BREAKDOWN INVENTORY ITEM used in # INVENTORY ITEM ID O SERIAL NUMBER o QUANTITY ON HAND 52
Other Universal Models GENERIC DATA MODELS INDUSTRY DATA MODELS - Manufacturing - Telecommunications - Health Care - Insurance - Financial Services - Professional Services - Travel - Web Information Models - People, organizations, contacts - Products, services - Orders, agreements - Shipments, delivery - Work efforts - Accounting and budgeting DATA WAREHOUSE MODELS - Sales Analysis - Logistics Analysis - Human resources analysis - Operation Analysis - Financial Analysis - Industry Data Mart Designs 53
All Types of Re-Usable Models TM ENTERPRISE ARCHITECTURE - A FRAMEWORK DATA What FUNCTION How NETWORK Where PEOPLE Who When Why List of Things Important to the Business List of Processes the Business Performs List of Locations in which the Business Operates Planner ENTITY = Class of Business Thing Function = Class of Business Process Node = Major Business Location People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Critical Success Factor e. g. Semantic Model e. g. Business Process Model e. g. Logistics Network e. g. Work Flow Model e. g. Master Schedule e. g. Business Plan Ent = Business Entity Reln = Business Relationship Proc. = Business Process I/O = Business Resources Node = Business Location Link = Business Linkage People = Organization Unit Work = Work Product Time = Business Event Cycle = Business Cycle End = Business Objective Means = Business Strategy e. g. Logical Data Model e. g. "Application Architecture" e. g. "Distributed System Architecture" e. g. Human Interface Architecture e. g. Processing Structure Ent = Data Entity Reln = Data Relationship Proc. = Application Function I/O = User Views Node = I/S Function (Processor, Storage, etc) Link = Line Characteristics People = Role Work = Deliverable Time = System Event Cycle = Processing Cycle End = Structural Assertion Means =Action Assertion TECHNOLOGY MODEL (PHYSICAL) e. g. Physical Data Model e. g. "System Design" e. g. "System Architecture" e. g. Presentation Architecture e. g. Control Structure e. g. Rule Design Builder Ent = Segment/Table/etc. Reln = Pointer/Key/etc. Proc. = Computer Function I/O = Screen/Device Formats Node = Hardware/System Software Link = Line Specifications e. g. Data Definition e. g. "Program" e. g. "Network Architecture" Ent = Field Reln = Address Proc. = Language Stmt I/O = Control Block Node = Addresses Link = Protocols e. g. DATA e. g. FUNCTION e. g. NETWORK Owner SYSTEM MODEL (LOGICAL) Designer DETAILED REPRESENTATIONS (OUT-OFCONTEXT) Sub. Contractor FUNCTIONING ENTERPRISE TM Zachman Institute for Framework Advancement People = User Work = Screen Format e. g. Security Architecture List of Events Significant to the Business MOTIVATION SCOPE (CONTEXTUAL) ENTERPRISE MODEL (CONCEPTUAL) List of Organizations Important to the Business TIME Time = Execute Cycle = Component Cycle List of Business Goals/Strat e. g. , Business Rule Model End = Condition Means = Action e. g. ORGANIZATION e. g. Rule Specification Time = Interrupt Cycle = Machine Cycle People = Identity Work = Job e. g. Timing Definition End = Sub-condition Means = Step e. g. SCHEDULE e. g. STRATEGY SCOPE (CONTEXTUAL) Planner ENTERPRISE MODEL (CONCEPTUAL) Owner SYSTEM MODEL (LOGICAL) Designer TECHNOLOGY CONSTRAINED MODEL (PHYSICAL) Builder DETAILED REPRESENTATIONS (OUT-OF CONTEXT) Sub. Contractor FUNCTIONING ENTERPRISE Copyright - John A. Zachman, Zachman International 54
What can we do? • Assess • Ask • Affect • Apply • Act 55
Assess the Environment • Goals? • Trust? • Approach? 56
Ask for What is Needed • Money • Focus • Requirements 57
Affect Policies ct je ok ro bo P d an H e nts EW) W” im get e NE • T d “ em n (N Bu quir tio • a e • R tegr • In 58
Apply Re-usable Models Offers perspectives Doesn’t replace analysis 59
Act According to Principles mon Com s Goal t Trus ate s i rec tive App pec ers P e Us Re 60
Keys to Successful integration Architecture, models, processes, technology Re-applying solutions that have worked + Enabling Environment on Comm s Goal t Trus te cia es re v App pecti s Per se e-U R 61
Remember… Commitment Technology Tools Resources Connections between PEOPLE! Expertise Methodologies 62
QUESTIONS/COMMENTS? Len Silverston lsilverston@univdata. com www. universaldatamodels. com http: //silverston. wiley. com 63
Скачать презентацию Universal Principles and Models Towards Integration By Len
2eea5e20dd8748f1339771932d1248c8.ppt