Enterprise Architecture for Integration: Rapid Delivery Methods and Technologies (Artech House Mobile Communications Library)

540 Pages·2006·29.22 MB·English

by  Clive Finkelstein

Enterprise Architecture for Integration
Rapid Delivery Methods and Technologies
DISCLAIMER OF WARRANTY
The technical descriptions, procedures, and computer programs in this book have
beendevelopedwiththegreatestofcareandtheyhavebeenusefultotheauthorina
broadrangeofapplications;however,theyareprovidedasis,withoutwarrantyof
anykind.ArtechHouse,Inc.andtheauthorandeditorsofthebooktitledEnterprise
Architecture for Integration: Rapid Delivery Methods and Technologies make no
warranties, expressed or implied, that the equations, programs, and procedures in
thisbookoritsassociatedsoftwarearefreeoferror,orareconsistentwithanypar-
ticularstandardofmerchantability,orwillmeetyourrequirementsforanyparticu-
lar application. They should not be relied upon for solving a problem whose
incorrect solutioncould result in injury toa personor loss ofproperty. Any use of
theprogramsorproceduresinsuchamannerisattheuser’sownrisk.Theeditors,
author,andpublisherdisclaimallliabilityfordirect,incidental,orconsequentdam-
agesresultingfromuseoftheprogramsorproceduresinthisbookortheassociated
software.
For a listing of recent titles in the Artech House
Titles in Computing, turn to the back of this book.
Enterprise Architecture for Integration
Rapid Delivery Methods and Technologies
Clive Finkelstein
artechhouse.com
Library of Congress Cataloging-in-Publication Data
Finkelstein, Clive.
Enterprise architecture for integration: rapid delivery methods and technologies/Clive
Finkelstein.
p. cm.
Includes bibliographical references and index.
ISBN 1-58053-713-8 (alk. paper)
1. System design. 2. Computer architecture. 3. Computer software—Development.
I. Title. II. Series.
QA76.9.S88F527 2006
005.1’2—dc22 2005058857
British Library Cataloguing in Publication Data
Finkelstein, Clive
Enterprise architecture for integration: rapid delivery methods and technologies.
1. Enterprise application integration (Computer systems) 2. Software architecture
I. Title
005.2’76
ISBN-10: 1-58053-713-8
Cover design by Igor Valdman
© 2006 Clive Finkelstein
All rights reserved.
PrintedandboundintheUnitedStatesofAmerica.Nopartofthisbookmaybereproduced
orutilizedinanyformorbyanymeans,electronicormechanical,includingphotocopying,
recording,orbyanyinformationstorageandretrievalsystem,withoutpermissioninwriting
from the publisher.
Alltermsmentionedinthisbookthatareknowntobetrademarksorservicemarkshave
beenappropriatelycapitalized.ArtechHousecannotattesttotheaccuracyofthisinforma-
tion.Useofaterminthisbookshouldnotberegardedasaffectingthevalidityofanytrade-
mark or service mark.
International Standard Book Number: 1-58053-713-8
Library of Congress Catalog Card Number: 2005058857
10 9 8 7 6 5 4 3 2 1
To my wife, Jill—my friend, my companion,
and the love of my life
To our daughter Kristi, our son-in-law Bill,
and our two beautiful granddaughters, Megan and Apryl

