Universal Data Modeling

Chapter 9. Modelling within Enterprise Data Architecture

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 9th 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.

So far, the focus of this book is all on data modeling. You have learned about conceptual data modeling, which focuses on understanding data from a business point of view. The outcome of this stage is the business requirement documentation (BRD), which describes the current state of data across the organization and how data flows through the enterprise in each workflow. Its main goal is not technical design, but to explain data in terms of business meaning, rules, and workflows. Your data models are built on top of these business activities and their requirements of data.

Later, when you moved on to logical data modeling, you learned about CRUD operations, i.e., Create, Read, Update, and Delete, which are the fundamental actions performed on data. By identifying which systems and processes perform CRUD operations on each dataset, you begin to see how data exists across the enterprise. CRUD operations impact data modeling by defining the actions happening in the ...