This document outlines the database development process, beginning with data modelling which involves understanding the organization, objectives, data types, and entities of the database. It describes three levels of data modelling: conceptual, logical, and physical. Conceptual modelling analyzes requirements, logical modelling defines data and relationships, and physical modelling builds database objects. It provides an example of modelling a salon database, including identifying objectives like tracking customers and reservations, data types like text and images, and key entities and their attributes like customers with IDs, names, gender, and contact details. Entity relationships are also discussed, such as one-to-one, one-to-many, and many-to-many.

1. DATABASE DEVELOMENT PROCESS

2. DATA MODELLING
It is the first step in creating a database. You must first
understand the
– Organisation that requires DBMS
– Objective of the database
– The type or nature of data to be captured and managed
– The Entities of the database
– The entity relations of the database

3. DATA MODELLING
It involves the process used to define and analyse data requirements needed to support
the business processes. The levels or data modelling are;
 Conceptual data modelling:
– analysing the organisation to with stakeholders
– identifying entities in the organisation for database
– specifying the scope of the DBMS
 Logical data modelling
– Translate conceptual into data definitions
– Establishing entities and their attributes
– Defining entity relations

 Physical data modelling
– Building and organising logical models into database objects like tables, forms, etc.,
and defining usage of the DBMS

4. APPLYING DATA MODELLING
You may achieve this by deploying the divide and
conquer principle.
– Let us as take a case study of saloon that needs a
database management system to run its operations
– Consider any government institution/agency or
private organisation that you think will need a DBMS
to improve their service or operations

5. APPLYING DATA MODELLING
Case Study: Saloon Operations
1. Consider the specific things the DBMS is
supposed to do (Objectives)
– To keep records of customers
– To make reservation for customers
– To keep records of Products and Services
– To Keep records of Staff of the Saloon
– And so on

6. APPLYING DATA MODELLING
Case Study: Saloon Operations
2. The type or nature of information to keep
– The database
– text data,
– numbers,
– dates and
– images for
• Example: images of products and possibly services

7. Entities
An entity may be a physical object such as a house or a car or a person, an event
such as a house sale or a car service, or a concept such as a customer transaction
order.
An entity may be defined as a thing which is recognized as being capable of an
independent existence and which can be uniquely identified.
Entity and Attribute
 And entities attribute is a set of facts about that entity that uniquely identifies
it from in a database. For example the customer table for the saloon DBMS will
be:
–
–
–
–
–
–
CustomerID,
Surname,
OtherNames,
Gender,
Address,
TelephoneNumber,

8. Entity Relations
ONE – ONE
ONE – MANY
MANY – MANY