Average Reviews:
(More customer reviews)This book is great stuff for Enterprise Architects. The discussion of Zachman is better than any of the Zachman Institues articles. The explanation of the value of architectural meta-models is excellent.
On the down side, the meta-models presented are very good EXCEPT that the author still presents data as being a part of an application. Surely 20 or so years after James Martin we are past that. Applications with their own data schemata are to be avoided and suppressed, rather than endorsed.
If your are a "real" Enterprise Architect, then this is book indispensable, but review all of the meta-models carefully to insure that they comply with your particular religion.
Click Here to see more reviews about: Data Model Patterns: A Metadata Map (The Morgan Kaufmann Series in Data Management Systems)
In recent years, companies and government agencies have come to realize that the data they use represent a significant corporate resource, whose cost calls for management every bit as rigorous as the management of human resources, money, and capital equipment. With this realization has come recognition of the importance to integrate the data that has traditionally only been available from disparate sources. An important component of this integration is the management of the "metadata" that describe, catalogue, and provide access to the various forms of underlying business data. The "metadata repository" is essential keeping track both of the various physical components of these systems, but also their semantics. What do we mean by "customer?" Where can we find information about our customers? After years of building enterprise models for the oil, pharmaceutical, banking, and other industries, Dave Hay has here not only developed a conceptual model of such a metadata repository, he has in fact created a true enterprise data model of the information technology industry itself.* A comprehensive work based on the Zachman Framework for information architecture-encompassing the Business Owner's, Architect's, and Designer's views, for all columns (data, activities, locations, people, timing, and motivation)* Provides a step-by-step description of model and is organized so that different readers can benefit from different parts* Provides a view of the world being addressed by all the techniques, methods and tools of the information processing industry (for example, object-oriented design, CASE, business process re-engineering, etc.)* Presents many concepts that are not currently being addressed by such tools - and should be
