Erickson Methodology for Enterprise Architecture

Douglas T. Erickson

Description

Get better results and rethink what information technology is and what it should be with the Erickson Methodology for Enterprise Architecture.
This book describes a methodology for architecting, designing, and constructing an enterprise that specifies what to do, but more importantly, how to it, and why you would want to do it that way! The methodological concepts, principles, conventions, and practices presented in this book have been developed and put into practice for over 25 years; and the results are dramatic and worthy of pursuit by any enterprise.

Sujets

• Business Process Management
• Zachman Framework
• Economics
• Business
• EMEA

Informations

• Publié par: iUniverse
• Date de parution: 20 décembre 2020
• Nombre de lectures: 0
• EAN13: 9781532099953
• Langue: English
• Poids de l'ouvrage: 1 Mo

Extrait

ERICKSON METHODOLOGY FOR ENTERPRISE ARCHITECTURE
VOLUME 1
 

ENTERPRISE ARCHITECTURE THAT:
➢ Achieves Enterprise Alignment, Integration,
Flexibility, And Responsiveness,
 
➢ Dramatically Reduces Costs!
How to Achieve a
21 st Century Enterprise Architecture Services Capability.
 
Written by
DOUGLAS T. ERICKSON
With Donald B. Phillips
Foreword by John A. Zachman
 
ERICKSON METHODOLOGY FOR ENTERPRISE ARCHITECTURE
HOW TO ACHIEVE A 21ST CENTURY ENTERPRISE ARCHITECTURE SERVICES CAPABILITY.
 
Copyright © 2020 Douglas T. Erickson.
 
All rights reserved. No part of this book may be used or reproduced by any means, graphic, electronic, or mechanical, including photocopying, recording, taping or by any information storage retrieval system without the written permission of the author except in the case of brief quotations embodied in critical articles and reviews.
 
The views expressed in this work are solely those of the author and do not necessarily reflect the views of the publisher, and the publisher hereby disclaims any responsibility for them.
 
iUniverse
1663 Liberty Drive
Bloomington, IN 47403
www.iuniverse.com
844-349-9409
 
Because of the dynamic nature of the Internet, any web addresses or links contained in this book may have changed since publication and may no longer be valid. The views expressed in this work are solely those of the author and do not necessarily reflect the views of the publisher, and the publisher hereby disclaims any responsibility for them.
 
Any people depicted in stock imagery provided by Getty Images are models, and such images are being used for illustrative purposes only.
Certain stock imagery © Getty Images.
 
ISBN: 978-1-5320-9994-6 (sc)
ISBN: 978-1-5320-9996-0 (hc)
ISBN: 978-1-5320-9995-3 (e)
 
Library of Congress Control Number: 2020914814
 
iUniverse rev. date: 09/28/2022
 

