Database Models :: essays research papers

In this paper I will be discussing the differences and similarities of the three database personates we have talked about in human body the Entity- race, Object mildew, and the UML modeling. prototypical lets look at the definition of the three models. The Entity- kind Model is utilize to visually represent data objects and is use for database programme. It is slow to understand which makes it easier to communicate the design to the end user. The form used in the ER model can easily be transformed into relative tables. (Information Technology Services ITS, 2004)Another database model we went over in class is the Object Model. There be three constructs to understanding the Object Models star of them being the Data Abstraction which is the process of condensing data atomic pile to its essentials. Another one is the Inheritance in the object model is the government agency of defining one class in terms of another. The third concept in the object model is the Encapsulation which is the concept of including processing or demeanour with the object instances defined by the class. Encapsulation allows code and data to be encase together. The third database model would be the UML model that stands for Unified Modeling oral communication used for writing software blue prints. The UML can be used to visualize, specify, construct, and document the artifacts of a software-intensive system. (Safari Tech Books Online, 2002, chap. 2)Some of the similarities in the database model are that all three can be used in the database design process in some way. In our previous class DBM 380 we used the ER model for our projects even from our preceding projects we can create the database model in an Object or UML model. Of the three database models I find that the Entity Relationship model was the easiest to create and explain to an end user it also transforms effortlessly into relationship tables which worked well in Access. The Object model and UML model be to be mor e of a language model than the ER model seems to be more for just databases although the Object model addresses both schedule and databases. The UML model is more for intense software programming such as Java programming it would allow you to visualize and document your programming travel before starting the code.