The Enterprise Data Model: A framework for enterprise data architecture, 2nd edition Paperback – 7 May 2012

The Framework for Enterprise Data Architecture, 2nd Edition, by Andy Graham is a valuable read for any data professional. This book expresses its concepts in easy to read English prose without having to read through paragraphs of waffle.The book maps the Silk Road, Figure 36, ending at Damascus. Whilst I didn't experience any `Road to Damascus' revelations when reading this book; it is packed with important and useful material.Ralf Kimball still gets a mention on page 44 in the 2nd Edition as he did in the 1st version. I assume this is the German cousin of Ralph Kimball.The material contained within this book is worth £22 of any data professional's money.

I could illustrate how lamentably bad this book was by telling you that I read it in a day and learnt nothing; that it is 130 pages long, but rather than being a distillation of all that is really important to know about Enterprise Data Models it is still full of padding and waffle and 100 of the pages could be chopped; or that it rehashes tired old mantras like Data-Information-Knowledge-Wisdom or the Quality, Time, Cost triangle.But I won't do that. I'll simply put this question to you.Do you really think you can learn anything from an author who has no idea how to use a possessive apostrophe? (I wouldn't care, but this is the second edition and one of the reasons given for updating the first edition is to correct grammatical errors)

The book provides a useful discussion of data architecture and some basic ideas. It is rather based on the author's own experience than a wider review of the topic, so I was expecting more. For me it was rather superficial.

Great book for me, I know a bit about this subject but not much and I needed a good, comprehensive summary which this book does very well.

I found this book easy to read and understandable. I liked the no-nonsense style the author has chosen, with the occasional quotes, which makes it not only an informative, but also an enjoyable read. It's less about Data Modelling, instead, as the title already suggests, more about the framework as such.Recommendable.

The only thing is missing on this book is more visual examples, since the book is about a model, for this reason, I was expecting more models than definitions.

This book covers the high level overview of EDM. I recommend to those who wanted to just brush up topics at high level.

This author's writing style is direct and easy to understand. I've been struggling to find a clear, concise book on this topic. The diagrams are informative. It is a quick read- I was able to read the whole book in a few hours. I've recommended this book to the entire project team.

Im Kindle sind die Grafiken leider überhaupt nicht erkennbar.Der Inhalt ist auch etwas enttäuschend und nicht auf dem neuesten Stand.

When I received the advanced order email from Amazon, the blurb made the book sound like a worthwhile addition to my library, providing a simplified overview of data architecture in the same way that the excellent book by James Martin did in the early 1980's. Alas, whilst the premise of this book is sound and the content is reasonably informative and interesting, its execution leaves a lot to be desired. I hope that the next version of this book is professionally edited and proof-read as it will turn this book around from a 'should avoid' to a 'must have'.The book is littered with spelling and grammatical errors to the extent that they detract from the value of the text and leave one frustrated and annoyed. Pedant that I am, I got to the stage that, towards the end of the book, I was just looking for the errors and keeping a tally by page. The following two random examples are actually call-outs and one would think that they, at least, would be accurate. They are:"One of the key foundations stones of MDM is an enterprise data model to govern the use and structure of the organisations data." (Page 19)and"By making all software adhere to the enterprise data model, the business protects it's self from the impact of changes in technology." (Page 26)Interestingly, my copy of Word 2003 didn't pick up the errors either.In addition, the book includes random comments that are out of context (e.g. Page 3), has what in any other book would be a side-bar randomly inserted into the middle of the text (e.g. "Some thoughts on Data Quality" on Page 27), refers to incorrect Figures (e.g. Page 99), makes inappropriate use of humour (Page 106), and the examples with Widget Ltd don't show a clear progression of ideas. To cap it off, having earlier poked fun at some newspaper headlines as a way of demonstrating ambiguity, Appendix A shows diagrammatically two ways to parse the headline "Enraged cow injures farmer with axe" but the diagram uses the word "kills" instead of "injures".All of this points to what I find to be an exceptionally shoddy piece of workmanship where the author manages to commit just about every writing howler described in a Technical Writing How-to book. (For an example of how to properly write a book such as this, one should read "Business Rule Concepts", Third Edition, by Ronald G. Ross).To sum up, within the dross, there are a number of useful nuggets of information. But I just don't know whether they are sufficient to justify the cost of the book and the anguish that follows when one tries to read it.