This book introduces the Unified Modelling Language (UML) and how it can be applied to database modelling and design. The authors describe how the artefacts provided by business modelling are used to establish system requirements, address issues that arise during the mapping of object models to data models and illustrate application of the UML diagrams and techniques through a recurrent case study
However, the book contains many errors and peculiarities. There is the occasional inane comment, e.g. 'It is important to have the database running at full speed all the time; this can be accomplished by having a well-designed database and taking advantage of specific DBMS properties. Running the database with the correct amount of storage helps keep the database running at its best' (p. 152)
Most annoying of all, however, is the proliferation of descriptions that explain nothing, e.g. 'After the intense mining of already captured information and using much of their own knowledge of database design and experiences building several other databases, the database designers make some decisions on how to build the database storage in table spaces. The team determines that there is a need to have five different table spaces ...' (p. 164).
This book is very poor for a UML book. The book's website is empty and does not supplement the book's content - it only contains a link to order the book and an email to contact the authors.