Chapter
Database Design,
and Administration
Database Design
Process of creating a design for a database that will
support the enterprise’s mission statement and
mission objectives for the required database system.
Database Design
Main approaches include:
Top-down
Bottom-up
Inside-out
Mixed
Cont…
Database Design
Main purposes of data modeling include:
to assist in understanding the meaning (semantics) of
the data;
to facilitate communication about the information
requirements.
Building data model requires answering questions
about entities, relationships, and attributes.
Database Design
A data model ensures we understand:
- each user’s perspective of the data;
- nature of the data itself, independent of its physical
representations;
- use of data across user views.
Criteria to Produce an Optimal
Data Model
Database Design
Three phases of database design:
Conceptual database design
Logical database design
Physical database design.
Conceptual Database Design
Process of constructing a model of the data used in
an enterprise, independent of all physical
considerations.
Data model is built using the information in users’
requirements specification.
Conceptual data model is source of information for
logical design phase.
Logical Database Design
Process of constructing a model of the data used in
an enterprise based on a specific data model (e.g.
relational), but independent of a particular DBMS
and other physical considerations.
Conceptual data model is refined and mapped on to
a logical data model.
Physical Database Design
Process of producing a description of the
database implementation on secondary storage.
Describes base relations, file organizations, and
indexes used to achieve efficient access to data.
Also describes any associated integrity
constraints and secuirty measures.
Tailored to a specific DBMS system.
Three-Level ANSI-SPARC
Architecture and Phases of
Database Design