DBMS - Part 3

Data Models
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Data Models
 Data Model:
 A set of concepts to describe the structure of a database,
the operations for manipulating these structures, and
certain constraints that the database should obey.
 Data Model Structure and Constraints:
 Constructs are used to define the database structure
 Constructs typically include elements (and their data
types) as well as groups of elements (e.g. entity, record,
table), and relationships among such groups
 Constraints specify some restrictions on valid data; these
constraints must be enforced at all times

Data Models
 Data Model Operations:
 These operations are used for specifying database
retrievals and updates by referring to the
constructs of the data model.
 Operations on the data model may include basic
model operations (e.g. generic insert, delete,
update) and user-defined operations (e.g.
compute_student_gpa, update_inventory)

Data Models
 An example of a user-defined operation could be
COMPUTE_GPA, which can be applied to a STUDENT object.
On the other hand, generic operations to insert, delete, modify,
or retrieve any kind of object are often included in the basic
data model operations.

Categories of Data Models







Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 12









 Conceptual (high-level, semantic) data models:
 Provide concepts that are close to the way many users
perceive data.
 (Also called entity-based or object-based data models.)
 Physical (low-level, internal) data models:
 Provide concepts that describe details of how data is stored
in the computer. These are usually specified in an ad-hoc
manner through DBMS design and administration manuals
 Implementation (representational) data models:
 Provide concepts that fall between the above two, used by
many commercial DBMS implementations (e.g. relational
data models used in many commercial systems).

 Conceptual data models use concepts such as entities, attributes,
and relationships.
 An entity represents a real-world object or concept, such as an
employee.
 An attribute represents some property of interest that further
describes an entity, such as the employee’s name or salary.
 A relationship among two or more entities represents an
association among the entities, for example, a works-on
relationship between an employee and a project.
 The entity–relationship model—a popular high-level
conceptual data model.

 Representational or implementation data models are
the models used most frequently in traditional
commercial DBMSs.
 These include the widely used relational data model,
as well as the so-called legacy data models—the
network and hierarchical models—that have been
widely used in the past.
 Data models represent data by using record structures
and hence are sometimes called record-based data
models.

 We can regard the object data model as an example
of a new family of higher-level implementation data
models that are closer to conceptual data models.
 A standard for object databases called the ODMG
object model has been proposed by the Object Data
Management Group (ODMG).
 Object data models are also frequently utilized as high-
level conceptual models, particularly in the software
engineering domain.

 Physical data models describe how data is stored as files in the computer by
representing information such as record formats, record orderings, and access paths.
 An access path is a search structure that makes the search for particular database
 records efficient, such as indexing or hashing.
 An index is an example of an access path that allows direct access to data using an
index term or a keyword.
 It is similar to the index at the end of this text, except that it may be organized in a
linear, hierarchical (tree-structured), or some other fashion.
 Another class of data models is known as self-describing data models.
 The data storage in systems based on these models combines the description of the
data with the data values themselves.
 In traditional DBMSs, the description (schema) is separated from the data. These
models include XML as well as many of the key-value stores and NOSQL systems
that were recently created for managing big data.

DBMS - Part 3

Uploaded by

Copyright:

Available Formats

DBMS - Part 3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DBMS - Part 3

Uploaded by

Copyright:

Available Formats

Data Models

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 12

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 21

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 22

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 23

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 24

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 2- 25

You might also like