# Exported by Aegisub 2.1.8 (built from SVN revision 4064) In this video we provide an overview of Information and Data Models. An information model is an abstract, formal representation of entities that includes their properties, relationships and the operations that can be performed on them. The main purpose of an Information Model is to model managed objects objects at a conceptual level, independent of any specific implementations or protocols used to transport the data. Data Models, on the other hand, are defined at a more concrete level and include many details. They are intended for software developers and include protocol-specific constructs. A data model is the blueprint of any database system. The figure illustrates the relationship between an Information Model and a Data Model. Information model proposals can be split into nine historical epochs. Network, Hierarchical, Relational Entity-Relationship, Extended relational, Semantic Object-oriented, Object-relational, Semi-structured Let us go over each one of these in the following slides. In a network model, a child can have more than one parent, and each record type points to each other with next, prior and direct pointers The figure shows the record types represented by rectangles in a CODASYL network. A collection of record types and keys form a CODASYL network or CODASYL database. To know more about this CODASYL network or CODASYL database. refer to the DB2 Fundamentals book. The hierarchical model organizes its data using a tree structure. The root of the tree is the parent followed by child nodes. A child node cannot have more than one parent, though a parent can have many child nodes. This is depicted in this figure. The first hierarchical database management system was IMS i.e. Information Management System released by IBM in 1968. It was originally built as the database for the Apollo space program to land the first humans on the moon. IMS is a very robust database that is still in use today at many companies worldwide. The relational data model is simple and elegant.
file:///D|/00_Raul_D/00_Work/ (1 of 2)1/9/2011 9:57:48 PM

however. an instance of a class.. The last decade has seen a substantial amount of work on semi-structured. This figure illustrates an example showing an Entity-Relationship i. the E-R model has found success as a tool to design relational databases.I/Transcripts/01_Information%20and%20Data%20Models... Thank you for watching.e. He proposed thinking of a database as a collection of instances of entities. object-relational mapping i. however.file:///D|/00_Raul_D/00_Work/_db2university..txt It has a solid mathematic foundation based on sets theory and predicate calculus and is the most used data model for databases The Object-Relational i.. For more videos like this.e.e. semantic and object oriented data models.e. Peter Chen proposed the entity-relationship data model. it treats every entity as an object i. XML is ideal to store semi-structured data. and hierarchical data models. Rather than being used as a model on its own. an E-R diagram that represents entities or tables and their relationships for a sample relational model. This was to be an alternative to the relational CODASYL. and a relationship as an inheritance.amentals%20I/Transcripts/01_Information%20and%20Data%20Models. In the mid 1970’s. Object oriented data models are popular in universities. an OR model is very similar to the relational file:///D|/00_Raul_D/00_Work/_db2university. ORM tools are available which allow a seamless integration of object-oriented programs with relational databases. please visit DB2University.txt (2 of 2)1/9/2011 9:57:48 PM . Object-Relational databases have the capability to store object relationships in relational form. This ends this presentation. but have not been widely accepted in the

Sign up to vote on this title
UsefulNot useful