TABLE OF CONTENTS
Dedication
William Darlage Testimonial
Foreword
Preface
Part One: An Introduction to Enterprise Architecture
1.1 Enterprise Architecture: What Is It?
1.2 Enterprise Architecture versus Enterprise Management
1.3 Enterprise Architecture: What Is Its’ Value?
1.4 Choosing How to Do Enterprise Architecture
1.5 Introduction to Enterprise Architecture Services for the 21st Century
1.6 What About TAFIM, C4ISR, DODAF, MODAF, UAF, AND TOGAF?
Part Two: The Enterprise Architecture Challenges
2.1 Introduction
2.2 The IT Job-Shop Business Model
2.3 The Obsession with Budgets and Schedules
2.4. The Search for the “Silver Bullet.”
2.5. The Focus on Who does What; and Lack of Focus on How and Why
2.6. The Build Versus Buy Conundrum
2.7. Overly Focusing On Projects (Tactical) Not On The Enterprise (Strategic)!
Part Three: The Erickson Methodology for Enterprise Architecture: How to Architect an Enterprise
3.1 Introduction
3.2 How to Perform the Enterprise Architecture Planning Phase (EAPP) (ZFEA Columns 1-6, Rows 1-2)
3.2.1 Introduction
3.2.2 Establish an Enterprise Architecture Planning Phase (EAPP) Project
3.2.2.1 Establish an EAPP Leadership Team
3.2.2.1.1 Select EAPP Enterprise Sponsor
3.2.2.1.2 Select EAPP Facilitator
3.2.2.1.3 Select EAPP Project Manager
3.2.2.2 Select EAPP Project Team Members
3.2.2.3 Select EAPP Project Support Team Members
3.2.2.4 Establish EAPP Project Facilities
3.2.2.5 Establish EAPP Project Team Work Routine
3.2.2.6 Develop EAPP Project Plan
3.2.2.6.1 Enterprise Architecture Planning Criteria
3.2.2.6.2 Obstacles to Effective Enterprise Architecture Planning
3.2.2.7 Conduct EAPP Team Orientation
3.2.3 Develop Enterprise Architecture Plan
3.2.3.1 Introduction
3.2.3.2 Develop Enterprise Scope Motivation Model (SMM) and Conceptual Motivation Model (CMM)
3.2.3.3 Develop Enterprise Scope Process Model (SPM) and Conceptual Process Model (CPM)
3.2.3.4 Develop Enterprise Scope Data Model (SDM) and Conceptual Data Model (CDM)
3.2.3.4.1 Develop Enterprise Scope Data Model (SDM)
3.2.3.4.2 Develop Enterprise Conceptual Data Model (CDM)
3.2.3.4.3 Develop Enterprise Information Architecture
3.2.3.4.4 Develop Logical Business Process Data Dependence Model
3.2.3.4.5 Develop Enterprise Entity-Relationship Model
3.2.3.5 Develop Enterprise Scope Location Model (SLM) and Conceptual Location Model (CLM)
3.2.3.6 Develop Enterprise Scope Organization Model (SOM) and
3.2.3.7 Develop Enterprise Scope Time Model (STM) and Conceptual Time Model (CTM)
3.2.3.8 Identify and Define Enterprise Strategic Issues
3.2.3.9 Develop Enterprise Architecture Implementation Prioritization
3.2.3.10 Develop Enterprise Architecture Strategy Plan (EASP)
3.3 How to Architect an Enterprise (ZFEA Row 3)
3.3.1 Establish an Enterprise Architecture Implementation Project (s) (EAIP).
3.3.1.1 Establish an EAI Oversight Group
3.3.1.2 Select EAIP EMEA Facilitator
3.3.1.3 Select EAIP Project Manager
3.3.1.4 Select EAIP EAP Facilitator (Also see Section 3.3.1.2)
3.3.1.5 Select EAIP EMEA EEP/EMP Facilitator
3.3.1.6 Select EAIP EAP Team Members
3.3.1.7 Select EAIP EEP/EMP Team Members
3.3.1.8 Establish EAP Facilities
3.3.1.9 Develop EAIP Project Plan
3.3.1.10 Conduct EAIP Team Orientation
3.3.2 Architect Enterprise Motivation (ZFEA Why Column, Row 3)
3.3.2.1 Develop Logical Product Motivation Model (PMM)/Logical Service Motivation Model (SMM)
3.3.2.2 Develop Logical Market Motivation Model
3.3.3 Architect Enterprise Data (ZFEA WHAT Column, Row 3)
3.3.3.1 The Enterprise Data Problem
3.3.3.2 The Enterprise Data Problem Solution
3.3.3.2.1 Adopt the Concept of an Enterprise Universe of Discourse
3.3.3.2.2 Adopt Fundamental Data Modeling Methodology Changes
3.3.3.3 Develop Enterprise Logical Data Model (ZFEA WHAT Column, Row 3, and Enterprise Database (ZFEA WHAT Column, Row 4)
3.3.3.3.1 Introduction
3.3.3.3.2 Criteria for Achieving High Quality, Cost-Effective Enterprise Data
3.3.3.4 Adopt Enterprise Database (EDB) Concept
3.3.3.5 Adopt Enterprise Data Services (EDS)
3.3.4 Architect Enterprise Business Processes (ZFEA HOW Column, Row 3)
3.3.4.1 The Business Process Problem
3.3.4.2 The Business Process Problem Solution
3.3.4.3 Develop Enterprise Business Process Architecture
3.3.4.3.1 Extend the Logical Business Process Decomposition to the Elementary Business Processes
3.3.4.3.2 Develop Business Process Specifications
3.3.5 Architect Enterprise Location (ZFEA WHERE Column, Row 3), Architect Enterprise Organization (ZFEA WHO Column, Row 3)
3.3.5.1 Develop Enterprise Logical Location Model (ZFEA WHERE Column, Row 3)
3.3.5.2 Architect Enterprise Organization (ZFEA WHO Column, Row 3)
3.3.6 Architect Enterprise Time (ZFEA WHEN Column, Row 3)
3.4 Enterprise Architecture (EA) Facilitation Skills
3.4.1 General Knowledge, Skills, and Expertise
3.4.1.1 Language Skills
3.4.1.2 Socratic Questioning Technique
3.4.1.3 Thinking Skills
3.4.1.4 Inductive and Deductive Reasoning
3.4.1.5 Facilitator Education, Background, and Experience
3.4.1.5 Facilitator Attitude, Character, and Behavior
3.4.2 General Enterprise Knowledge
3.5 Summary
APPENDIX A: Graphics Legend
Douglas T. Erickson
Donald B. Phillips
DEDICATION
I dedicate this book to my parents, Lawrence and Agnes Erickson. They exemplified, to me, what parents should be and do. They set the example of how to be a person who could be courageous, respected as a person, and who had value to others. I am profoundly glad that I am their son! However, I am still striving to meet their example!
My special recognition of Catherine Banning for sharing her life, and sustaining and abiding me through my effort to write this book. Along the way she taught me something about love and appreciation for another.
— Doug Erickson
To my wife, Diann, for her patience and understanding – for enduring those times I was away on projects - for calling her on our anniversary while I was having dinner with Doug many miles away.
— Don Phillips
 
William Darlage Testimonial
“It is my opinion that the methodology used on this project to define and understand explicitly (to the excruciating level of detail) the business processes and needs, and then to develop a system that meets those needs has been successful. From a data integrity perspective, having each piece of information identified by date/time, stored only once, and used as required exceeded our expectations.
Based on our experience this combination of methodology, tools, and skills should be the “platinum standard” employed on all future projects since it produces an exceptional level of quality and efficiency.
Willian Darlage, CPCU, Director, Actuarial Department, Ohio Bureau of Workers’ Compensation referring to results achieved using the Erickson Methodology for Enterprise Architec ture.
FOREWORD
I have known Douglas T. Erickson almost before he became known as Doug Erickson! It was probably about 1980 when we first met. Sometime in 1980, I was traveling through Phoenix, Arizona. I called Doug from the airport about 4:30 in the afternoon and asked him if I could come to his office for a discussion on an idea I had. He said he would wait for me at his office. Little did he know, nor I, that that conversation would last until after 1:00 AM the next morning. I did not have prepared “architecture” material at the time, but I had the initial concept in mind.
During that extended discussion,