or go to full-text search page →

Search

Search IconIcon to open search

Physical Data Model: Bottom-Up Approach

Last updatedUpdated: by Simon Späti · CreatedCreated: · 1 min read · growing Note status Growing. Worked on quite a bit, still rough. Expect bullets, gaps and views that update. Estimated from edit history · 4 sessions over 2 years · 192 words · How my notes grow Recent changes 8 months ago +0 / −3 words 2 years ago +3 / −3 words 3 years ago +1 / −1 words 3 years ago published · 119 words

The physical model involves implementing or generating the model in the target database system, taking into account the unique syntax variations of each database.


A straightforward progression from conceptual to physical data modeling.

One significant advantage of a conceptual model, especially in larger, more complex enterprise organizations, is its ability to provide a robust framework. This framework organizes both the logical and physical models in a manner that’s decoupled from the source systems.

Conversely, the bottom-up approach starts with an analysis of existing data sources. This can include databases, spreadsheets, and various forms of structured and unstructured data. From this analysis, a physical data model is created, mirroring the current data storage and its interrelations.

Subsequently, this approach advances to development a Logical Data Model. This model represents business requirements, followed by a conceptual model that offers a high-level overview of the data. The bottom-up method proves especially useful when working with legacy systems or in scenarios where there is a lack of clear understanding of the organization’s data requirements.


Origin: Data Modeling – The Unsung Hero of Data Engineering: Modeling Approaches and Techniques (Part 2) | ssp.sh