Data Modeling Essentials

by Graham Witt and Graeme Simsion

Book Overview

Data Modeling Essentials, Third Edition, covers the basics of data modeling while focusing on developing a facility in techniques, rather than a simple familiarization with "the rules". In order to... This description may be from another edition of this product.

• Format: Hardcover
• Language: English
• ISBN: 1576108724
• ISBN13: 9781576108727
• Release Date: December 2000
• Publisher: Coriolis Group Books
• Length: 480 Pages
• Weight: 1.85 lbs.
• Dimensions: 1.2" x 7.4" x 9.2"

Customer Reviews

COMPETENCY IN DATA MODELING

Once you have a basic understanding of your application development tool, it will be a lot easier to learn the principles of data modeling. Authors Graeme Simsion and Graham Wittdone have done an outstanding job in this book of helping IT professionals to acquire competency in data modeling. Simsion and Wittdone begin this book by covering the basics of data modeling. Next, the authors look at some fundamental techniques for organizing data. In addition, the authors present a top-down approach to data modeling, supported by a widely used diagramming convention. They also look at a particular and very important type of choice in data modeling. Then, they turn to the nuts and bolts of data: attributes and columns. The authors then look in detail at the technical criteria governing primary key selection. Next, they look at some of the more common alternatives and extensions, focusing on conceptual modeling. Then, they look at the critical data modeling issues in project planning and management, with the aim of giving you the tools to examine critically any proposed approach from a data modeling perspective. The authors continue by looking at a variety of techniques for gaining a holistic understanding of the relevant business area and the role of the proposed information system. Next, they cover the development and use of a repertoire of standard solutions that are a large part of practical data modeling. In addition, they then look at the most common situation and describe the transformations and design decisions that are needed to apply to the conceptual model to produce a logical model suitable for direct implementation as a relational database. The authors then review the inputs that the physical database designer requires in addition to the Logical Data Model; as well as, looking at a number of options available for achieving performance goals. Next, they look at three further stages of normalization: Boyce-Codd normal form (BCNF), fourth normal form (4NF), and fifth normal for (5NF). They then continue to look in a broad fashion at the business rules and then focus on the types of rules that are of particular concern to the data modeler. In addition, the authors look at some basic principles and structures for handling time-related data. Next, they look at how the requirements for data marts and data warehouses differ from those for operational databases. Finally, they look briefly at data management in general, and then discuss the uses of enterprise data models. With the preceding in mind, the authors have done an excellent job of showing how to develop enterprise data modeling. At the same time, the authors caution that "while enterprise data models can be powerful vehicles for promulgating new ideas, they may also stifle original thinking by requiring conformity."

Much more than just a new cover

Even if you already own the second edition, you should buy the third (or get your employers to buy it for you). (Putting this first for those people who don't want to read the whole review). I already owned the second edition - it is the most frequently borrowed book from the set that I keep on my desk. So why did I buy the new edition as soon as I could? Because it is new, and covers new stuff - like sixth normal form (which turned out to be very familiar), and the Object Class Hierarchy, which is the answer to a Corporate/Enterprise Data/Information Architect/Administrator's prayer (job title generator - for each pair, pick one - the titles may vary, but the job seems to stay the same!) After years of developing web pages, spreadsheets and documents, and trying to get people to use them, this structure finally brings it all together. It is tempting to dip into a book like this to look things up, or to explain something to someone else (it is very handy if someone wants to know what, exactly, you mean by 'fifth normal form' - just hand them the book open at the relevent section). But if you don't read the whole thing, then you risk missing all sorts of useful stuff that gets mentioned in passing (sometimes a passing remark, sometimes getting as much as a whole paragraph). For example, there is a very useful question to elicit important information from senior management, in chapter 10. (Go and read the book to find it!) I think that the chapter on Enterprise Data Management needs expanding. Preferably into a companion volume ('Enterprise Data Management Essentials' - any chance, gentlemen?) But that is just about my only caveat. The second edition is still the most frequently borrowed book on my desk - but only because I don't let this one out of my sight, and I have been making people buy their own copies. If you buy the book and disagree with me - feel free to come and tell me why at any DAMA conference!

Essentially the best reference for data modelling

The most valuable book I own about data modelling. Covers all the basics one needs to know if they are going to talk about data modelling and what it really means and what is involved. And if you are expected to actually do the data modelling, even better, it provides coverage on all the things you should include, or at least consider, as well as some insights on how you are going to show the value and importance of being able to model your data. Even a seasoned modeller like myself wants to refer to a solid piece of reference material to ensure I'm doing the right thing and that I'm not forgetting anything. I was very happy to see a section on Conceptual Data Modelling as I find myself spending more time in this space getting the business to recognise that 'they' own this model, and they should identify and define all their business attributes here. That way when the database, or data interface, needs to be built the logical model can be created using these conceptual models as a reference point... should be less argument on what that column in the database really means! So many more highlights... but maybe I'm just a fanatic about data... it's my coffee table book. Thanks Graeme and Graham.

THE Book on Data Modeling

Dr. Simsion's book is the absolutely best on Data Modeling and Database Design. The book is written in a language that is clear, concise and easy to grasp.The concepts are addressed in a sequence that makes them easy to understand.Several years ago, I learned Data Modeling using the 1st edition of this book.The second edition is even better.I highly recommend it for novices and experts alike.Marcelo Rocha DaSilva...

Pick the mind of a real database designer

I read this book casually at first, thinking that it would merely confirm what I knew, since I was finishing up a database certification program. So when it pushed me to think harder, I put it away. HOWEVER, I recently returned to the book after some experience with Paradox for DOS, and I now see the light. It took real work to get through the first two chapters--about three hours for me--but I am glad that I have revisited this book and can tell everyone to (1) get it if they are serious about database design and (2) finish the lessons, even if they seem difficult or if they don't serve up simple rules right away. Simsion makes you really think about data organization, something usually left by the side of the road in the rush to put up a system. At least with this book your database will have the best possible foundation.