1.

Describe 3 major steps of the database design process [15]

a. Conceptual Design
Once all the requirements have been collected and analyzed, the next step is to
create a conceptual schema for the database, using a high-level conceptual data
model. This phase is called conceptual design.

The result of this phase is an Entity-Relationship (ER) diagram or UML class diagram.
It is a high-level data model of the specific application area. It describes how
different entities (objects, items) are related to each other. It also describes what
attributes (features) each entity has. It includes the definitions of all the concepts
(entities, attributes) of the application area.

During or after the conceptual schema design, the basic data model operations can
be used to specify the high-level user operations identified during the functional
analysis. This also serves to confirm that the conceptual schema meets all the
identified functional requirements. There are several notations to draw the ER
diagram.

b. Logical Design
The result of the logical design phase (or data model mapping phase) is a set of
relation schemas. The ER diagram or class diagram is the basis for these relation
schemas.

To create the relation schemas is quite a mechanical operation. There are rules how
the ER model or class diagram is transferred to relation schemas.

The relation schemas are the basis for table definitions. In this phase (if not done in
previous phase) the primary keys and foreign keys are defined.

c. Physical Design
The goal of the last phase of database design, physical design, is to implement the
database. At this phase one must know which database management system
(DBMS) is used. For example, different DBMS's have different names for datatypes
and have different datatypes.

The SQL clauses to create the database are written. The indexes, the integrity
constraints (rules) and the users' access rights are defined.

Finally the data to test the database is added in. In parallel with these activities,
application programs are designed. The implementation of the programs can start
when the database is created and data has been added in.
2. Give the difference between the hierarchical model and the network model, relational &
object model [10]

HIERARCHICAL DATA NETWORK DATA MODEL

MODEL
In this model, to store data hierarchy In this model, you could create a
method is used. network that shows how data is
related to each other.
It implements 1:1 and 1:n relations. It implements 1:1, 1:n and also
many to many relations.
To organize records, it uses tree To organize records, it uses graphs.
structure.
Records are linked with the help of Records are linked with the help of
pointers. linked list.
Insertion anomaly exits in this model There is no insertion anomaly.
i.e. child node cannot be inserted
without the parent node.
Deletion anomaly exists in this There is no deletion anomaly.
model i.e. it is difficult to delete the
parent node.
It is used to access the data which is It is used to access the data which is
complex and asymmetric. complex and symmetric.
This model lacks data independence. There is partial data independence
in this model.

RDBMS OODBMS

Stands for Relational Database Stands for Object Oriented

Management System. Database Management
System.

Stores data in Entities, defined Stores data as Objects.

as tables hold specific
information.
Handles comparatively simpler Handles larger and complex
data. data than RDBMS.
 Entity type refers to the Class describes a group of
collection of entity that share a objects that have common
common definition. relationships, behaviors, and
also have similar properties.

RDBMS stores only data. Stores data as well as

methods to use it.

Data Independence from Data Encapsulation.

application program.
A Primary key distinctively An object identifier (OID) is an
identifies an object in a table. unambiguous, long-term
name for any type of object or
entity.

3. With the aid of a diagram, describe each component in DBMS structure [25]

The database system is divided into three components: Query Processor, Storage Manager,
and Disk Storage. These are explained as following below.
1. Query Processor:
It interprets the requests (queries) received from end user via an application program into
instructions. It also executes the user request which is received from the DML compiler.
Query Processor contains the following components:

DML Compiler –
It processes the DML statements into low level instruction (machine language), so
that they can be executed.

DDL Interpreter –
It processes the DDL statements into a set of table containing meta data (data about
data).

Embedded DML Pre-compiler –

It processes DML statements embedded in an application program into procedural
calls.

Query Optimizer –
It executes the instruction generated by DML Compiler.

2. Storage Manager:
Storage Manager is a program that provides an interface between the data stored in the
database and the queries received. It is also known as Database Control System. It maintains
the consistency and integrity of the database by applying the constraints and executes the
DCL statements. It is responsible for updating, storing, deleting, and retrieving data in the
database.
It contains the following components:

Authorization Manager –
It ensures role-based access control, i.e.,. checks whether the particular person is
privileged to perform the requested operation or not.

Integrity Manager –
It checks the integrity constraints when the database is modified.

Transaction Manager –
It controls concurrent access by performing the operations in a scheduled way that it
receives the transaction. Thus, it ensures that the database remains in the
consistent state before and after the execution of a transaction.

File Manager –
It manages the file space and the data structure used to represent information in the
database.

Buffer Manager –
It is responsible for cache memory and the transfer of data between the secondary
storage and main memory.
3. Disk Storage:
It contains the following components:

Data Files –
It stores the data.

Data Dictionary –
It contains the information about the structure of any database object. It is the
repository of information that governs the metadata.

Indices –
It provides faster retrieval of data item