i table of contents - ies.aust.com · enterprise architecture for integration: rapid delivery...

iEnterprise Architecture for Integration: Rapid Delivery Methods and Technologies i

Table of ContentsContents Page

BACK COVER.............................................................................................................2

Table of Figures ............................................................................................................xiii

Foreword to Third Edition ................................................................................................a

Preface to Third Edition.................................................................................................... i

Evolution from the Industrial Age to the Information Age ............................................ iv

Third Edition Changes............................................................................................... vii

Acknowledgements ...................................................................................................viii

Reading Strategies....................................................................................................viiiFor All Readers......................................................................................................viiiBusiness and IT Executives and Methodology Readers ......................................... ixTechnical Staff and Technology Readers .............................................................. xiiEnterprise Architecture Readers........................................................................... xiv

Additional Materials .................................................................................................. xivOnline Book Materials........................................................................................... xivFormat Conventions for the Book .......................................................................... xv

Free Use of Modeling Tools....................................................................................... xvUsing the Modeling Tools for Full-Capacity Projects.............................................xviiIn-house Courses Available for the Book..............................................................xviiAvailability of HD Video Courses based on the Book...........................................xviiiUniversity and Corporate Use of the Book ...........................................................xviiiStructured Chapters for Rapid Delivery................................................................xviiiCopyright and Trademark Acknowledgments ....................................................... xixOther Acknowledgments....................................................................................... xix

Chapter 1: Enterprise Architecture and Enterprise Engineering.......................................1

The Evolution of Enterprise Architecture......................................................................1

Zachman Framework V1.0 for Enterprise Architecture ................................................6The Difference Between Primitives and Composites................................................6Identifying Reusable, Priority Areas for Early Delivery ...........................................10

Zachman Framework V3.0 for Enterprise Architecture ..............................................11

Enterprise Engineering for Rapid Development.........................................................13

Enterprise Architecture for Enterprise Integration ......................................................21The Importance of Metadata..................................................................................21

Summary...................................................................................................................23

Part I: Enterprise Architecture for Managers..................................................................27

Chapter 2: Balanced Scorecard and Strategy Maps......................................................29

Basic Concepts of Balanced Scorecard.....................................................................31Translate the Strategy to Operational Terms .........................................................31Align the Organization to the Strategy ...................................................................31

ii Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies


Make Strategy Everyone’s Everyday Job...............................................................32Make Strategy a Continual Process.......................................................................34

Basic Concepts of Strategy Maps..............................................................................36

Examples of Balanced Scorecard and Strategy Maps ...............................................39Mobil North America Marketing and Refining.........................................................40Differentiation of the Financial Perspective at Mobil...............................................40The New Customer Perspective at Mobil ...............................................................41The Learning and Growth Perspective at Mobil .....................................................44

Steps for Balanced Scorecards and Strategy Maps...................................................45Methods for Strategies, Processes, and Systems..................................................45

Summary...................................................................................................................48

Chapter 3: Using Strategy Analysis to Define the Future ........................................................50

Strategy Analysis in Business Planning.....................................................................51Using Strategy Analysis.........................................................................................53The Quality of Planning Statements.......................................................................53

The Steps of Strategy Analysis..................................................................................56Step 1—Understand the Mission and Purpose ......................................................56Step 2—Identify the Major Business Areas............................................................58Step 3—Determine What Has to Be Achieved, in Terms of Goals .........................58Step 4—Identify Issues for Opportunities or Problems...........................................60Table 3.4 Assessment of Concerns and Issues .....................................................63Step 5—What Strategies Will Achieve or Resolve the Issues ................................64Step 6—Define Key Performance Indicators..........................................................67Step 7—Identify the Current Functions That Exist .................................................69Step 8—Allocate Implementation Responsibility ....................................................70Step 9—Define Job Role Responsibilities..............................................................72Table 3.5 CFO Job and Finance Department Tactical Plan ...................................73Benefits of Strategy Analysis .................................................................................75

Strategy Analysis for IT Project Specifications...........................................................75Step 1—Examine Business and Project Mission....................................................76Step 2—Project Goals and Performance Criteria...................................................76Step 3—Define Clear Business and Project Goals ................................................76Step 4—Identify Business Problems or Opportunities............................................77Step 5—Define Strategies for Problems or Opportunities ......................................77Step 6—Define Key Performance Indicators..........................................................77Step 7—Determine Business Functions.................................................................77Step 8—Identify Managers and Business Experts .................................................77Step 9—Schedule Joint Business and IT Participation...........................................78

Preparation for Strategy Analysis ..............................................................................78Business Planning Questionnaire ..........................................................................78Enterprise Mission and Purpose ............................................................................79Business Unit Mission and Purpose.......................................................................81Policies, Objectives, or Strategies..........................................................................82Processing of Questionnaire Responses ...............................................................82

Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies iii


Refined Policies, Objectives, or Strategies ............................................................83Markets, Products, Services, Channels, and SWOTs ............................................83

Questionnaire Templates ..........................................................................................83Business Planning Questionnaire Template ..........................................................84Strategic Modeling Questionnaire Template ..........................................................84

Summary...................................................................................................................84

Chapter 4: Governance Analysis Using Enterprise Architecture ....................................85

Responsibilities Imposed by Sarbanes-Oxley............................................................85Typical Internal Control Questions.........................................................................88Managing Internal Controls Using Enterprise Architecture.....................................89

Governance Analysis Framework for Sarbanes-Oxley...............................................90Developing a Governance Analysis Framework.....................................................95Methods and Tools for Governance Analysis.........................................................96Business Transformation Using Enterprise Architecture ......................................100

Step-by-Step Approach for Governance Analysis....................................................100Step 1—Establish Plan for Strategic Modeling Project.........................................101Step 2—Capture Business Planning Input as Catalyst.........................................101Step 3—Conduct Strategic Modeling Facilitated Session ....................................102Step 4—Carry Out Strategic Model Analysis .......................................................102Step 5—Derive Governance Analysis Documentation .........................................102Step 6—Review Matrices and Governance Implementation Plan ........................103Step 7—Manage Progressive Completion of GAF Matrices.................................103Step 8—Manage Implementation of Governance Systems..................................103

Summary.................................................................................................................103

Part II: Enterprise Architecture Methods......................................................................105

Chapter 5: Methods for Building Enterprise Architecture ......................................................107

Systems Development Evolution .............................................................................107Evolution of Software Engineering .......................................................................107Evolution of Information Engineering ...................................................................108Evolution of Object-Oriented Methods .................................................................109

Review of Enterprise Architecture ...........................................................................110Business Knowledge Needed ..............................................................................110Technology Decisions Using EA..........................................................................110Enterprise Architecture and Pace of Change .......................................................111

Government Methods for Enterprise Architecture ....................................................112Federal Enterprise Architecture Framework (FEAF) ..........................................112Relating FEAF to the Zachman Framework .........................................................118

DoD Architecture Frameworks.................................................................................121Defence Terminology...........................................................................................122Commercial and Government Terminology..........................................................122Defence Planning Terminology............................................................................122The Need for Defence Interoperability .................................................................123

iv Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies


Approach 1: Common Integrated Technology Environments ...............................126Approach 2: Integrated Technology and Information Environments .....................126Approach 3: Partially Integrated Technology and Information ..............................126Approach 4: Federated Information and Technology Environment.......................130Evolution of Enterprise Architecture in DoD.........................................................131Defence Architecture Framework.........................................................................134Relating Zachman Framework to the Defence Framework ..................................137Enterprise Architecture Project Results at Defence .............................................141

