by Kevin S
As we prepare to take the next step in database design, it is important to relate the new material with what we have already learned. In the article “Logical Versus Physical Database Modeling”, authors Ryan Stephens and Ronald Plew do just that. They describe data modeling as “a link between business needs and system requirements”. They summarize the logical model deliverables as including the ERD, Business process diagrams, and user feedback documentation. Where as the deliverables for physical modeling includes server model diagrams and its feedback documentation.
The logical data model, which we have been creating, will be converted into a relational database model. This process is known as physical modeling. While it seems simple by definition, the requirements of the hardware and software also need to be met which can be a hassle. Choosing the correct systems for the database can be crucial in getting the right information to the right place.
This article is nice since it is like a bridge between the previous weeks chapters and this weeks chapter. The article is written with the total novice in mind, and is completely easy to read which is nice. But I do think that the authors could have implemented a bit more technical jargon into the article so those with an interest within the subject could be better relate.
Stephens, R. K., & Plew, R. R. (2001, March 14). Logical versus physical database modeling. Retrieved from http://www.developer.com/tech/article.php/641521/Logical-Versus-Physical-Database-Modeling.htm