Here you will learn how to develop an attractive, easily readable, conceptual, business-oriented entity/relationship model, using a variation on the UML Class Model notation.
By way of background, an appendix provides a history of the two groups, revealing the sources of their different attitudes towards the system development process..
This book is a handbook to describe how to build models such as these.
The diagrams were at various levels of abstraction, and they were all rendered in the slightly modified version of UML Class Diagrams presented here.
David Hay is the author of Enterprise Model Patterns: Describing the World , a comprehensive model of a generic enterprise.
These adjustments are described in this book.
Designers have a different view of the world from those who develop business-oriented conceptual Data models, which means that to use UML for architectural modeling requires some adjustments.
The notation involved happens to be the one for class models in the Unified Modeling Language, even though UML was originally developed to support object-oriented design.
Here all modelers will receive guidance on how to produce a high quality (that is, readable) entity/relationship model to describe the Data architecture of an organization.
David Hay\'s objective is to finally bring these two groups together in peace.
This book has two audiences: Data modelers (both analysts and database designers) who are convinced that UML has nothing to do with them; and UML experts who don\'t realize that architectural Data modeling really is different from object modeling (and that the differences are important).
Here you will learn how to develop an attractive, easily readable, conceptual, business-oriented entity/relationship model, using a variation on the UML Class Model notation
