Expert answer:What is an EA, and what does Enterprise Architect
Solved by verified expert:In your opinion, what are three main topics of chapter three?How do these assessments work?What is EA1 and how does it affect an Enterprise Architect?Outline and describe in some detail EA2 – EA8.Must be a minimum words of 1000, with 3 or more references. In APA format with no PLAGARISM.NOTE: Chapter 3 is found in below attachment.
collaborative_enterprise_architecture.docx
Unformatted Attachment Preview
Collaborative Enterprise
Architecture
Intentionally left as blank
Collaborative Enterprise
Architecture
Enriching EA with Lean, Agile, and
Enterprise 2.0 Practices
Stefan Bente
Dr. Uwe Bombosch
Shailendra Langade
AMSTERDAM • BOSTON • HEIDELBERG • LONDON
NEW YORK • OXFORD • PARIS • SAN DIEGO
SAN FRANCISCO • SINGAPORE • SYDNEY • TOKYO
Morgan Kaufmann is an imprint of Elsevier
Acquiring Editor: Andrea Dierna
Development Editor: Robyn Day
Project Manager: Jessica Vaughan
Designer: Greg Harris
Morgan Kaufmann is an imprint of Elsevier
225 Wyman Street, Waltham, MA 02451, USA
# 2012 Elsevier, Inc. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic
or mechanical, including photocopying, recording, or any information storage and retrieval system,
without permission in writing from the publisher. Details on how to seek permission, further information about
the Publisher’s permissions policies and our arrangements with organizations such as the Copyright Clearance
Center and the Copyright Licensing Agency, can be found at our website: www.elsevier.com/permissions.
This book and the individual contributions contained in it are protected under copyright by the Publisher (other
than as may be noted herein).
Notices
Knowledge and best practice in this field are constantly changing. As new research and experience broaden our
understanding, changes in research methods or professional practices, may become necessary. Practitioners and
researchers must always rely on their own experience and knowledge in evaluating and using any information
or methods described herein. In using such information or methods they should be mindful of their own safety
and the safety of others, including parties for whom they have a professional responsibility.
To the fullest extent of the law, neither the Publisher nor the authors, contributors, or editors, assume any liability for
any injury and/or damage to persons or property as a matter of products liability, negligence or otherwise, or from any
use or operation of any methods, products, instructions, or ideas contained in the material herein.
Library of Congress Cataloging-in-Publication Data
Bente, Stefan.
Collaborative enterprise architecture : enriching EA with lean, agile, and enterprise 2.0 practices /
Stefan Bente, Uwe Bombosch, Shailendra Langade.
p. cm.
Includes bibliographical references and index.
ISBN 978-0-12-415934-1
1. Management information systems. 2. Business enterprises–Computer networks. 3. Information
technology– Management. 4. Software architecture. I. Bombosch, Uwe. II. Langade, Shailendra. III. Title.
HD30.213.B463 2013
658.4’038011–dc23
2012014682
British Library Cataloguing-in-Publication Data
A catalogue record for this book is available from the British Library.
ISBN: 978-0-12-415934-1
Printed in the United States of America
12 13 14 15 16
10 9 8 7 6 5 4 3 2 1
For information on all MK publications visit our website at www.mkp.com
To our families (Beate and Thomas; Christiane and Julian; Deepali, Pratik,
and Tanishka), with many thanks for their support and patience.
Intentionally left as blank
Contents
Acknowledgments…………………………………………………………………………………………….. xi
CHAPTER 1
Why Collaborative Enterprise Architecture? ……………………………………….. 1
Reasons for This Book…………………………………………………………………….. 1
Goals and Benefits of Enterprise Architecture …………………………………………. 4
Controlling IT Complexity …………………………………………………………… 6
Aligning Business and IT ……………………………………………………………. 9
The Gray Reality: Enterprise Architecture Failures ………………………………….. 11
Between Success and Disappointment ……………………………………………. 12
Perspective: Between Bird’s-Eye View and Nitty-Gritty on the Ground …….. 14
Governance: A Host of Directives, but No One Follows Them ……………….. 19
Strategy: Marathon or 100 m Run? ……………………………………………….. 21
Transformation: Between Standstill and Continuous Revolution …………….. 23
Enriching EA by Lean, Agile, and Enterprise 2.0 Practices ………………………… 25
How This Book Is Structured ……………………………………………………… 28
CHAPTER 2
What Is Enterprise Architecture? …………………………………………………… 31
The Meaning of Architecture …………………………………………………………… 31
Applying Architecture to an Enterprise ……………………………………………….. 34
EA Applicability and Use ……………………………………………………………….. 36
CHAPTER 3
What Enterprise Architects Do: Core Activities of EA …………………………… 39
Defining the IT Strategy (EA-1) ……………………………………………………….. 41
Defining the Goals ………………………………………………………………….. 42
Stipulating the Rules ………………………………………………………………… 43
The Gartner Grid ……………………………………………………………………. 46
Identifying the Initiatives …………………………………………………………… 48
The Role of an Enterprise Architect ………………………………………………. 49
Modeling the Architectures (EA-2) ……………………………………………………. 49
Models and Views of Various Architectures …………………………………….. 49
Visualizing Cross-Relations and Transformations………………………………. 51
Modeling Standards …………………………………………………………………. 52
Evolving the IT Landscape (EA-3) …………………………………………………….. 58
Application Rationalization ………………………………………………………… 58
General IT Transformations ……………………………………………………….. 66
SOA Transformations ………………………………………………………………. 67
Assessing and Building Capabilities (EA-4) ………………………………………….. 69
Competence Development for Enterprise Architects …………………………… 69
vii
viii
Contents
Formalizing Enterprise Architecture ………………………………………………. 74
EA Team Position in the Organization Structure ………………………………… 76
Developing and Enforcing Standards and Guidelines (EA-5) ………………………. 78
Standardizing on Technology Usage ……………………………………………… 79
Enforcing Standards and Guidelines ………………………………………………………………………. 83
Monitoring the Project Portfolio (EA-6) ………………………………………………………………….. 86
Building the Project Portfolio ………………………………………………………………………………. 87
Auditing the Portfolio ……………………………………………………………………………………….. 93
Leading or Coaching Projects (EA-7)……………………………………………………………………… 98
Managing Risks Involved in IT (EA-8) …………………………………………………………………..100
CHAPTER 4
EA Frameworks ………………………………………………………………………. 105
What is an EA Framework? …………………………………………………………… 106
The Zachman Framework for Enterprise Architecture …………………………….. 108
The Open Group Architecture Framework (TOGAF) ……………………………… 110
TOGAF Architecture Development Methodology (ADM) …………………… 111
TOGAF Architecture Content Framework ……………………………………… 114
TOGAF Architecture Capability Framework ………………………………….. 115
Gartner Methodology (Formerly META Framework) …………………………….. 118
The Role and Use of EA frameworks………………………………………………… 121
CHAPTER 5
EA Maturity Models ………………………………………………………………….. 123
Applying Maturity Model to EA ……………………………………………………… 124
What is a Maturity Model? ……………………………………………………….. 124
Relevance of Maturity Models in EA …………………………………………… 126
A Rule of Thumb for the Architectural Maturity of an Enterprise …………… 126
OMB EA Assessment Framework……………………………………………………. 127
Architecture Capability Maturity Model of the US Department of Commerce … 130
EA Maturity Model by MIT Center for Information System Research ………….. 132
Experiences with the Maturity Models ………………………………………………. 134
CHAPTER 6
Foundations of Collaborative EA ………………………………………………….. 137
Reflections on Complexity ……………………………………………………………. 139
Beyond Threshing Machines …………………………………………………….. 139
Structure and Behavior of Complex Phenomena ………………………………. 140
Principles of Managing Complexity …………………………………………….. 141
Management Capabilities of Hierarchies and Networks ……………………… 146
The EA Dashboard as a Yardstick for EA Effectiveness ………………………….. 152
CHAPTER 7
Toward Pragmatism: Lean and Agila EA ………………………………………… 159
The Architecture Factory: Applying Lean and Agile Methods to EA ……………. 160
Lean and Agile Principles as Facilitators for the Architecture Factory……… 162
Contents
ix
Definition of a Lean and Agile EA ……………………………………………….163
Lean and Agile Principles …………………………………………………………………………………. 165
Team-driven and Flexible: Agile Software Development ……………………..165
Learning from Mass Production: Lean Software Development ……………….174
Lean and Agile: Parallels and Differences ……………………………………….180
Building Block 1: Get Rid of Waste by Streamlining Architecture Processes ………………………. 182
The Seven Wastes of EA …………………………………………………………..183
Value Stream Analysis Tools for EA …………………………………………….193
Transition to a Lean and Agile EA Organization ……………………………….203
Summing It Up: Assessment by the EA Dashboard …………………………….205
Building Block 2: Involve all Stakeholders by Interlocking Architecture Scrums ..205
An Agile EA Project ………………………………………………………………..206
Scrum Patterns for EA ……………………………………………………………..209
Summing It Up: Assessment by the EA Dashboard …………………………….215
Building Block 3: Practice Iterative Architecture Through EA Kanban …………..216
Agile EA Requirements Management ……………………………………………217
An EA Kanban Board Using TOGAF ADM …………………………………….222
Synchronization with Implementation Projects …………………………………230
Summing It Up: Assessment by the EA Dashboard …………………………….233
CHAPTER 8
Inviting to Participation: EAM 2.0 …………………………………………………. 235
A Primer on Enterprise 2.0 ………………………………………………………………………………… 237
Building Block 4: Participation in Knowledge ………………………………………………………….. 246
The Strategy Blog …………………………………………………………………..247
Collaborative Data Modeling: The ObjectPedia ………………………………..249
Weak Ties and a Self-Organizing Application Landscape …………………….251
Summing It Up: Assessment by the EA Dashboard …………………………….256
Building Block 5: Participation in Decisions ……………………………………………………………. 258
The Diagnostic Process Landscape ……………………………………………………………………….. 259
The Bazaar of IT Opportunities……………………………………………………261
Summing It Up: Assessment by the EA Dashboard …………………………….264
Building Block 6: Participation in Transformation …………………………………………………….. 265
Mashing Up the Architecture Continuum ………………………………………..265
The Change Management Microblog …………………………………………….270
Summing It Up: Assessment by the EA Dashboard …………………………….277
The Bottom Line: Inviting to Explore ……………………………………………………………………. 278
CHAPTER 9 The Next Steps: Taking Collaborative EA Forward ……………………………. 279
A Summary ………………………………………………………………………………………………….. 279
Getting Started with Collaborative EA …………………………………………………………………… 283
Interpreting the Organizational Attitude Toward Change ……………………..283
x
Contents
Motivate the Elephant …………………………………………………………….. 286
Direct the Rider ……………………………………………………………………. 288
Shape the Path ……………………………………………………………………… 290
Looking Ahead …………………………………………………………………………. 293
Appendix: The Bank4Us Staff ……………………………………………………………………………. 295
References …………………………………………………………………………………………………… 297
Index …………………………………………………………………………………………………………. 303
Acknowledgments
Writing a book is a strenuous journey. We are indebted to many people who helped us along the way.
Murali Padmanabhan, at the time coordinating the Tata Consultancy Services (TCS) learning and
development initiative, established our early contact to Elsevier India. Without his efforts the book
idea would never have taken off in the first place.
We are sincerely grateful to the TCS management, in particular to Krishnan Ramanujam and
Santosh Mohanty, for their motivation, support, and friendly eye toward the book. Hermann Klein and
Ingo Rosenstein, by their kind permission, made it possible for us to work on the book project.
Many thanks go to numerous colleagues at TCS, especially to Harish Iyer, Bernd Linowski, and
Ameya Vanjari. They not only listened to our continuous rambles about architecture; they also
provided many useful insights in return.
Ravindra Asundi, Beate Beering, Dirk Fiege, Bernd Linowski, and Gero Seifert took the trouble to
struggle through 180 pages of the half-finished book to uncover the structural weaknesses, and they
kindly and patiently pointed out how we could fix them. We are deeply grateful for the time they
invested, and the gentle yet effective feedback they gave.
Bhadresh Vyasa, Sandeep Karkera, and Vinu Jade dedicated their time to the project by allowing
us to interview them in depth about their experiences in various aspects of EA. Many thanks for that!
We are indebted to several eminent authors in our field, most notably John Zachman from Zachman
International, Jeanne W. Ross from the Center for Information Systems Research at the Massachusetts
lnstitute of Technology, and Steve Nunn and Andrew Josey from The Open Group for their kind
permission, backed by active support, to reprint some of their intellectual property in this book.
Craig Mullins and Wayne Eckerson reviewed the final manuscript, providing many useful comments and improvement proposals. Our heartfelt thanks also go to the editors at Morgan Kaufmann:
Rachel Roumeliotis, Andrea Dierna, and Robyn Day. You all effectively helped us through the tedious
exercise of writing and finishing this book on time.
Last but not least, our sincere gratitude goes to our wives. They willingly accepted the sight of
husbands brooding over their laptops on weekends. They agreed to family funds flowing into a writing
workshop in India instead of into long-deserved family vacations. Furthermore, they actively
supported our work in numerous ways, from discussions over proofreading to stepping in when we
(again) neglected our household duties in favor of an authors’ phone conference. Beate, Christiane,
and Deepali, we definitely owe you one.
xi
Intentionally left as blank
CHAPTER
Why Collaborative Enterprise
Architecture?
1
CONTENT
Reasons for This Book ………………………………………………………………………………………… 1
Goals and Benefits of Enterprise Architecture ……………………………………………………………… 4
Controlling IT Complexity ………………………………………………………………………………….. 6
Aligning Business and IT ………………………………………………………………………………….. 9
The Gray Reality: Enterprise Architecture Failures ………………………………………………………. 11
Between Success and Disappointment ………………………………………………………………… 12
Perspective: Between Bird’s-Eye View and Nitty-Gritty on the Ground …………………………….. 14
Governance: A Host of Directives, but No One Follows Them ………………………………………. 19
Strategy: Marathon or 100 m Run? …………………………………………………………………….. 21
Transformation: Between Standstill and Continuous Revolution ……………………………………. 23
Enriching EA by Lean, Agile, and Enterprise 2.0 Practices ……………………………………………… 25
How This Book Is Structured…………………………………………………………………………….. 28
Reasons for this book
Enterprise architecture (EA) is often projected as a multipurpose medicine that cures an enterprise
of all pains and problems. EA comes in different flavors—sometimes a marketing gimmick in management talks, sometimes a means to boast about knowledge of some framework or other, and sometimes
an academic research topic. As a consequence, there seems to be a mystical mist surrounding the field
of EA. This mist obscures the meaning and purpose of this field—not only for the naı¨ve observer but
also for the mature architect.
In our professional lives, we (the authors of this book) have approached EA from the ground up, coming
from the basic levels of IT and software architecture. When EA groups were established in our
organizations, we experienced both the benefits and the shortcomings of EA. When eventually taking over
enterprise archite …
Purchase answer to see full
attachment
How it works
- Paste your instructions in the instructions box. You can also attach an instructions file
- Select the writer category, deadline, education level and review the instructions
- Make a payment for the order to be assignment to a writer
- Download the paper after the writer uploads it
Will the writer plagiarize my essay?
You will get a plagiarism-free paper and you can get an originality report upon request.
Is this service safe?
All the personal information is confidential and we have 100% safe payment methods. We also guarantee good grades