The Open Group Architecture Framework ...............................................................144Enterprise Engineering in FEAF, DoDAF, EAP, and TOGAF...............................145

Enterprise Architecture Project Experience .............................................................145Project Experience Summary ..............................................................................150

Strategies for Enterprise Architecture Implementation .............................................151Strategy A: Top-Down, Rigorous Implementation ................................................151Strategy B: Selective EA, Based on ROI..............................................................154Strategy C: Deliver in 3-Month Incremental Builds...............................................156

Recommended Approach for Enterprise Architecture..............................................160

Summary.................................................................................................................162

Chapter 6: Using Business-Driven Data Mapping for Integrated Data .........................163

Enterprise Architecture Build Context ......................................................................163Reading Strategy for This Chapter.......................................................................164

Data Modeling Conventions.....................................................................................165Business-Driven Enterprise Engineering Phases.................................................166Data Modeling Phase ..........................................................................................167Definition of Data Modeling..................................................................................167A Simple Data Map..............................................................................................168Definition of a Data Entity ....................................................................................169Definition of a Data Attribute ................................................................................169Definition of Data Associations ............................................................................170Business-Driven Association Degree...................................................................170IT-Driven Association Degree ..............................................................................171Business-Driven Association Nature....................................................................172IT-Driven Association Nature ...............................................................................173Business-Driven Time-Dependent Nature............................................................173Time-Dependent Nature in IT-Driven Data Mapping ............................................174Association Degree and Nature Summary ...........................................................175Case Study Problem 1.........................................................................................175

Data Entity Types ....................................................................................................175Principal Entity.....................................................................................................176Type Entity ..........................................................................................................177Secondary Entity .................................................................................................180Exclusive Type Entity...........................................................................................181Inclusive Type Entity............................................................................................182Intersecting Entity ................................................................................................183

Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies v


Role Entity ...........................................................................................................186Case Study Problem 2.........................................................................................188Recognizing a Structure Entity.............................................................................188Structure Entity ....................................................................................................189Structure Entity Represents a Table ....................................................................192Summary of Entity Types.....................................................................................194Case Study Problem 3.........................................................................................195

Data Attribute Types................................................................................................195Data Attributes (Keys)..........................................................................................195Primary Key, with Examples ................................................................................195Foreign Key, with Examples ................................................................................197Key Attribute Alias ...............................................................................................199Compound Key, with Examples ...........................................................................200Data Attributes (Non-Keys) ..................................................................................201Selection Attributes (Secondary Keys).................................................................202Elemental and Group Attributes...........................................................................203Repeating Group Attributes .................................................................................203Derived Attributes ................................................................................................205Optional Attributes ...............................................................................................207

Entity List Conventions ............................................................................................208Entity List for Data Model Examples ....................................................................209Data Map for Data Model Examples ....................................................................210Case Study Problem 4.........................................................................................210

More about Entities and Attributes...........................................................................210Entity Purpose Descriptions.................................................................................211Good Purpose Descriptions .................................................................................212Attribute Purpose Descriptions ............................................................................213Association Purpose Descriptions........................................................................214Business Process Purpose Descriptions..............................................................214Entity Model View Authority .................................................................................215Attribute Data Domain .........................................................................................216Attribute Edit Rules..............................................................................................217Edit Rule Example ...............................................................................................217Attribute Model View Authority.............................................................................218Summary of Attribute Characteristics...................................................................219Case Study Problem 5.........................................................................................220Case Study Problem 6.........................................................................................220

Data Mapping Summary..........................................................................................221

Chapter 7: Strategic Modeling for Rapid Delivery of Enterprise Architecture ...............223

Enterprise Architecture Incremental Build Context...................................................223Reading Strategy for this Chapter........................................................................224

Developing a Strategic Model..................................................................................225Preparing for Strategic Modeling .........................................................................225Strategy for the Facilitated Modeling Session ......................................................226

vi Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies


Starting the Facilitated Modeling Session ............................................................2271. Project Ownership Policy .................................................................................2272. Project Management Policy .............................................................................2323. Project Authorization Policy .............................................................................232Continuing the Facilitated Modeling Session .......................................................233Case Study Problems for Strategic Modeling.......................................................233

Box 7.1: Strategic Modeling Statements..................................................................234Case Study Example 7.1 Policies, Objectives or Strategies.................................234Case Study Example 7.1 Tasks...........................................................................235

Progressive Evolution of Strategic Model ................................................................237Statement 4: Project Teams Policy ......................................................................237Statement 5: Project Activities Policy...................................................................238Statement 6: Project Skills Policy.........................................................................239Statement 7: Project Resources Policy................................................................240Statement 8: Related Budgets Policy...................................................................242Statement 9: Related Projects Policy...................................................................243Strategic Model Sample Solution.........................................................................244

Identifying Business Activities from a Data Map ......................................................245Potential Business Activities ................................................................................247

Deriving Project Plans for Rapid EA Delivery ..........................................................248Benefits of Entity Dependency Analysis...............................................................251Entity Dependency Analysis Rules ......................................................................253Entity Dependency Rule Exercises ......................................................................256Deriving Project Plans and Project Maps .............................................................258Entity Dependency Analysis Steps ......................................................................258

Case Study Entity Dependency Problems ...............................................................265

Project Maps are Do-It-Yourself (DIY) Construction Kits..........................................265Using Project Management Packages .................................................................266

Real-Life Strategic Modeling Projects......................................................................269Large Government Department Project Example.................................................269Regional Bank Project Example ..........................................................................271Using the Strategic Model for Communication .....................................................276Need for Better Coordination throughout the Bank ..............................................278Medium Government Department Project Example .............................................279Large Government Department Project Example.................................................281Small Company Project .......................................................................................283

Summary of Strategic Modeling...............................................................................284

Chapter 8: Strategic Alignment, Activity & Workflow Modeling, and Business Rules ...285


Step 6 – Define Strategic Alignment Matrices..........................................................288Relationship between Business Plans, Data and Activities ..................................288Aligning Business Plans to Organization (Col 6–Col 4)........................................289Case Study Problems for Strategic Alignment Matrices .......................................289

Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies vii


Step 7 – Activity Modeling Concepts .......................................................................290Differences between Functions, Activities and Processes ...................................290The Role of IDEF0...............................................................................................292IDEF0 Model Components...................................................................................294Context Diagram..................................................................................................295Reading a Context Diagram.................................................................................296ICOM Input Arrow................................................................................................297ICOM Control Arrow ............................................................................................298ICOM Output Arrow .............................................................................................298ICOM Mechanism Arrow......................................................................................298Activity Maps as Decomposition Diagrams ..........................................................299Activity Map Feedback Loops ..............................................................................300Node Diagram or Activity Hierarchy .....................................................................300

Step 7 – Activity-Based Costing (ABC)....................................................................301Comparison to Traditional Financial Accounting ..................................................302The Steps of Activity-Based Costing....................................................................303Forming Activity Alternatives................................................................................306Monitoring the Benefits ........................................................................................307

Step 8 – Workflow Modeling ....................................................................................307Using Project Maps for Workflow Modeling..........................................................308Derivation of Activity Models from Project Maps ..................................................310Derivation of a Workflow Model from Activity Maps .............................................311Derivation of Activity Model from Entity Dependency Cluster...............................312

Step 9 – Business Rules for Workflow Modeling......................................................314Mapping BRS Proteus to Enterprise Architecture ................................................315

