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.
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).
David Hay's objective is to finally bring these two groups together in...
Here you will learn how to develop an attractive, easily readable, conceptual, business-oriented entity/relationship model, using a variation on th...