Why this is in my collection

From the publisher:

Data Model Patterns: A Metadata Map not only presents a conceptual model of a metadata repository but also demonstrates a true enterprise data model of the information technology industry itself. It provides a step-by-step description of the model and is organized so that different readers can benefit from different parts. It offers 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.) and presents several concepts that need to be addressed by such t

Highlights

  • A data model of the IT industry itself — Hay turns the modeling lens back on its own discipline and builds an enterprise model of information technology's artifacts: entities, attributes, programs, databases, requirements; the boldest possible demonstration that everything, including modeling, can be modeled.
  • Metadata is just data whose subject is data — the book dissolves the mystique around metadata repositories by modeling them with ordinary entity/relationship discipline; the conceptual foundation under every model repository that model-driven data-engineering tooling instantiates.
  • A repository model is the precondition for generation — once models, mappings, and rules are themselves stored as structured data, transformations over them (validation, comparison, code generation) become queries and programs; this book maps the data structures a data engine runs on.
  • The Zachman framework given a backbone — Hay organizes the map along the framework's perspectives, showing how business-view concepts trace down to implementation-view artifacts; the traceability spine that lets a change in the conceptual model propagate to generated code.
  • Row-two/row-three discipline: business model vs system design — keeping the business's view and the designer's view as distinct, mapped layers is exactly the logical/physical separation that makes solutions regenerable across platforms.
  • Even meta-models obey the same patterns — party, document, activity structures reappear one level up, in the model of models; pattern density goes all the way down, which is why a generic modeling metamodel is feasible at all.
  • Written before its market existed — in 2006 few needed a rigorous metadata map; in the age of catalogs, lineage tools, and model-driven generation, this is the reference model the industry keeps reinventing pieces of.

Highlights on this page are generated with the help of AI.