Definition of Business Rules using BRS Proteus .....................................................318

Summary of Strategic Alignment, Activity and Workflow Modeling, and Business Rules................................................................................................................................320

Chapter 9: Using Business Normalization for Future Business Needs.........................323


Introduction to Normalization ...................................................................................326Business Normalization .......................................................................................326Resolution of Forms Design Problems.................................................................327Resolving Database Design Problems.................................................................331Tables Related by Common Keys........................................................................332Benefits of Business Normalization......................................................................335Normalized Tables and Rules..............................................................................335Identifying Data as a Business Resource.............................................................336Case Study Problems 1 to 6 ................................................................................337

First Business Normal Form (1BNF)........................................................................337Example of First Business Normal Form..............................................................339Case Study Problem 7: Normalization Preparation and 1BNF .............................339

viii Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies

Table of ContentsContents PageSecond Business Normal Form (2BNF)...................................................................340Example of Second Business Normal Form.........................................................340Second Business Normal Form Data Map ...........................................................341Alternative Normalization Approaches .................................................................342Identification of Homonyms and Synonyms .........................................................345Case Study Problem 9: 2BNF..............................................................................346

Third Business Normal Form (3BNF).......................................................................346Example of Third Business Normal Form.............................................................347Third Business Normal Form Data Map...............................................................347Case Study Problem 10: 3BNF............................................................................348

Identifying Current and Future Business Needs.......................................................348Normalization Crosscheck of Employee...............................................................349What About Future Salary Needs? ......................................................................352Accommodating Employee Job Salary ................................................................353Result of Business Normalization Crosscheck.....................................................354Summary for Third Business Normal Form..........................................................354Case Study Problem 11: Normalization Crosscheck............................................355

Fourth Business Normal Form (4BNF) ....................................................................355Example of Fourth Business Normal Form ..........................................................356Example of a 4BNF Data Map .............................................................................357Case Study Problem 12: 4BNF............................................................................357

Capturing Expert Business Knowledge....................................................................358

Fifth Business Normal Form (5BNF)........................................................................358Example of Fifth Business Normal Form..............................................................359Examples of 5BNF Entities: Employee Structure .................................................360Example of 5BNF: Product Structure ...................................................................368Using Product Structure for “Where-Used” ..........................................................373Example of 5BNF: Organization Relationships ....................................................3745BNF Example: Organization Role Structure.......................................................3765BNF Example: Organization Structure ...............................................................3795BNF Expert Knowledge: “Market Intelligence”....................................................380Case Study Problem 13: 5BNF............................................................................383

Summary of Business Normalization .......................................................................383Benefits of Business Normalization......................................................................384

Chapter 10: Using Process Models to Define Business Processes .............................387

Enterprise Architecture Incremental Build Context...................................................387Reading Strategy for This Chapter.......................................................................390

Initial Menu Structure from a Data Model.................................................................391Simple Menu Structure Design for Person Skill....................................................391Tabbed Menu Structure Design ...........................................................................393

Preliminary Screen Designs from a Data Model ......................................................394Typical Screen Design for a Single Entity ............................................................394Typical Screen Design for One to Many Associations..........................................395

Data Base and Transaction Performance................................................................396

Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies ix


Database Capacity Planning from a Logical Data Model .....................................397Logical Transaction Performance Analysis ..........................................................400Physical Transaction Performance – Not Optimized ............................................402Physical Transaction Performance – Data Base Clustering .................................404Distributed Data Base Design – Not Optimized....................................................405Distributed Transaction Performance – Network Impact ......................................407Distributed Transaction Performance – Data Replication.....................................407

Prototyping from a Data Model ................................................................................409Menu Design and Screen Design for Order Entry Data Map................................410Tables and Relationships in Microsoft Access .....................................................413Reusing Screen and Menu Designs.....................................................................414

Process Modeling Using BPMN...............................................................................417Differences Between Functions, Activities and Processes ...................................419Basic Concepts of BPMN ....................................................................................419

Menu Design, Screen Design and Process Modeling Summary................................................425Part III: Enterprise Integration Technologies .......................................................................427

Chapter 11: Enterprise Application Integration Concepts ............................................429

Technologies for Enterprise Integration ...................................................................429Basic XML Concepts ...........................................................................................430Business Documents...........................................................................................430Electronic XML Documents..................................................................................431The Need for XML Transformation.......................................................................432

B2B Cost Effectiveness Business Drivers................................................................435The Growth of Trading Communities ...................................................................436Connecting Enterprises Together ........................................................................437Finding Buyers and Suppliers ..............................................................................443

XML Messaging and Repository Standards.............................................................444Industry Markup Vocabularies .............................................................................445RosettaNet ..........................................................................................................446

ebXML.....................................................................................................................450ebXML Integration Server Concepts ....................................................................453Redundant Data Integration using EAI.................................................................457

EAI Vendors and Products ......................................................................................460

Summary of Enterprise Application Integration........................................................460

Chapter 12 : Enterprise Portal Technologies for Integration ........................................463

The Evolution of Enterprise Portals .........................................................................463Definition of an Enterprise Portal .........................................................................463Structured and Unstructured Data Resources......................................................464Basic Architecture of an Enterprise Portal............................................................464Integration using an Enterprise Portal..................................................................467

Enterprise Portal Case Studies................................................................................469

x Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies


Herman Miller B2B e-Business Portal ..................................................................469Ford Motor Company B2E Internal Corporate Portal............................................472General Motors Corporation Employee Portal......................................................475

Enterprise Portal Product Categories ......................................................................478Collaborative Portal Products ..............................................................................479Business Intelligence Portal Products..................................................................479Integration Portal Products ..................................................................................479

Enterprise Portal Product Descriptions ....................................................................480

Summary of Enterprise Portal Technologies for Integration.....................................480Summary of Enterprise Portal Characteristics......................................................480

Chapter 13: Web Services for Real-Time Integration...................................................483

Introduction to Web Services...................................................................................483Concepts and Components of Web Services.......................................................484

Intranet and Internet Web Services for Integration...................................................485Intranet Web Services Integration Example .........................................................486Internet Web Services Integration Example .........................................................487

XML Standards for Web Services............................................................................489SOAP Definition...................................................................................................491WSDL Definition ..................................................................................................493UDDI Definition....................................................................................................494

Web Services Evolution...........................................................................................497Phase 1 Evolution: 1999-2001.............................................................................497Phase 2 Evolution: 2002-2004.............................................................................497Phase 3 Evolution: 2005 and Beyond ..................................................................500

Challenges in Phase 3 Evolution .............................................................................500The Importance of Message Semantics: Metadata ..............................................500Revenue Models for Web Services......................................................................501

Web Services Vendors ............................................................................................502

Summary of Web Services ......................................................................................503

Chapter 14: Service-Oriented Architecture for Integration ...........................................505

The Importance of Service–Oriented Architecture ...................................................505Manual Integration Approaches ...........................................................................506Coordinated Error Management ..........................................................................508

What are Service-Oriented and Event-Driven Architectures ....................................512Business Process Execution Language (BPEL)...................................................513Web Services Choreography Interface (WSCI)....................................................516Business Process Modeling Language (BPML) ...................................................519Simple BPML Activity Types ................................................................................521Complex BPML Activity Types.............................................................................521ebXML Business Process Specification Schema (BPSS) ....................................524Business Process Modeling Notation (BPMN) .....................................................527

Business Process Management Software Vendors .................................................529

Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies xi


Summary of Service-Oriented Architecture..............................................................531