Contents
Foreword xix
Preface xxv
CHAPTER 1
Enterprise Architecture and Enterprise Engineering 1
1.1 The Evolution of Enterprise Architecture 1
1.2 Using the Zachman Framework for Enterprise Architecture 5
1.2.1 The Difference Between Primitives and Composites 6
1.2.2 Identifying Reusable, Priority Areas for Early Delivery 8
1.3 Enterprise Engineering for Rapid Development 10
1.4 Using Enterprise Architecture for Enterprise Integration 15
1.4.1 The Importance of Metadata 16
1.5 Summary 18
Endnotes 19
PART I
Enterprise Architecture for Managers 21
CHAPTER 2
Balanced Scorecard and Strategy Maps 23
2.1 Introduction to Balanced Scorecard and Strategy Maps 23
2.2 Basic Concepts of Balanced Scorecard 24
2.2.1 Translate the Strategy to Operational Terms 24
2.2.2 Align the Organization to the Strategy 26
2.2.3 Make Strategy Everyone’s Everyday Job 26
2.2.4 Make Strategy a Continual Process 27
2.2.5 Mobilize Change Through Executive Leadership 28
2.3 Basic Concepts of Strategy Maps 28
2.4 Examples of Balanced Scorecard and Strategy Maps 31
2.4.1 Differentiation of Mobil North America Marketing and Refining 31
2.4.2 Differentiation of the Financial Perspective at Mobil 32
2.4.3 The New Customer Perspective at Mobil 33
2.4.4 The Internal Process Perspective at Mobil 34
2.4.5 The Learning and Growth Perspective at Mobil 35
2.5 Steps to Develop Balanced Scorecards and Strategy Maps 36
2.5.1 Methods for Defining Strategies, Processes, and Systems 37
2.6 Summary 39
Endnotes 39
vii
viii Contents
CHAPTER 3
Using Strategy Analysis to Define the Future 41
3.1 Strategy Analysis in Business Planning 41
3.1.1 Using Strategy Analysis 43
3.1.2 The Quality of Planning Statements 44
3.2 The Steps of Strategy Analysis 46
3.2.1 Step 1—Understand the Mission and Purpose 46
3.2.2 Step 2—Identify the Major Business Areas 47
3.2.3 Step 3—Determine What Has to Be Achieved 48
3.2.4 Step 4—Identify Issues Representing Opportunities or Problems 49
3.2.5 Step 5—Determine What Will Achieve or Resolve the Issues 53
3.2.6 Step 6—Define Key Performance Indicators 56
3.2.7 Step 7—Identify the Current Functions That Exist 57
3.2.8 Step 8—Allocate Functional Responsibility to Implement
3.2.8 Strategies 58
3.2.9 Step 9—Define Job Role Responsibilities for Each Function 60
3.2.10 Benefits of Strategy Analysis 62
3.3 Strategy Analysis for Project Specifications 62
3.3.1 Step 1—Examine Business and Project Mission Statements 63
3.3.2 Step 2—Identify Project Goals and Performance Criteria 63
3.3.3 Step 3—Define Clear Business and Project Goals 63
3.3.4 Step 4—Identify the Business Problems or Opportunities 63
3.3.5 Step 5—Determine Strategies to Address Problems or
3.2.8 Opportunities 64
3.3.6 Step 6—Define Key Performance Indicators 64
3.3.7 Step 7—Determine Which Business Functions Are to
3.2.8 Be Supported 64
3.3.8 Step 8—Identify Managers and Business Experts from
3.2.8 Each Function 64
3.3.9 Step 9—Schedule Joint Participation by Business and IT Experts 64
3.4 Preparation for Strategy Analysis 65
3.4.1 Business Planning Questionnaire 65
3.4.2 Enterprise Mission and Purpose 67
3.4.3 Business Unit Mission and Purpose 68
3.4.4 Policies, Objectives, or Strategies 68
3.4.5 Processing of Questionnaire Responses 68
3.4.6 Refined Policies, Objectives, or Strategies 68
3.4.7 Markets, Products and Services, Channels, and SWOTs 69
3.5 Questionnaire Templates for Enterprise Architecture 69
3.5.1 Business Planning Questionnaire Template 69
3.5.2 Strategic Modeling Questionnaire Template 69
3.6 Summary 70
Endnotes 70
CHAPTER 4
Governance Analysis Using Enterprise Architecture 73
4.1 Responsibilities Imposed by Sarbanes-Oxley 73
Contents ix
4.1.1 Typical Internal Control Questions 74
4.1.2 Managing Internal Controls Using Enterprise Architecture 76
4.2 Governance Analysis Framework (GAF) for Sarbanes-Oxley 77
4.2.1 Developing a Governance Analysis Framework 80
4.2.2 Methods and Tools for Governance Analysis 82
4.2.3 Business Transformation Using Enterprise Architecture 85
4.3 Step-by-Step Approach for Governance Analysis 85
4.3.1 Step 1—Establish Plan for Strategic Modeling Project 86
4.3.2 Step 2—Capture Initial Business Planning Input as Catalyst 86
4.3.3 Step 3—Conduct Strategic Modeling Facilitated Session 86
4.3.4 Step 4—Carry Out Strategic Model Analysis 86
4.3.5 Step 5—Derive Governance Analysis Framework
3.2.8 Documentation 87
4.3.6 Step 6—Review Matrices and Governance Implementation Plan 87
4.3.7 Step 7—Manage Progressive Completion of GAF Matrices 87
4.3.8 Step 8—Manage Implementation of Governance Analysis
3.2.8 Systems 87
4.4 Summary 88
Endnotes 89
PART II
Enterprise Architecture Methods 91
CHAPTER 5
Methods for Building Enterprise Architecture 93
5.1 Evolution of Systems Development Methodologies 93
5.1.1 Evolution of Software Engineering 93
5.1.2 Evolution of Information Engineering 94
5.1.3 Evolution of Object-Oriented Methods 95
5.2 Review of Enterprise Architecture 95
5.2.1 Business Knowledge Is Needed for Enterprise Architecture 95
5.2.2 Technology Decisions Using Enterprise Architecture 96
5.2.3 Enterprise Architecture and the Pace of Change 96
5.3 Government Methods for Building Enterprise Architecture 97
5.3.1 Federal Enterprise Architecture Framework 97
5.3.2 Relating the FEAF to the Zachman Framework 102
5.4 Department of Defense Architecture Frameworks 105
5.4.1 Defence Planning Terminology 105
5.4.2 The Need for Defence Interoperability 106
5.4.3 Approach 1: Common Integrated Technology Environments 109
5.4.4 Approach 2: Integrated Technology and Information
3.2.8 Environments 109
5.4.5 Approach 3: Partially Integrated Technology and Information 109
5.4.6 Approach 4: Federated Information and Technology
3.2.8 Environment 112
5.4.7 Evolution of Enterprise Architecture Within DoD 113
5.4.8 Defence Architecture Framework 115