FREE Two-Day Shipping for students on millions of items. Learn more |
| ||||||||||||
Frequently Bought Together
Product Details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, read author blogs, and more.
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
66 of 73 people found the following review helpful:
1.0 out of 5 stars
Vague, shallow, difficult to apply. Worst case study ever in print.,
By
This review is from: An Introduction To Enterprise Architecture: Second Edition (Paperback)
This book provides a cursory treatment of a deep subject. At barely 250 pages of main body text--and they are small pages at that, set in a generous type--there is no room to go into detail on much of anything. You will learn, perhaps, what a dataflow diagram or an IDEF0 frame is, but you will certainly not learn how to create or manipulate them, or much about how to use them, or their relative strengths and weaknesses, beyond the casual sentence or two about any given model in this book. And, look, I love diagrams, but it seems like every third illustration is this book is a reprint or an absolutely trivial variation on the author's "EA Cube" overview diagram. You can see it on the front cover--it's not exactly as complicated as the human nervous system. Once or twice would have done it for me. Shallow? I slosh through deeper puddles on a rainy day.But the shining feature of this book is the "case study" of a company adopting the particular flavor of Enterprise Architecture that Scott Bernard is trying to sell, something called EA3. He follows this ficticious company through the entire course of the book, costing a substantial fraction of the already meager pagecount. What would you expect such a case study to entail, dear reader? Maybe some process diagrams, data entity schemas, architecture documents...you know, an ENTERPRISE ARCHITECTURE for the example company? Sadly, the joke is on us. None of this is forthcoming. The "case study" consists almost entirely of descriptions of meetings where everybody talks about the wonderful things they're going to do with this new enterprise architecture, followed by more meetings where everybody congatulates each other on the wonderful things they've just done thanks to enterprise architecture. Like the rest of the book, there is just no "there" there. Actual models? No room! Sample documents? No time! Any business school or MIS student who tried to hand in this pollyanna sales pitch as a "case study" would only get an F because the grade scale doesn't go to "G." Perhaps the only value in this book is that, if read critically, it will teach you a great deal about why "Enterprise Architecture" has such a poor reputation in certain sectors of industry today. I really think that a lot of EA is about self-aggrandizement on the part of IT professionals, who think the entire business should revolve around their pretty diagrams and three-ring binders. We in the IT community need to get our minds right: we are here to support and enable the business, not impede it or, worse, subordinate it to its tools. If something like Enterprise Architecture is good for business, then we need to find ways to do it that don't involve saying to the people we are supposed to be helping: "Wait! Stop what you're doing and redefine everything you do according to MY methodology!" Read the first five pages of the "case study" in this book to see the new CIO do EXACTLY THAT. He should have been laughed out of the boardroom.
3 of 3 people found the following review helpful:
3.0 out of 5 stars
Introduction; What's the next step?,
Amazon Verified Purchase(What's this?)
This review is from: An Introduction To Enterprise Architecture: Second Edition (Paperback)
Solid introduction to the field.As is appropriate for a first book it outlines the theory. When I finish it however, I'm going to be looking for something that can lead me through the next step; identifying the challenges and techniques to confront them. That's not this book.
2 of 3 people found the following review helpful:
5.0 out of 5 stars
Very Good Introduction to Enterprise Architecture,
By
This review is from: An Introduction To Enterprise Architecture: Second Edition (Paperback)
"Introduction to Enterprise Architecture" is a very good text for a student or experienced professional to start to understand this very complex topic. The more useful aspect of the book is how it shows you the required elements of any Enterprise Architecture, and how they fit together. That is the most important thing for any Enterprise Architect to learn. That is presented well in the book.In addition, there is a good summary of many of the most referenced EA Frameworks. The examples are good, especially, the appendices that walk you through the specific deliverable documents for several of the well known EA Frameworks. That alone, is well worth the price of the book.
Share your thoughts with other customers: Create your own review
|
|
Inside This Book
(learn more)
Key Phrases - Statistically Improbable Phrases (SIPs):
(learn more)
security plan, data dictionary, object library, documentation element, sequencing plan, executive team, work breakdown structure, physical data model, system data flow diagram, network inventory, logical data model, project requirements, future operating scenarios, technology infrastructure level, repository relate, key business services, documentation framework, technology operating environment, capital planning process, architectural alignment, investment business case, documentation artifacts, knowledge warehouses, other management processes, documentation methodology Key Phrases - Capitalized Phrases (CAPs): (learn more)
Enterprise Architecture, Management Plan, Strategic Plan, Chief Architect, Security Program, Key Term, Learning Objectives, Working Group, E-Government Plan, Home Architecture Analogy, Technology Infrastructure, Business Process, Case Study, Output Measure, John Zachman, Danforth Manufacturing Company, Business Level, Executive Committee, Service Bus, Component Performance Measure, Thompson Model, Alternatives Analysis, Enterprise Resource Planning, Steven Spewak, Vince Albright Browse Sample Pages:
Front Cover | Table of Contents | First Pages | Index | Back Cover | Surprise Me!
security plan, data dictionary, object library, documentation element, sequencing plan, executive team, work breakdown structure, physical data model, system data flow diagram, network inventory, logical data model, project requirements, future operating scenarios, technology infrastructure level, repository relate, key business services, documentation framework, technology operating environment, capital planning process, architectural alignment, investment business case, documentation artifacts, knowledge warehouses, other management processes, documentation methodology Key Phrases - Capitalized Phrases (CAPs): (learn more)
Enterprise Architecture, Management Plan, Strategic Plan, Chief Architect, Security Program, Key Term, Learning Objectives, Working Group, E-Government Plan, Home Architecture Analogy, Technology Infrastructure, Business Process, Case Study, Output Measure, John Zachman, Danforth Manufacturing Company, Business Level, Executive Committee, Service Bus, Component Performance Measure, Thompson Model, Alternatives Analysis, Enterprise Resource Planning, Steven Spewak, Vince Albright Browse Sample Pages:
Front Cover | Table of Contents | First Pages | Index | Back Cover | Surprise Me!
What Other Items Do Customers Buy After Viewing This Item?
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
Customer Discussions
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|
Listmania!
|
|