Chapter 15: Managing and Delivering Enterprise Architecture ....................................535

Virtualization and On Demand.................................................................................535Virtualization Concepts ........................................................................................536On Demand Concepts .........................................................................................539

The Evolution to Cloud Computing ..........................................................................541Web 2.0 and RIA Products ..................................................................................542Cloud Computing and SaaS Products .................................................................542

The Costs of Integration ..........................................................................................542

The Role of Modeling Tools.....................................................................................545

Modeling Tool Products and Directions ...................................................................546Modeling Tool Product Descriptions ....................................................................547

Summary of Key Enterprise Architecture Principles.................................................547Evolution to the 21st Century Enterprise...............................................................547Architects of the Enterprise..................................................................................547Using the Zachman Framework for Reusability....................................................548Systems Development Directions in the 21st Century...........................................548Using Business Plans to Define the Future..........................................................549Enterprise Architecture in Government and Defense ...........................................549Development of Integrated Data Models..............................................................550Strategic Alignment using the Zachman Framework............................................551Using Activity Modeling for Reusable Activities....................................................551Workflow Modeling and Business Rules ..............................................................551Menu Structure Design and Screen Design .........................................................552Process Modeling to Define Reusable Processes................................................552Technologies and Products for EAI......................................................................552Enterprise Portal Technologies and Products ......................................................553Technologies and Products for Web Services .....................................................553Technologies and Products for SOA and BPM ....................................................554Achieving Business and Technology Integration..................................................555

Future Directions in Enterprise Architecture ............................................................556Enterprise Architecture Skills-Transfer.................................................................556Methodology Directions .......................................................................................557Technology Directions .........................................................................................557Standards for Enterprise Architecture ..................................................................558

Appendix 1: What is Wrong with Information Engineering and How to Fix it? ..............559

Introduction .............................................................................................................559

Problems of Systems Development.........................................................................559Some Solutions to these Problems......................................................................560My Early Exposure to the Problems.....................................................................562

The History of Information Engineering ....................................................................563Table A1: Evolution of Information Engineering....................................................564

xii Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies

Table of ContentsContents PageSystems Development Breakthroughs.....................................................................566

Comparing the Variants of Information Engineering .................................................568Table A2: Stages of Information Engineering.......................................................569Enterprise Architecture ........................................................................................572Using Information Engineering with Enterprise Architecture.................................572

Summary.................................................................................................................573

Next Steps...............................................................................................................573

xiii Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies

Table of Figures

Contents Page

Figure 1.1: The owner, designer, and builder are interested in different diagrams orrepresentations from their perspectives in the design and construction of buildings,airplanes, and enterprise systems................................................................................................... 2Figure 1.2: Different questions (or abstractions) also need to be considered in thedesign and construction of buildings, airplanes, and enterprise systems. ...................................... 3Figure 1.3: Different model representations exist in each of 15 cells to address theperspective of each row and the focus of each column. ................................................................. 4Figure 1.4: The complete Zachman framework for enterprise architecture is basedon a further three columns, for a total of six columns and five rows—making up 30 cells.Each cell may contain various types of models, as illustrated in this figure. .................................... 5Figure 1.5: V1.0 of the Zachman Framework for Enterprise Architecture (Courtesyof John A. Zachman.) ........................................................................................................................ 7Figure 1.6: An enterprise-wide approach is shown as a horizontal band across the fullwidth of each cell. A high-level view of the models within each cell is shown as anarrow “slice” for the enterprise-wide band at the top 10% of each cell. ........................................ 8Figure 1.7: Priority areas for early delivery are identified as vertical “slivers” within eachcell, which extend to the depth of the cell. Resources are allocated to these priority areas(slivers) so they can be defined, built, and delivered first. ............................................................... 9Figure 1.8: The Planner and Owner rows (rows 1 and 2) are used for ReusabilityDefinition. The Owner row is most effective in its ability to identify enterprise-widereusability opportunities................................................................................................................. 11Figure 1.9: Zachman Framework V3.0 for Enterprise Architecture (Courtesy ofJohn A. Zachman.).......................................................................................................................... 13Figure 1.10: Horizontal slices and vertical slivers for V3.0 of the ZachmanFramework (from Figure 1.7)......................................................................................................... 14Figure 1.11: Enterprise engineering supports all rows of the Zachman framework,with rapid implementation of priority enterprise architecture areas............................................... 17Figure 2.1: Strategy analysis addresses Zachman framework, column 6, Scopeand Business (Rows 1 and 2)........................................................................................................ 30Figure 2.2: Mobil’s Balanced Scorecard (From: [], Figure 2-5, p. 42. © 2001 HarvardBusiness School Press. Reprinted with permission.)..................................................................... 32Figure 2.3: Mobil’s strategy map, part 1, reading from the top down. (After: [31],Figure 2-6, p. 42.) ........................................................................................................................... 33Figure 2.4: Mobil’s strategy map, part 2, reading from the top down. (After: [],Figure 2-6, p. 43)............................................................................................................................. 34Figure 2.5: Strategy maps show the dependent components of a strategic plan.This shows a private-sector organization example on the left and a public sectoror nonprofit organization example on the right. (From: [], Figure 1-2, p. 8. © 2004Harvard Business School Press. Reprinted with permission.)............................................................. 37Figure 2.6: Strategy maps show value creation (From: [], Figure 1-3, p. 11. © 2004Harvard Business School Press. Reprinted with permission.)....................................................... 39Figure 2.7: Mobil’s strategy map—the differentiated financial perspective. (From:Figure 2-1, p. 31. © 2001 Harvard Business School Press. Reprinted with permission.)............. 41Figure 2.8: Mobil’s strategy map—the customer perspective. (From: [11], Figure 2-3,p. 36. © 2001 Harvard Business School Press. Reprinted with permission.) ................................ 43Figure 2.9: Mobil’s strategy map—the internal process perspective. (From:

xiv Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies

Table of FiguresFigure Page

Figure 2-4, p. 39. © 2001 Harvard Business School Press. Reprinted with permission.) ............. 44Figure 2.10: Mobil’s strategy map—the learning and growth perspective. (From:Figure 2-5, p. 41. © 2001 Harvard Business School Press. Reprinted with permission.) ............. 46Figure 3.1: Strategy analysis addresses the Zachman frameworkWhy column for theScope and Business rows (Planner [C6R1] and Owner rows [C6R2])............................................. 51Figure 3.2: The hierarchical nature of business plans................................................................... 52Figure 3.3: Relationship between planning statements. ........................................................... 55Figure 3.4: A stable strategic plan takes its foundation for the mission and vision fromthe environment. Strategies and tactics address issues, to achieve goals and objectiveswithin the boundaries defined by policies. ...................................................................................... 66Figure 3.5: The steps of strategy analysis. ................................................................................. 68Figure 3.6: Business function–strategy matrix. Arrows identify new functions notcurrently supported by XYZ Corporation. ....................................................................................... 71Figure 3.7: Job role responsibilities can be read down each function column.............................. 73Figure 4.1: Governance analysis addresses the Why column for the Scope andBusiness rows (Planner [C6R1] and Owner rows [C6R2]) of the Zachman framework................... 86Figure 4.2: Multiple-location testing considerations for auditors in relation to internalcontrol reporting for Sarbanes-Oxley. (Source: File 2003_0822_Sarbanes-Oxley_Omnibus_Final_rev.pdf in 2003_0822_pcaob.zip as discussed in [3]. [Reprinted with Permission]).............. 87Figure 4.3: The Zachman framework for enterprise architecture can be used to createa governance analysis framework as an internal control reporting approach to complywith Section 404 of the Sarbanes-Oxley Act of 2002...................................................................... 89Figure 4.4: Typical GAF matrix that relates why (as rows for planning statements) andwho (as columns for business units). ............................................................................................. 91Figure 4.5: Typical GAF matrix that relates how (as rows for business activities) andwhy (as columns for planning statements)..................................................................................... 92Figure 4.6: Typical GAF matrix that relates why (as rows for planning statements) andwhat (as columns for data objects). ............................................................................................... 93Figure 4.7: Typical GAF matrix that relates how (as rows for business activities) andwhat (as columns for data). ........................................................................................................... 94Figure 4.8: Project plan for governance analysis strategic modeling projects. ........................... 101Figure 5.1: Layers of Spewak enterprise architecture planning. (From: [97]. © 1992S. Spewak. Reprinted with permission.) ...................................................................................... 114Figure 5.2: Five basic reference models of the FEAF and their relationship to each other.(From: [97]. ©2004 FEA Program Management Office. Reprinted with permission.) ................. 116Figure 5.3: FEA reference model integration. (From: [97]. © 1992 FEA ProgramManagement Office. Reprinted with permission.) ........................................................................ 117Figure 5.4: Broad mapping of Spewak EAP and FEAF to the Zachman framework.(From: © 2005 Robert Weisman, CGI. Reprinted with permission.)............................................ 119Figure 5.5: The Enterprise Architecture Method (EAM), the copyright of which is aCGI extension to Spewak’s EAP. (From: [100]. © 2005 CGI. Reprinted with permission.).......... 120Figure 5.6: Joint and combined defense interoperability is needed. (From:© 2005 Robert Weisman, CGI. Reprinted with permission.) ........................................................ 122Figure 5.7: Defense information infrastructure. (From: [104]. © 2004 Robert Weisman,CGI. Reprinted with permission.) ................................................................................................. 127Figure 5.8: U.S. DISA C4I FTW implementation plan for a global command and control

Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies xv


