Universal Data Modeling

Chapter 5. Logical Modeling and Document Model

A note for Early Release readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 5th chapter of the final book. The GitHub repo will be made active later on.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at @oreilly.com.

In previous chapters, you have learned that the data modeling process consists of three stages, conceptual, logical, and physical. The conceptual model is the bridge between the business users and the technical professionals. The logical model is the mathematical description of the model that lays the foundation for computer implementation. The physical model is the detailed blueprint of the computer implementation. You also learned how to collect business requirements from the business users and create the entity relationship model. These result in your conceptual data model, which paves the way for future works.

The first such work is logical modeling. In this stage, you will find the best logical representation of your model, and convert your conceptual model into this representation. The logical model is the interface between business requirements and the physical implementation, as well as the interface between natural language and computer binary code. It defines ...