Project-Based Learning (PBL) for DBMS

B. Tech- CSL0311
Prepared by – Dr. R.P. Sarang

1. Suggested PBL Topics for DBMS

Students can choose from the following real-world DBMS projects or work on the topics
allotted by the instructor:
1. Library Management System – Maintain books, borrowers, and transactions.
2. Student Enrollment System – Manage student admissions, courses, and fee
payments.
3. Hospital Management System – Store patient records, doctor schedules, and medical
history.
4. Online Food Ordering System – Track orders, customers, and restaurant inventory.
5. Employee Payroll Management – Manage employee details, salary, deductions,
overtime and bonuses.
6. Inventory Management System – Maintain stock levels, supplier details, and
purchase records.
7. E-Commerce Database – Store product information, customer details, orders, and
payments.
8. Hotel Booking System – Manage room reservations, customer details, and billing.
9. Vehicle Rental System – Keep records of rented vehicles, customers, and rental
payments.
10. Blood Bank Management System – Maintain donor, recipient, and blood stock
details.

2. Guidelines for DBMS PBL

General Guidelines
 The project should involve real-world database applications.
 The team must consist of 3-5 students working collaboratively.
 The database should follow Normalization principles (at least up to 3NF).
 Queries should include basic, aggregate, and join operations.
 The project should be implemented using SQL and a database management system
like MySQL, or Oracle.
 Students should use ER diagrams, relational schema, and SQL queries for designing
and implementing the database.
 Documentation: Each team must maintain a Project Report with ER diagrams,
relational schema, and SQL queries.
 Presentation: Each group will present their project, explaining design choices,
challenges faced, and solutions implemented.
 Originality: The project must be unique and plagiarism-free.
4. Documents Required for Assessment

Students should submit the following mandatory documents:

a. Mid-Term Submission – 24/Sept/2025

 Updated ER Diagram & Relational Schema
 Database Creation Queries (DDL – Create Table, Constraints, etc.)
 Sample Insert Queries (DML – Insert, Update, Delete)
 Basic SQL Queries (Select, Joins, Aggregate functions, etc.)
b. Project Proposal (Initial Submission) – 20/11/2025
 Title of the project
 Objective & problem statement
 Scope & expected outcomes
 ER Diagram & Relational Schema (Draft Version)
c. Final Project Report – 22/11/2025
 Cover Page & Table of Contents
 Introduction (Project Background, Objective, Scope, etc.)
 ER Diagram & Relational Schema
 List of Tables (Attributes, Data Types, Constraints)
 SQL Queries (Basic, Join, Aggregation, Subqueries)
 Screenshots of Database Implementation & Outputs
 Challenges & Solutions Faced
 Future Enhancements & Conclusion
d. Source Code & Database Dump – 23/11/2025
 SQL script file containing table creation, insert statements, and queries.
 Exported database dump (.sql file) for easy execution.
e. Presentation (Final Assessment) 24/11/2025 onwwards
 5-10 minute presentation explaining the project’s design, functionality, and
implementation.

5. Assessment Rubrics (Evaluation Criteria)

The project will be graded out of 100 based on the following rubrics:
Criteria Weightage Evaluation Parameters
Problem Definition 10% Clarity of problem statement, real-world relevance.
Database Design 20% Proper ER diagram, relational schema, normalization.
SQL Implementation 20% Correctness of table creation, queries, constraints.
Functionality & Queries 20% CRUD operations, Joins, Aggregate functions, Subqueries.
Project Report 10% Documentation clarity, formatting, completeness.
Presentation & Demo 10% Project explanation, live demonstration, Q&A.
Originality & Innovation 10% Unique features, problem-solving approach.
Total: 100 Marks
6. Steps to Be Followed by Students
 Phase 1: Project Planning (Week 1-2)
o Select a real-world problem and define the problem statement.
o Create a Project Proposal and get it approved by the instructor.
 Phase 2: Database Design (Week 3-4)
o Design the ER Diagram & Relational Schema.
o Normalize the database to 3rd Normal Form (3NF).
 Phase 3: Implementation (Week 5-7)
o Implement the database in MySQL/PostgreSQL/Oracle.
o Write SQL queries to create tables, relationships, and constraints.
 Phase 4: Query Development (Week 8-9)
o Implement basic and advanced queries including Joins, Subqueries, Aggregation.
o Perform data insertion and testing.
 Phase 5: Testing & Optimization (Week 10-11)
o Test the database for data consistency, integrity, and performance.
 Phase 6: Documentation & Submission (Week 12)
o Prepare the final project report and submit the database dump & source
code.
o Deliver a presentation and demo in front of evaluators.

7. Expected Final Outcome

By the end of the project, students should deliver:
Fully functional database with properly designed schema and optimized queries.
Well-structured project report containing ER diagrams, SQL scripts, and test results.
Live demonstration of how data is stored, retrieved, and manipulated using SQL
queries.
Enhanced understanding of how real-world databases are designed and managed.
 FORMAT OF PROJECT REPORT

Cover Page
 Title of the Project
 Submitted by (Names, Roll Numbers, Team Members)
 Department Name
 Institution Name
 Supervisor/Instructor Name
 Date of Submission

Table of Contents
 List all sections and subsections with corresponding page numbers.

1. Introduction
 Overview of the Project
o Brief introduction to the system being developed.
 Problem Statement
o Explanation of the real-world problem being solved.
 Objectives
o Define the goals of the project (e.g., efficient data management, automation,
accuracy).
 Scope
o What functionalities will be included/excluded in the project.
 Technologies Used
o Mention Database Management System (DBMS) (e.g., MySQL, PostgreSQL,
Oracle).
o Mention Backend (if applicable) (e.g., Java, Python, PHP).

2. System Analysis
 Existing System & Its Limitations
o Challenges faced in the current/manual system.
 Proposed System & Benefits
o How the new system overcomes existing limitations.
 Feasibility Study
o Technical Feasibility: Availability of tools and technologies.
o Operational Feasibility: Ease of use for end-users.
o Economic Feasibility: Cost-effectiveness of the project.

3. Database Design
3.1 Entity-Relationship (ER) Diagram
 Graphical representation of relationships between entities.
3.2 Relational Schema
 Tabular representation of all tables and attributes.
4. Implementation
4.1 Database Creation (DDL Queries)
 SQL scripts used for table creation with constraints.
4.2 Data Manipulation (DML Queries)
 Queries for Insert, Update, Delete operations.
4.3 Query Processing
 Basic Queries: Retrieve specific records.
 Aggregate Queries: COUNT, SUM, AVG, MIN, MAX.
 Join Queries: INNER JOIN, LEFT JOIN, RIGHT JOIN.
 Nested Queries & Views (if implemented).

5. Testing & Results

5.1 Test Cases
Test Case ID Test Scenario Input Expected Output Actual Output Status
TC01 Insert new student Alice, 21 Record Inserted Record Inserted Pass
5.2 Sample Outputs
 Screenshots of query execution and results.
 Screenshots of application interface (if applicable).

6. Challenges & Solutions

 Difficulties faced during implementation.
 How challenges were resolved.

7. Future Enhancements
 Additional features that could be implemented later.

8. Conclusion
 Summary of project outcomes and key learnings.

9. References
 Books, research papers, online articles, tutorials, and documentation followed
during the project.

10. Appendix (If Any)

 Additional SQL queries, database dump file, or any other relevant details.