system. (From: [104]. © 2004 Robert Weisman, CGI. Reprinted with permission.) .................... 128Figure 5.9: Some DoD Common Operating Environment Trends (From: [104].© 2004 Robert Weisman, CGI. Reprinted with permission.) ....................................................... 129Figure 5.10: U.K. Ministry of Defence COE. (From: [104]. © 2004 Robert Weisman,CGI. Reprinted with permission.) .................................................................................................. 130Figure 5.11: Defence Drill-Down and Roll-Up Functionalities in this CanadianArmy Example (Source: Canadian DND) .................................................................................... 131Figure 5.12: The Clinger-Cohen Act (discussed earlier for FEAF) was also a startingpoint for defense enterprise architecture. (From: [104]. © U.S. Air Mobility Command.Reprinted with permission.) ......................................................................................................... 133Figure 5.13: DoD operational/systems/technical architecture. (Adapted from DoDAF.)................. 135Figure 5.14: Key analysis relationships in C4ISR. (From: [110]. © 2004 U.S. AirMobility Command. Reprinted with permission.) .......................................................................... 136Figure 5.15: Key planning relationships in C4ISR. (From: [110]. © 2004 U.S.Air Mobility Command. Reprinted with permission.).................................................................... 137Figure 5.16: The DoDAF framework products (“as is” baseline strategy). See Table 5.1for the abbreviation references in this figure. (From: [112]. © 2004 U.S. Air MobilityCommand. Reprinted with permission.) ........................................................................................ 138Figure 5.17: C4ISR and DoDAF Product Deliverables, Mapped Broadly to the ZachmanFramework (Source: US Air Mobility Command) ........................................................................ 141Figure 5.18: Strategy A—top-down, rigorous detail. (From: © 2002 ZachmanInternational. Reprinted with permission.) .................................................................................... 152Figure 5.19: Enterprise architecture “analysis paralysis.” (From: []. © 2004 CGI.Reprinted with permission.) .......................................................................................................... 154Figure 5.20: Strategy B—selective EA, based on ROI business case. (Source: © 2002. JohnZachman and Zachman International. Reprinted with permission.)............................................ 156Figure 5.21: Incremental implementation of enterprise architecture. (From: [127].© 2004 Robert Weisman, CGI. Reprinted with permission.) ........................................................ 158Figure 5.22: Strategy C—Deliver enterprise architecture progressively in 3-monthincremental builds. (From: [126]. © 2004 Zachman International. Reprinted with permission.) .. 158Figure 5.23: Broad enterprise engineering implementation sequence usedthroughout the book..................................................................................................................... 161Figure 6.1: Data mapping addresses Zachman framework What column[C1R1–C1R3]. ............................................................................................................................. 164Figure 6.2: Steps 1 through 5 for rapid implementation of enterprise architecture. .................... 165Figure 6.3: Data modeling phase in enterprise engineering. ...................................................... 166Figure 6.4: Example of a simple data map.................................................................................. 168Figure 6.5: A data association in a data map. ............................................................................. 171Figure 6.6: Business-driven association degree of one, and also one or many. ........................ 171Figure 6.7: IT-driven association degree of one and one or many.............................................. 172Figure 6.8: business-driven association nature of mandatory and optional. ............................... 173Figure 6.9: IT-driven association nature of mandatory and optional. .......................................... 174Figure 6.10: Business-driven association nature of mandatory becoming optional. ................... 174Figure 6.11: Business-driven data mapping notation summary. ................................................. 176Figure 6.12: A principal entity contains common shared data throughoutan enterprise................................................................................................................................ 178

xvi Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies


Figure 6.13: A Type Entity indicates that other entities may also exist ....................................... 179Figure 6.14: A type entity data map and entity list. ..................................................................... 180Figure 6.15: A secondary entity data map and entity list. ........................................................... 181Figure 6.16: An Exclusive Type Entity.......................................................................................... 182Figure 6.17: An Inclusive Type Entity .......................................................................................... 182Figure 6.18: The importance of many-to-many associations. ..................................................... 183Figure 6.19: Decomposing a many-to-many association. ........................................................... 184Figure 6.20: Steps in Decomposing a Many to Many Association .............................................. 185Figure 6.21: Data Map and Entity List of an Intersecting Entity .................................................. 186Figure 6.22: Data map and entity list of a role entity. .................................................................. 187Figure 6.23: Resolving recursive associations, and many-to-many associationsbetween secondary entities. ........................................................................................................ 190Figure 6.24: Recursive associations and many-to-many associations betweensecondary entities are resolved by using a structure entity. ....................................................... 190Figure 6.25: Entity list alternatives used by structure entities. .................................................... 191Figure 6.26: Summary of entity types, with examples................................................................. 194Figure 6.27: Employee Id# is an underlined, Primary Key .......................................................... 196Figure 6.28: employee number# is a Common Primary Key ...................................................... 197Figure 6.29: Job Title# is a Common Primary and Foreign Key ................................................. 198Figure 6.30: Employee type number# is a Common Primary and Foreign Key.......................... 198Figure 6.31: Current Job# is a Foreign Key Alias for Job Title #................................................. 200Figure 6.32: job title and job number are both unique Candidate Keys ...................................... 200Figure 6.33: Example of Compound Primary Keys ..................................................................... 200Figure 6.34: Another Example of Compound Primary Keys ....................................................... 201Figure 6.35: Examples of Selection Attributes (Secondary Keys)............................................... 202Figure 6.36: Example of Elemental Non-Key Attributes .............................................................. 203Figure 6.37: Example of Group and Elemental Non-Key Attributes............................................ 204Figure 6.38: Example of Repeating Group Attributes.................................................................. 204Figure 6.39: Another Example of Repeating Group Attributes.................................................... 205Figure 6.40: Example of a Derived Attribute ............................................................................... 206Figure 6.41: Another Example of a Derived Attribute.................................................................. 206Figure 6.42: Example of Optional Attributes (shown by superscript o) ........................................ 207Figure 6.43: Data Map of Entities for Entity List .......................................................................... 211Figure 6.44: Data Map Showing the Concept of Model Views.................................................... 216Figure 6.45: Attribute Edit Rules.................................................................................................. 218Figure 6.46: Attribute Model View Authority ................................................................................ 219Figure 6.47: Summary of Attribute Characteristics...................................................................... 220Figure 7.1: Strategic Modeling addresses Zachman Framework What (Col 1),Scope and Business (Rows 1–2) ................................................................................................ 224Figure 7.2: The Initial Strategic Model, with Business Rules Shown .......................................... 228Figure 7.3: Addition of Budget and its Business Rules to the Strategic Model ........................... 229Figure 7.4: Many to Many Rule Between Project and Budget Needs Resolution....................... 230

Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies xvii


