Top positive review
Invaluable for non-technical managers of technical people!
on January 23, 2004
Confused about getting your message across to the geek next door? Confused even about what (s)he does? Wonder why it takes six months to change the color of a button on a web page, or how to get data from one part of your business to another? Then this book is for you!
Enterprise Architecture is not going to make you into a developer (and why would you want to be one, in the first place? For the pizza and sugar-filled drinks?) but the book provides a congent explanation of the tasks that should go behind the development of enterprise-wide systems. This is of particular value if your work requires that you interact with architects and technical leads - you can gain a solid understanding of their concerns, the technical pressures with which they live, and their goals.
Of course, there's the caveat: the book describes ideal development, or at least what its authors believe to be ideal development of large-scale systems. Too many of my experiences have been in businesses that would have profited from their CTOs having read Enterprise Architecture - perhaps if more do, there will be fewer late nights!
I give this book 5 stars as a review, and as a value to the manager. Were I in the trenches, I might reconsider - the work concentrates on breadth, not depth. To the authors' credit, of course, they make that fairly clear from the start, and there are guidelines as to where to search for more. Who knows how long they'll last, or how long this book will remain current, but for now, it's the best book I've found on the subject, and instead of using it to prop up a shaky table, I have it as reference when I'm speaking to engineers by phone!