Advanced Database Systems
THE DATABASE
DEVELOPMENT
PROCESS
Prepared by Sanie G. Bautista, MSIT
Learning Content
The Database Development Process
1. Database within Information Systems
Development
2. Database Development Process
3. Managing People Involved in Database
Development
Learning Objectives
At the end of the session, students are expected to:
• Describe the life cycle of a systems development
project, with emphasis on purpose of database,
analysis, design, and implementation activities;
• Explain the prototyping approach to database
and application development;
• Explain the roles of individuals who design,
implement, use and administer databases.
What is Database?
A Database is an organized collection of data,
often stored electronically, that can be accessed,
managed, and updated efficiently. A database is
only one component of an information system.
What is Information System (IS)
An Information System (IS) collects, processes,
stores, and distributes information.
5 Components of an Information System:
1. Hardware
2. Software
3. Data
4. People
5. Procedures
Components of an Information
System (IS)
1. Hardware – The physical devices (servers, computers, storage
devices).
Example: A school server that stores student records.
2. Software – Programs that process and manage the data.
Example: Microsoft Access, MySQL, Oracle.
3. Data – The most important component; raw facts and figures stored
in the system.
Example: Names, grades, product prices.
4. People – Users and IT staff who manage and use the system.
Example: Teachers entering grades, students checking
schedules.
5. Processes – The rules, methods, and steps for using the system.
Example: A step-by-step enrollment process in a school
database.
Example in real life:
In an online shopping platform:
• Hardware: Company servers, customer
smartphones
• Software: Shopping app and website
• Data: Product details, customer orders
• People: Buyers, sellers, IT team
• Processes: Add to cart → Checkout →
Payment → Shipping
Database Life Cycle (DBLC)
The Database Life Cycle is the step-by-step process of creating, using,
and improving a database.
Stages of DBLC:
1. Requirements Analysis
- Find out what information the organization needs and how it will
be used.
Example:
A school needs to record student grades, attendance, and fees.
2. Logical Design
- Create a blueprint of the database using Entity-Relationship (ER)
Diagrams.
- Organize data into tables, set primary keys, and remove
redundancy through normalization.
Example:
Create a “Students” table with fields like StudentID, Name, and
GradeLevel.
Database Life Cycle (DBLC)
3. Physical Design
- Focus on performance—how to make the database run faster and
handle large data efficiently.
Example: Choosing proper indexes so searches are faster.
4. Implementation and Loading
- Build the database using a DBMS (e.g., MySQL, Oracle) and add
the initial data.
Example: Enter all current students’ information.
5. Testing and Evaluation
- Check for errors and see if it works as planned.
Example: Test if the system correctly calculates grades.
6. Operation and Maintenance
- Use the database in real life and keep it updated.
Example: Add new students each year and update fee records.
Levels of Database Design
Databases can be viewed in three levels:
1. Notional/Conceptual Level – The big picture of the system (what
data is needed, not how it’s stored).
2. Logical Level – How data is structured in tables and relationships.
3. Physical Level – The actual storage and performance optimization.
Example:
● Conceptual: “We need a database for library books and borrowers.”
● Logical: Design tables for Books, Members, and Borrowing records.
● Physical: Decide storage format, indexing, and backup methods.
Steps in Designing a Database
1. Requirement Handling
– Define the purpose and goals of the database.
2. Identify Entities and Attributes
Entities = things we store data about (e.g., Students, Courses).
Attributes = details about each entity (e.g., Name, Age).
3. Declare Keys –
• Primary Key: Uniquely identifies each record.
• Foreign Key: Connects one table to another.
4. Establish Relationships
– Link tables together (one-to-one, one-to-many, many-to-many).
5. Testing
– Ensure the design works and avoids inconsistencies.
6. Data Input
– Add the actual data.
Steps in Designing a Database
Example:
For a Gym Membership Database:
• Entities: Members, Trainers, Classes
• Attributes: MemberName, ContactNumber, TrainerName,
ClassTime
• Relationships: A trainer can handle many members (One-to-
Many).
Centralized vs. Decentralized
Database Design
• Centralized Design – Used for small databases with fewer
entities. Everything is planned and controlled from one place.
Example: A small café’s inventory system.
• Decentralized Design – Used for large, complex databases
with many entities and relationships. Different parts are
designed separately and later integrated.
Example: A large hospital system with separate modules
for patients, billing, pharmacy, and staff.
People Involved in Database Development
• Database Administrator (DBA): Manages the database,
ensures security, backups, and performance.
• Database Designer/Data Modeler: Designs the database
structure and relationships between data.
• Application Developer/Programmer: Creates applications
that interact with the database.
• Business Analyst: Gathers requirements and ensures the
database supports business goals.
• System Analyst: Bridges the technical and business sides,
ensuring the database integrates with other systems.
Summary
• Databases power modern systems.
• Information Systems have 5 components: Hardware,
Software, Data, People, Processes.
• DBLC has 6 stages:
Requirements → Logical → Physical → Implementation →
Testing → Maintenance.
• Database design involves entities, attributes, keys, and
relationships.
• Centralized = Small systems.
• Decentralized = Large systems
Task
1. Give a real-life example of a system and describe its DBLC
stages.
2. Identify three entities and their attributes for a Hotel
Reservation System.
3. Explain when you would use a centralized database design
and when you would use a decentralized one.
THANK YOU FOR
LISTENING!