Figure 7.5: Resolution of Many to Many by Adding Project Budget............................................ 231Figure 7.6: Addition of Project Manager and Person to the Strategic Model .............................. 233Figure 7.7: Addition of Project Objective to the Strategic Model................................................. 234Figure 7.8: Strategic Model Starting Point for use with Box 7.1.................................................. 236Figure 7.9: Sample Solution for Project Teams in Box 7.1 ......................................................... 238Figure 7.10: Sample Solution for Project Activities in Box 7.1 .................................................... 239Figure 7.11: Sample Solution for Project Skills in Box 7.1 .......................................................... 241Figure 7.12: Sample Solution for Project Resources in Box 7.1 ................................................. 242Figure 7.13: Sample Solution for Related Budgets in Box 7.1 .................................................... 244Figure 7.14: Sample Solution for Related Projects in Box 7.1 .................................................... 245Figure 7.15: Evolved Strategic Model Sample Solution for Box 7.1............................................ 246Figure 7.16: Identifying Business Activities from a Strategic Model............................................ 247Figure 7.17: Project Budget Management Activity Identified from Strategic Model .................... 249Figure 7.18: Highlighted Entities for Project Budget Management Activity................................. 250Figure 7.19: Project Objective Management Activity Highlighted in Strategic Model ................. 251Figure 7.20: Project Plans Derived from Strategic Model ........................................................... 252Figure 7.21: Entity Dependency Rule 1 for Association Degree or Cardinality........................... 254Figure 7.22: Entity Dependency Rule 2a for Association Nature ................................................ 255Figure 7.23: Entity Dependency Rule 2b for Association Nature ................................................ 255Figure 7.24: Entity Dependency Examples of Ownership ........................................................... 257Figure 7.25: Data Map to be used for Entity Dependency Analysis............................................ 259Figure 7.26: Identifying Phase Numbers for Person Skill Management...................................... 260Figure 7.27: Project Map Subproject Deliverables for Person Skill Management ...................... 260Figure 7.28: End-Point PROJECT RESOURCE for Entity Dependency Analysis ...................... 261Figure 7.29: Identifying Phase Numbers for Project Resource Management ............................. 263Figure 7.30: Project Map Subproject Deliverables for Project Managementand Project................................................................................................................................... 264Figure 7.31: This Strategic Map will be Analyzed Manually in Case StudyProblem 2 to derive Project Plans for Subprojects...................................................................... 267Figure 7.32: Gantt chart for Customer Needs Analysis Activity (Source: DSS).......................... 270Figure 7.33: Project Map for Large Government Department (Source: DSS) ............................ 271Figure 7.34: Summary Project Map for Government Department (Source: DSS) ...................... 272Figure 7.35: Subset of the Bank’s strategic model...................................................................... 273Figure 7.36: Derived project plan for Market Need Activity, which is reusable ........................... 274Figure 7.37: Derived project plan for Market Plan Activity .......................................................... 275Figure 7.38: Gantt chart Project Plan for Market Need Activity andMarket Plan Activity ..................................................................................................................... 276Figure 7.39: Summary Project Map for Regional Bank (Source: Kwangju Bank)....................... 276Figure 7.40: Customer Management Project Map (Source: Kwangju Bank) .............................. 277Figure 7.41: Articles of Law used as Strategic Modeling Catalyst (Source: PAI) ....................... 280Figure 7.42: Subset Article Rows for Organization Unit Columns (Source: PAI) ........................ 281Figure 7.43: Strategic Data Map developed from Articles of Law (Source: PAI) ........................ 282

xviii Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies


Figure 7.44: Project Map from Automatically Derived Clusters (Source: PAI) ............................ 282Figure 7.45: Strategic Plans and Life Events used as Catalysts for StrategicModeling (Source: HRDC)........................................................................................................... 283Figure 8.1: Activity Modeling addresses Zachman Framework Col 2, Rows 1–2....................... 285Figure 8.2: Steps 6 - 8 for Rapid Implementation of Enterprise Architecture.............................. 287Figure 8.3: Alignment Matrix of Plans (Col 6) to Organization Structure (Col 4).This matrix shows “Who” are involved and “Why” they are needed............................................ 290Figure 8.4: Functions group related activities. Activities show WHAT is to be done.Processes show HOW tasks are executed. ................................................................................ 291Figure 8.5: Activity Models and ABC are used for Process Improvement .................................. 292Figure 8.6: Activity Model for Human Resource Recruiting ........................................................ 294Figure 8.7: IDEF0 Activity Model diagrams. The Context diagram shows the overallscope of an activity at the highest level ....................................................................................... 295Figure 8.8: ICOM is an acronym for: Input; Control; Output; and Mechanism ........................... 296Figure 8.9: A typical Context diagram ......................................................................................... 296Figure 8. 10: Reading high level Context diagram, or lower level Activity Maps ........................ 297Figure 8.11: IDEF0 Activity Model diagrams. An Activity Map is a decompositiondiagram that shows the relationship between activities at the same level .................................. 299Figure 8.12: Feedback loops originate as Outputs. They can feedback as Inputs,Controls or Mechanisms.............................................................................................................. 300Figure 8.13: IDEF0 Activity Model diagrams. A Node diagram shows hierarchicalrelationships between activities at different levels....................................................................... 301Figure 8.14: Example of an Output Measure for an Activity........................................................ 304Figure 8.15: Workflow Modeling addresses Zachman Col 4, Row 2 .......................................... 308Figure 8.16: Data Map to be used for derivation of Workflow Model .......................................... 309Figure 8.17: Job Skill Management Cluster in the Data Map ...................................................... 310Figure 8.18: Project Map for Subproject Clusters in Figure 8.17 ................................................ 311Figure 8.19: Activity Map from Project Map, showing a feedback loop....................................... 311Figure 8.20: Activity Map from Project Map, showing decomposition hierarchy......................... 311Figure 8.21: Activity Flowchart derived from activity hierarchy diagram, showingpotential execution sequence...................................................................................................... 312Figure 8.22: Workflow diagram derived from activity flowchart, with externaltasks also added.......................................................................................................................... 313Figure 8.23: Highlighted Entities for Project Budget Management Activity................................. 314Figure 8.24: Context Diagram for Project Budget Management Activity..................................... 314Figure 8.25: Business Rules apply to Col 6, Row 3; Rule Design is Row 4;Rule Specification is Row 5 ......................................................................................................... 316Figure 8.26: BRS Proteus Support for Zachman Framework (Source: BRSolutions)................. 317Figure 8. 27: Developing the Business Model (Source: www.BRSolutions.com) ....................... 318Figure 9.1: Logical Data Modeling addresses Zachman Framework Col 1, Row 3 .................... 324Figure 9.2: Logical Data Modeling for 3-Month Incremental Builds ............................................ 324Figure 9.3: Problems that can occur with the Employee Register Form..................................... 328Figure 9.4: Employee details are moved to an Employee Details Form ..................................... 329Figure 9.5: Employee Skills are moved to an Employee Skill Details Form................................ 329

Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies xix


