Information Modeling and Relational Databases: From Conceptual Analysis to Logical Design

Author: Terry Halpin
List Price: $59.95
Our Price: Click to see the latest and low price
ISBN: 1558606726
Publisher: Morgan Kaufmann (06 April, 2001)
Edition: Paperback
Sales Rank: 21,115
Average Customer Rating: 4.83 out of 5

Buy now directly from Amazon.com - Purchase this book, safely and securely from the largest book dealer on the Internet, Amazon.com

Customer Reviews

Rating: 5 out of 5
Brilliant
This book is nothing short of brilliant. I read this book, did the exercises, and can honestly say its the best and most clearly written software development book I have read to date.

I started knowing nothing about how to design a database, and came away as an expert.

Halpin should win an award for this book.


Rating: 5 out of 5
Best Book On Data I've Read
After having used ER modeling with extreme frustration, I finally decided to investigate something new. This is the bible for ORM, and ORM is just so far superior to ER for conceptual modeling, which I now realize is critical.

Conceptual modeling means modeling your data in a way that makes sense to everyone, from the business experts (who know nothing about databases) to the coders and DBA's. And ORM provides a logical, intuitive way to do this.

Once you've got a conceptual model, it's pretty straightforward to get an ER model, from which you can develop the logical databased design. In fact, MS Visio (forget which version) does this for you.

The reason ER fails is that it cannot model data in a stable way. It still has a place, but ORM is so much more powerful, scalable, and stable.

And not only will you learn about ORM (he has great exercises to help practice), but you will learn a lot about data in general.

This is the best technical/developer/software engineering book I have ever read.


Rating: 5 out of 5
It opened a whole new "way of thinking".
This book is a masterpiece. ORM as a concept is so powerful. I have been doing Software Design for about 6 years now, and I always felt that there was a conceptual gap between writing use cases and doing software analysis and design from them. It needed an experienced designer in order to make a jump from use cases to analysis & design. (Even then the business facts would be missed out or simply be wrong, that would show up as bugs later on). I was on the lookout for "something" that helps me in real "industrial strength" software. ORM's fact oriention is a real supplement (and enhancement) to object orientation.

Similar Products

· Inside Relational Databases
· Data Model Patterns: Conventions of Thought
· Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design, Second Edition
· Data Modeler's Workbench: Tools and Techniques for Analysis and Design

Return To Main Computer Book IndexSearch Our Entire Computer Book Catalog