by Phuong H
In the article “The Essential Skills of Data Modeling,” the author mentions that “the purpose of database modeling is to capture reality” therefore, it is more important for designer to understand the business concept rather than focusing on designing the model. It is because they can have a really nice database model but the important is can it be used to answer a business question, like the author stated “a model that fails to represent reality is likely to fail at some point because a client’s question cannot be converted to SQL” (Watson, 2006). Furthermore, the way you represent the model is not important the key is that the model can capture the reality (Watson, 2006). The author also mentions a few errors that student usually make when they learning about database modeling: “not recognizing that an attribute is an entity, failing to generalize several entities as a single entity, not reading relationship both way, ignoring exceptions that result in a failure to represent reality” (Watson, 2006). The author proposed that integrating SQL while teaching database modeling will help the student learn better because they can see how SQL related to database modeling.
I learned how to design a database model in my accounting class and I agreed with the author that the most challenging in designing a model is to capture the business rules and its exception. It is really important to include the exception because without the exception, the model will fails to answer some of the business question. I also think that it is easier to draw out the model on paper before working on the software.
Richard, T. W. (2006). The essential skills of data modeling. Journal of Information Systems Education, 17(1), 39-41. Retrieved from http://search.proquest.com/docview/200134852?accountid=10357