Figure 9.6: Skills are moved to a Skill Details form..................................................................... 330Figure 9.7: Job name is moved to a Job Details Form................................................................ 331Figure 9.8: The Employee, Employee Skill and Skill tables use common keysto cross-reference........................................................................................................................ 332Figure 9.9: We can extract Job Name from the Job table based on Job No............................... 333Figure 9.10: All tables are related by common keys for cross-reference.................................... 334Figure 9.11: Unnormalized Entity, used as an example for Business Normalization.................. 338Figure 9.12: Data Map of Unnormalized Entity ........................................................................... 338Figure 9.13: Data Map of 1BNF Entities...................................................................................... 339Figure 9.14: 2BNF EMPLOYEE, EMPLOYEE SKILL and SKILL entities ................................... 341Figure 9.15: Decomposition of Many to Many applies 1BNF and 2BNF..................................... 342Figure 9.16: Applying the 1BNF Rule to SKILL ........................................................................... 343Figure 9.17: Applying the 2BNF Rule to SKILL ........................................................................... 344Figure 9.18: Example Data Map in Third Business Normal Form (3BNF) .................................. 348Figure 9.19: 3BNF Data Map after Normalization Cross-Check ................................................. 354Figure 9.20: 4BNF Data Map for 4BNF entities........................................................................... 357Figure 9.21: Data Map showing a Typical 5BNF Entity............................................................... 360Figure 9.22: Format of EMPLOYEE STRUCTURE 5BNF Entity ................................................ 360Figure 9.23: Employee Structure 5BNF “Manages” and “Reports to” Relationships .................. 362Figure 9.24: Employee Structure “Supports” and Supported By” Relationships ......................... 364Figure 9.25: Answers to Questions 1 and 2 on “Sales Support” Relationships .......................... 364Figure 9.26: Answers to Questions 3 and 4 on “Sales Support” Relationships .......................... 365Figure 9.27: Answers to Questions 5 and 6 on “Sales Support” Relationships .......................... 366Figure 9.28: Effect of Expert Knowledge “Backup Support” Relationship................................... 367Figure 9.29: 5BNF Data Map for PRODUCT STRUCTURE ....................................................... 369Figure 9.30: High-Level PRODUCT STRUCTURE Bill of Material Table ................................... 370Figure 9.31: Manufacture of Sub-Assembly 4362 in PRODUCT STRUCTURE......................... 370Figure 9.32: Quantities used for Physical assembly of SUB 4558 for ASM 4358(Source: Bob Weisman) .............................................................................................................. 371Figure 9.33: Manufacture of Sub-Assembly 4556 in PRODUCT STRUCTURE......................... 371Figure 9.34: Expert Knowledge of Alternative Item 4088 in PRODUCT STRUCTURE.............. 373Figure 9.35: Example of “Where Used” with PRODUCT STRUCTURE ..................................... 374Figure 9.36: 5BNF High-level Example of ORGANIZATION STRUCTURE ............................... 374Figure 9.37: 5BNF and 4BNF Examples of ORGANIZATION STRUCTURE ............................. 376Figure 9.38: Resolution of Many to Many with ORG ROLE ........................................................ 377Figure 9.39: 5BNF Data Map Showing ORG STRUCT and ROLE STRUCT ............................. 378Figure 9.40: 5BNF ROLE STRUCT Table Showing Typical Content.......................................... 378Figure 9.41: 5BNF ROLE STRUCT Table Shows Important Facts about Brink ......................... 379Figure 9.42: 5BNF ORG STRUCT Table Shows Other Facts .................................................... 380Figure 9.43: Both 5BNF Tables are used together for Market Intelligence................................. 381Figure 9.44: Further Market Intelligence from these 5BNF Tables ............................................. 382Figure 9.45: Still Further Market Intelligence from these 5BNF Tables ...................................... 383

xx Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies


