by Penny P
In the article that I read, it said that when you start working on data modeling you’re eventually working on something that will lead to database design. Before data modeling become popular, some people saw data administration and information groups as obstacles because it slowed down development. However, companies soon came to the conclusion that database models can actually serve as framework for new applications to be designed. New applications get created for different tasks while the old ones get integrated with the new.
The idea of data modeling is basically an abstract representation of real objects/environments as a database with a series of models is designed around it. Data modeling is used to increase the understanding of a business problem and identify the components. The first step to data modeling is to collect data and review the procedures and practices of the company. By learning about the data, it helps the designer identify and define the entities and their relationships; this is known as the conceptual model. After the conceptual model is created, it gets transformed into a logical data model where the data gets more specific and can describe the attributes for the entities.
I think this article was helpful because it explains why it is important to understand the data that is presented before doing the actual data modeling. You need to figure out how the entities connect with each other in their relationships. It was also cool to know that if the data modeling is done correctly, it could be used as a framework or template for future models. I guess the best type of modeling is the one where you can add on to it in the future without affecting the performance of entire model.
Weldon, J. L. “A Career in Data Modeling. Taking Up-front Time to Organize a Database Model Can save Time during Applications Development.” BYTE 1 June 1997: 103. Factiva. Web. 13 Jan. 2012.