There will come a time when an organization needs to update their data. A conceptual model takes care
of this. The conceptual model is the first step, followed by the logical and physical models. It is a chance
to get all stakeholders involved and demonstrate what the finalized database will look like and how it will
work. In order to develop the model, requirements must be realized first; stakeholders can get involved
to determine what requirements must be met. The next step to fulfill the requirements of the proposal is
to create a logical model which includes not only the data, but their relationships as well. Stakeholders
can and should be involved in this stage as well. Finally, the physical model is laid out which is more
database specific and much closer to the final product. An example of this is updating a system for an
eCommerce site. If the site gets a ground-up redesign, all of the current data will need to be saved and
reapplied to the new model. There may be more new fields that are required, and new relationships as
well (Nalimov, 2021).
Bibliography
Nalimov, C. (2021, September 22).
What is a conceptual data model? With examples!
Retrieved from
gleek.io: https://www.gleek.io/blog/conceptual-data-model.html
