FEDERAL POLYTECHNIC

BAUCHI
SCHOOL OF BUSINESS STUDIES
DEPARTMENT OF BUSINESS
ADMINISTRATION AND MANAGEMNT

ASSIGNMENT:

BY:
NAME: GLADYS ABUBAKAR MUSA
REG NO.: 24/153647 (STREAM A)

EED PRACTICAL
DATABASE

QUESTION:
EXPLAIN THE STEPS IN DATABASE DEVELOPMENT
LIFE CIRCLE IN DETAILS WITH REFERENCE.
DESIGN A SAMPLE DATABASE SYSTEM WITH AT
LEAST TEN (10) ENTITIES WITH THEIR
ATTRIBUTES, AND RELATIONSHIPS.

AUGUST, 2025
DATABASE DEVELOPMENT LIFE CYCLE (DDLC)
The Database Development Life Cycle (DDLC) is a structured
process for designing, developing, implementing, and
maintaining a database system to meet an organization's data
management needs. It ensures that the database is efficient,
secure, and aligned with business requirements. Below, I
outline the key stages of the DDLC in details.

1. REQUIREMENTS ANALYSIS: Identify the needs of users

Activities:
 Identify stakeholders and conduct interviews or
surveys.
 Document business rules and data requirements.
 Understand what kind of data will be stored and how it
will be accessed.

Deliverables:
 Requirements Specification Document
 Data usage scenarios
2. CONCEPTUAL DESIGN: Develop a high-level data model
independent of any specific database technology.

Activities:
 Build an Entity-Relationship Diagram (ERD).
 Define entities, relationships, and constraints.
 Ensure normalization principles are considered.

Deliverables:
 Conceptual Schema (ERD)
 Entity and attribute definitions
3. LOGICAL DESIGN: Translate the conceptual model into a
logical structure for a specific DBMS.

s
Activities:
Page | 1
  Convert ER diagrams to relational schemas.
 Apply normalization (1NF, 2NF, 3NF).
 Define primary keys and foreign keys.

Deliverables:
 Logical schema
 Normalized table structures
4. PHYSICAL DESIGN: Optimize storage and access of the
database for performance.

Activities:
 Define storage structures, indexing strategies, and
partitioning.
 Estimate storage needs and performance requirements.
 Consider backup and recovery processes.

Deliverables:
 Physical schema
 Index and access path specifications
5. IMPLEMENTATION: Create the actual database using the
chosen DBMS.

Activities:
 Write SQL DDL scripts to create tables and constraints.
 Insert initial data using SQL DML.
 Set up user roles and permissions.
Deliverables:
 Operational database
 SQL scripts
6. TESTING AND EVALUATION: Ensure the database
meets functional and performance requirements.
Activities:
 Perform unit testing on individual queries or
transactions.
 Conduct integration testing with applications.
 Test for concurrency, recovery, and security.

Deliverables:

Page | 2
  Test cases and test results
 Evaluation report
7. OPERATION AND MAINTENANCE: Monitor and maintain
the database system after deployment.
Activities:
 Monitor performance and fine-tune queries.
 Perform regular backups and ensure data recovery
processes.
 Apply patches and updates to the DBMS.

Deliverables:
 Maintenance logs
 Updated user manuals and documentation
8. DATABASE EVOLUTION (OR ENHANCEMENT): Modify
and extend the database to meet new requirements.

Activities:
 Modify schemas and update data models.
 Migrate data when changing systems.
 Introduce new features or support new data types.

Deliverables:
 Revised database version.
 Change documentation

Page | 3
 REFERENCES

Ramakrishnan, R., & Gehrke, J. (2003). Database Management

Silberschatz, A., Korth, H. F., & Sudarshan, S. (2020). Database

Connolly, T., & Begg, C. (2015). Database Systems: A Practical

Date, C. J. (2004). An Introduction to Database Systems (8th

Elmasri, R., & Navathe, S. B. (2016). Fundamentals of Database

Rob, P., & Coronel, C. (2007). Database Systems: Design,

Hoffer, J. A., Ramesh, V., & Topi, H. (2016). Modern Database

Page | 4
UNIVERSITY MANAGEMENT SYSTEM - DATABASE DESIGN
University Management System – Database Design
Entities, Attributes, and Descriptions
1. Student
student_id (Primary Key)
first_name
last_name
gender
date_of_birth
email
phone_number
address
program_id (Foreign Key → Program)

2. Course
course_id (Primary Key)
course_name
course_code
credit_hours
department_id (Foreign Key → Department)
3. Lecturer
lecturer_id (Primary Key)
first_name
last_name
email
phone_number
hire_date
department_id (Foreign Key → Department)
4. Department
department_id (Primary Key)
department_name
faculty_id (Foreign Key → Faculty)
5. Faculty
faculty_id (Primary Key)
faculty_name
dean_name
6. Program
program_id (Primary Key)
program_name
duration_years
Page | 5
 department_id (Foreign Key → Department)
7. Enrollment
enrollment_id (Primary Key)
student_id (Foreign Key → Student)
course_id (Foreign Key → Course)
semester
session
enrollment_date
8. Result
result_id (Primary Key)
enrollment_id (Foreign Key → Enrollment)
grade
remarks
9. Classroom
classroom_id (Primary Key)
building_name
room_number
capacity
10. Course_Schedule
schedule_id (Primary Key)
course_id (Foreign Key → Course)
lecturer_id (Foreign Key → Lecturer)
classroom_id (Foreign Key → Classroom)
day_of_week
start_time
end_time
Relationships
Relationship Description
Student → Program Many students are enrolled in one program
Program → Department Each program belongs to one department
Department → Faculty Each department belongs to a faculty
Course → Department Each course is offered by one department
Lecturer → Department Each lecturer belongs to a department
Student → Enrolment A student can enroll in many courses
Enrolment → Course Each enrollment links to one course
Enrolment → Result Each enrollment can have one result
Course Schedule → Course Each schedule is for one course
Course Schedule → Lecturer Each schedule has one lecturer
Course Schedule → Classroom Each schedule takes place in one classroom

Page | 6
Sample ERD Summary (Text Format)
Student (M) — (1) Program
Program (M) — (1) Department
Department (M) — (1) Faculty
Course (M) — (1) Department
Lecturer (M) — (1) Department
Student (M) — (M) Course through Enrollment
Enrollment (1) — (1) Result
Course (M) — (M) Lecturer through Course Schedule
Course Schedule (1) — (1) Classroom

ENTITY-RELATIONSHIP DIAGRAM (ERD)

Page | 7