Universal Data Modeling

Chapter 3. Requirement Gathering of Conceptual 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 3rd 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 [e-mail].

In the previous chapter, you were introduced to the Entity–Relationship (ER) model. You learned that an entity represents a real-world object or concept, an attribute describes its properties, a key uniquely identifies each instance, and a relationship defines how entities are connected. These concepts form the building blocks of data modeling, allowing you to represent complex business information in a structured and understandable way. You also explored how to describe these components using shorthand notations and visualize them through Entity–Relationship Diagrams (ERDs).

Understanding the theory behind the ER model is an essential first step. In this chapter, you will take a step further. You will start building it.

The first step in this modeling process is to build a team. A conceptual data model is a bridge between the business users and the technical professionals. These are two different groups. It is a joint effort to build this bridge. In order ...