Figure 10.1: Process models address Zachman framework [C2R2-C2R3]. ............................... 388Figure 10.2: Menus, screens, and processes are defined for columns 4 and 2. ........................ 389Figure 10.3: Data map fragment to be used for menu structure design...................................... 392Figure 10.4: Menu structure design from a data map fragment. ................................................. 392Figure 10.5: Project Resource Management Menu Structure Design......................................... 394Figure 10.6: Typical Columnar Screen Form Design from an Entity........................................... 396Figure 10.7: One to many associations suggest Master – Detail screen designs ...................... 397Figure 10.8: Screen form designs based on data map associations. ......................................... 398Figure 10.9: Data Map used for Data Base Capacity Planning, for TransactionResponse Time Analysis and for Distributed Transaction Performance Analysis ...................... 399Figure 10.10: Data Map showing Data Volumes and Association Frequencies ......................... 399Figure 10.11: Physical Transaction Performance Analysis – Not Optimized.............................. 403Figure 10.12: Physical Transaction Performance Analysis – Data Base Clustering................... 404Figure 10.13: Distributed Database Design – Not Optimized ..................................................... 406Figure 10.14: Distributed Transaction Performance Analysis – Network Impact........................ 408Figure 10.15: Typical Sales and Distribution Data Model, to be used for Prototyping................ 410Figure 10.16: The Order Entry Data Map, with all Attributes Displayed...................................... 411Figure 10.17: Cluster Analysis and Menu Design of Order Entry Data Map............................... 412Figure 10.18: Screen Design of the Customer Form from the CUSTOMER entity..................... 412Figure 10.19: Screen Design of the Order Form from the ORDER entity ................................... 413Figure 10.20: Screen Design of the Order Details Form from ORDER PRODUCT.................... 414Figure 10.21: Physical Database Design and DDL generated for Microsoft Access .................. 415Figure 10.22: Generated DDL Opened as a Data Model in Microsoft Access............................ 415Figure 10.23: CUSTOMER in Phase 1 is generated as a Columnar Table ................................ 416Figure 10.24: Reuse of Menus and Screens with entry from PRODUCT ................................... 416Figure 10.25: Reuse of CUSTOMER Form with entry from PRODUCT ..................................... 417Figure 10.26: Functions group related activities. Activities show WHAT is to bedone. Processes show HOW tasks are executed (Repeated from Figure 8.4) .......................... 420Figure 10.27 : Core Set of BPMN Diagram elements (Source: BPMN 2.0 Specs[Reprinted with Permission])........................................................................................................ 420Figure 10.28: A BPMN Business Process Diagram for a Doctor’s Surgery(Source: BPMN 2.0 Specs [Reprinted with Permission]) ............................................................ 421Figure 10.29: Messages in a diagram associated with message flow(Source: BPMN 2.0 Specs [Reprinted with Permission]) ............................................................ 422Figure 10.30 : Message Flow between Participants across Pools(Source: BPMN 2.0 Specs [Reprinted with Permission]) ............................................................ 422Figure 10.31: Example of Choreography within a Collaboration(Source: BPMN 2.0 Specs [Reprinted with Permission]) ............................................................ 423Figure 10.32: Business Process Diagram in BPMN of an Online Auction(Source: BPMI.org [Reprinted with Permission])......................................................................... 424Figure 10.33: Complex Processes Invoke Child Processes ....................................................... 425Figure 11.1: Example of an XML Purchase Order (© 2001 Software AG.[Reprinted with Permission].)....................................................................................................... 431Figure 11.2: A Purchase Order in two different XML formats (© 2001 Software AG.

Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies xxi


[Reprinted with Permission].)....................................................................................................... 433Figure 11.3: Example of the XSLT transformation engine used by BizTalk DataMapper (© 2004 Microsoft Corporation. [Reprinted with Permission].)....................................... 434Figure 11.4: Trading Communities accept a variety of XML message envelopeformats, automatically converting from one to the other (© 2002 CommerceOne.[Reprinted with Permission].)....................................................................................................... 436Figure 11.5: Using a Web Browser, Company 1 can connect easily to Company 2and so purchase goods and services (© 2002 CommerceOne.[Reprinted with Permission].)....................................................................................................... 437Figure 11.6: Company 1 and Company 2 both use XML electronic PurchaseOrders directly from or to back-end Systems (© 2002 CommerceOne.[Reprinted with Permission].)....................................................................................................... 438Figure 11.7: There are many possible XML formats for document interchangebetween organizations (© 2002 CommerceOne. [Reprinted with Permission].)......................... 439Figure 11.8: A Common XML Purchase Order format can easily be extendedusing XML to address different Industry requirements (© 2002 CommerceOne.[Reprinted with permission]) ........................................................................................................ 440Figure 11.9: Real-World Document Delivery (© 2002 CommerceOne. [Reprinted withPermission].)................................................................................................................................ 441Figure 11.10: Electronic Document Delivery (© 2002 CommerceOne. [Reprinted withPermission].)................................................................................................................................ 442Figure 11.11: CommerceOne has established a Global Trading Web (GTW)using large Telcos across many Countries (© 2002 CommerceOne.[Reprinted with Permission].)....................................................................................................... 444Figure 11.12: ebXML Message Envelope Format (© 2001 ebXML.org.[Reprinted with permission]) ........................................................................................................ 451Figure 11.13: Steps in using the ebXML Repository (© 2001 ebXML.org.[Reprinted with Permission])........................................................................................................ 452Figure 11.14: XML Messages are examined for Content and Process Workflow.They are transformed to the format expected by back-end enterprise systems.(Source: eXcelon Corporation – now Sonic Software © 2001 Sonic Software.[Reprinted with permission]) ........................................................................................................ 454Figure 11.15: XYZ Workflow Steps to Accept an XML PO sent by ABC.(Source: eXcelon Corporation – now Sonic Software © 2001 Sonic Software.[Reprinted with Permission])........................................................................................................ 455Figure 11.16: XYZ Workflow Steps to Process an XML PO that was sent by ABC.(Source: eXcelon Corporation – now Sonic Software © 2001 Sonic Software.[Reprinted with permission]) ........................................................................................................ 456Figure 11.17: ABC Workflow Steps for Receipt of the ASN and Supplier Invoicefrom XYZ. (Source: eXcelon Corporation – now Sonic Software © 2001 Sonic Software.[Reprinted with permission]) ........................................................................................................ 456Figure 11.18: Address Change Notification Form with Manual Reentry (Adapted from© 2001 Gartner. [Reprinted with permission]) ............................................................................ 458Figure 11.19: Address Change Notification using EAI avoids the need for ManualReentry. (Adapted from Gartner Group © 2001 Gartner. [Reprinted with permission]) ............. 459Figure 12.1: Typical Enterprise Portal Architecture (Adapted from: Colin White,BI Research © 2005 BI Research. [Reprinted with Permission]) ............................................... 466Figure 12.2: Herman Miller MySIGN e-Business Portal (Source: © 2001

xxii Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies


Herman Miller. [Reprinted with Permission]) .............................................................................. 471Figure 12.3: Employee Section of the Ford B2E Portal (Source: © 2002Ford Motor Company. [Reprinted with Permission]) .................................................................. 474Figure 12.4: General Motors “MySocrates” Employee Portal (Source:© 2002 GM Corporation. [Reprinted with Permission]) .............................................................. 476Figure 13.1: Web Services are implemented using SOAP, WSDL and UDDI ............................ 486Figure 13.2: Address Change Notification using SOAP and Web Services avoidsthe need for Manual Reentry. (Adapted from Source: © 2001 Gartner Group.[Reprinted with Permission].)....................................................................................................... 488Figure 13.3: Invocation of Remote Web Services for Credit Card Approval, OrderFulfillment and Shipping using SOAP (Source: © 2001 Software AG.[Reprinted with Permission].)....................................................................................................... 490Figure 13.4: SOAP Message Envelope Structure (Source: © 2001 W3C.[Reprinted with Permission].)....................................................................................................... 492Figure 13.5: Structure of WSDL Interface and Implementation Files (Source:© 2001 IBM Corporation. [Reprinted with Permission].) ............................................................. 493Figure 13.6: Structure of a UDDI Definition (Source: © 2001 IBM Corporation.[Reprinted with Permission].)....................................................................................................... 495Figure 13.7: Relationship between WSDL Files and a UDDI Definition (Source:© 2001 IBM Corporation. [Reprinted with Permission].) ............................................................ 496Figure 13.8: Publishing and Discovering Web Services using UDDI, WSDL andSOAP (Source: © 2001 Software AG. [Reprinted with Permission].).......................................... 496Figure 14.1: Integration Platform is for all Communication (Source: © 2001Software AG. [Reprinted with Permission].) ................................................................................ 507Figure 14.2: What Errors can occur? (Adapted from Source: © 2001 Software AG.[Reprinted with Permission].)....................................................................................................... 509Figure 14.3: Real-Time Error Management (Adapted from Source: © 2001Software AG. [Reprinted with Permission].) ................................................................................ 511Figure 14.4: A Travel Agent Example using BPEL (Source: © 2002 IBM Corporation.[Reprinted with Permission].)....................................................................................................... 516Figure 14.5: Example of BPML used to Synchronize Activities Executing in Parallel) ............... 523Figure 14.6: A Process from Different Points of View using BPMN............................................ 528Figure 14.7: Part of Travel Agent example in Figure 14.4, shown as a BPMN BPD .................. 529Figure 15.1: Different modes of partitioning (Source: © 2005 IBM Corporation.[Reprinted with Permission].)....................................................................................................... 537Figure 15.2: Enterprise Workload Management (Source: © 2005 IBM Corporation.[Reprinted with Permission].)....................................................................................................... 538Figure 15.3: On Demand Operating Environment Architecture (Source: © 2005IBM Corporation. [Reprinted with Permission].) .......................................................................... 539Figure 15.4: Summary of Virtualization and On Demand (Source: © 2005IBM Corporation. [Reprinted with Permission].) .......................................................................... 540Figure 15.5: Relative Costs of Different Integration Approaches (Source:© 2002 ZapThink. [Reprinted with Permission].)......................................................................... 543Figure 15.6: The Integration “Zipper” (Source: © 2003 ZapThink.[Reprinted with Permission].)....................................................................................................... 544