CS2082 - Database Management Systems Laboratory

Requirement for the Lab:

Create the necessary tables, with sufficient attributes in each table. Use the SQL queries for
storing, manipulating and retrieving data based on various conditions.

List of Projects

Project no: 0 - Inventory Management System (IMS)

A DBMS-based Inventory Management System is required to store and manage inventory

details, supplier information, and transaction records systematically.

Problem Description

Businesses often struggle with managing inventory efficiently, leading to problems such as
overstocking, stockouts, and inaccurate records. A DBMS-based Inventory Management
System is required to store and manage inventory details, supplier information, and
transaction records systematically.

System Requirements
The database should support the following functionalities:

1. Product Management
o Store details of products (Product ID, Name, Category, Description, Price,
Quantity in Stock).
o Allow adding, updating, and deleting product records.
2. Supplier Management
o Maintain supplier details (Supplier ID, Name, Contact Information, Address).
o Associate suppliers with products.
3. Stock Transactions
o Record stock purchases and sales.
o Update stock levels automatically after transactions.
4. Order Management
o Track customer orders (Order ID, Customer Name, Date, Total Amount).
o Link products to orders with quantity and price details.
5. Reports and Queries
o Generate inventory reports (low stock alerts, fast-moving products).
o Retrieve transaction history for auditing.

Database Schema (Basic Tables)

1. Products (ProductID, Name, Category, Price, QuantityInStock)

2. Suppliers (SupplierID, Name, Contact, Address)
3. Stock_Transactions (TransactionID, ProductID, Type (Purchase/Sale), Quantity,
Date)
 4. Orders (OrderID, CustomerName, Date, TotalAmount)
5. Order_Details (OrderDetailID, OrderID, ProductID, Quantity, Price)

Expected Outcome

A functional inventory management database that efficiently stores and retrieves

inventory data, ensures real-time stock updates, and allows businesses to maintain accurate
inventory records.

Project no: 1 - Hospital Management System (HMS)

Design and implement a Database Management System (DBMS) for a Hospital Management
System to efficiently manage patient records, doctor details, appointments, and billing
information.

Problem Description
Hospitals deal with large volumes of patient data, doctor schedules, and medical records
daily. Manual handling of these records can lead to inefficiencies, errors, and delays in patient
care. A DBMS-based Hospital Management System is needed to store, manage, and retrieve
patient, doctor, and appointment information systematically.

System Requirements
The database should support the following functionalities:

1. Patient Management
o Store patient details (Patient ID, Name, Age, Gender, Address, Contact,
Medical History).
o Maintain records of admitted and outpatient patients.
2. Doctor Management
o Store doctor details (Doctor ID, Name, Specialization, Contact, Availability).
o Assign doctors to patients based on specialization and availability.
3. Appointment Scheduling
o Record patient appointments (Appointment ID, Patient ID, Doctor ID, Date,
Time, Status).
o Allow patients to book, modify, or cancel appointments.
4. Medical Records Management
o Maintain medical history, prescriptions, and test reports for patients.
5. Billing and Payment
o Store billing details (Bill ID, Patient ID, Treatment Cost, Payment Status, Date).
o Generate invoices for patients based on treatments and services provided.
6. Reports and Queries
o Generate reports on patient admissions, doctor schedules, and billing records.
o Retrieve medical history for better diagnosis and treatment.

Database Schema (Basic Tables)

 1. Patients (PatientID, Name, Age, Gender, Address, Contact, MedicalHistory)
2. Doctors (DoctorID, Name, Specialization, Contact, Availability)
3. Appointments (AppointmentID, PatientID, DoctorID, Date, Time, Status)
4. Medical_Records (RecordID, PatientID, DoctorID, Diagnosis, Prescription,
TestResults, Date)
5. Billing (BillID, PatientID, TotalAmount, PaymentStatus, Date)

Expected Outcome

A functional hospital management database that efficiently stores and retrieves patient and
doctor data, ensures smooth appointment scheduling, maintains medical records, and
streamlines billing processes.

Project no: 2 - Bank Management System (BMS)

Design and implement a Database Management System (DBMS) for a Bank Management
System to efficiently manage customer accounts, transactions, loans, and employee records.

Problem Description
Banks handle large volumes of customer data, financial transactions, and loan processing
daily. Managing these records manually is prone to errors, inefficiencies, and security risks. A
DBMS-based Bank Management System is required to store and manage customer details,
accounts, transactions, and loan records securely and efficiently.

System Requirements
The database should support the following functionalities:

1. Customer Management
o Store customer details (Customer ID, Name, Address, Contact, Date of Birth,
Aadhar/PAN).
o Manage different types of accounts (Savings, Current, Fixed Deposit).
2. Account Management
o Maintain account details (Account ID, Customer ID, Account Type, Balance,
Open Date).
o Link customers to multiple accounts.
3. Transaction Management
o Record all transactions (Transaction ID, Account ID, Type
(Deposit/Withdrawal/Transfer), Amount, Date, Time).
o Ensure balance updates after each transaction.
4. Loan Management
o Store loan details (Loan ID, Customer ID, Loan Type, Amount, Interest Rate,
Duration, Status).
o Track loan repayment schedules and pending dues.
5. Employee Management
o Store employee records (Employee ID, Name, Role, Branch, Salary, Contact).
o Assign employees to manage customer accounts and loans.
 6. Reports and Queries
o Generate reports on account balances, transactions, and loan repayments.
o Retrieve transaction history for auditing and compliance.

Database Schema (Basic Tables)

1. Customers (CustomerID, Name, Address, Contact, DOB, Aadhar/PAN)

2. Accounts (AccountID, CustomerID, AccountType, Balance, OpenDate)
3. Transactions (TransactionID, AccountID, Type, Amount, Date, Time)
4. Loans (LoanID, CustomerID, LoanType, Amount, InterestRate, Duration, Status)
5. Employees (EmployeeID, Name, Role, Branch, Salary, Contact)

Expected Outcome

A functional bank management database that efficiently stores and retrieves customer and
account details, ensures secure transactions, manages loans effectively, and provides
accurate reports for banking operations.

Project no: 3 - Restaurant Management System (RAS)

Design and implement a Database Management System (DBMS) for a Restaurant

Management System to efficiently manage customers, orders, menu items, billing, and staff
records.

Problem Description
Restaurants handle various operations, including managing menu items, taking customer
orders, processing payments, and handling staff assignments. Manual handling of these
operations can lead to errors, delays, and inefficiencies. A DBMS-based Restaurant
Management System is required to store and manage restaurant data in a structured and
efficient manner.

System Requirements
The database should support the following functionalities:

1. Customer Management
o Store customer details (Customer ID, Name, Contact, Address).
o Maintain reservation details (Table Booking, Special Requests).
2. Menu Management
o Maintain a list of menu items (Item ID, Name, Category, Price, Availability).
o Categorize food items (Starters, Main Course, Desserts, Beverages).
3. Order Management
o Store order details (Order ID, Customer ID, Table Number, Order Status, Date
& Time).
o Link orders with menu items and track preparation status.
4. Billing and Payment
o Generate bills (Bill ID, Order ID, Total Amount, Payment Method, Status).
o Support multiple payment options (Cash, Card, UPI).
 5. Staff Management
o Store employee details (Employee ID, Name, Role, Contact, Salary).
o Assign staff to tables and kitchen duties.
6. Reports and Queries
o Generate reports on daily sales, most popular menu items, and employee
performance.
o Retrieve order history and customer details for loyalty programs.

Database Schema (Basic Tables)

1. Customers (CustomerID, Name, Contact, Address)

2. Menu (ItemID, Name, Category, Price, Availability)
3. Orders (OrderID, CustomerID, TableNumber, OrderStatus, DateTime)
4. Order_Details (OrderDetailID, OrderID, ItemID, Quantity, Price)
5. Billing (BillID, OrderID, TotalAmount, PaymentMethod, Status)
6. Employees (EmployeeID, Name, Role, Contact, Salary)

Expected Outcome

A functional restaurant management database that efficiently stores and retrieves customer
details, menu items, orders, and billing records to ensure smooth restaurant operations and
improved customer experience.

Project no: 4 - Salary Management System (SMS)

Design and implement a Database Management System (DBMS) for a Salary Management
System to efficiently manage employee salaries, deductions, bonuses, and payroll processing.

Problem Description
Organizations need a systematic way to process employee salaries, track deductions and
bonuses, generate payslips, and maintain payroll records. Manual handling of payroll can
lead to errors, delays, and compliance issues. A DBMS-based Salary Management System is
required to automate payroll processing and ensure accurate salary payments.

System Requirements
The database should support the following functionalities:

1. Employee Management
o Store employee details (Employee ID, Name, Department, Designation,
Contact, Bank Account).
o Maintain job details (Date of Joining, Work Status).
2. Salary Structure Management
o Store salary details (Salary ID, Employee ID, Basic Salary, Allowances,
Deductions, Net Salary).
o Support different salary structures based on job roles.
3. Payroll Processing
 o Calculate salaries based on basic pay, allowances, deductions (tax, insurance,
PF, etc.).
o Track overtime pay and bonuses.
4. Deductions and Bonuses
o Maintain records of deductions (PF, Tax, Insurance).
o Store bonus details for employees.
5. Payslip Generation
o Generate monthly payslips (Payslip ID, Employee ID, Month, Net Salary,
Payment Status).
o Maintain payroll records for audits and reporting.
6. Reports and Queries
o Generate reports on salary expenses, tax deductions, and employee payroll
history.
o Retrieve salary records for individual employees.

Database Schema (Basic Tables)

1. Employees (EmployeeID, Name, Department, Designation, Contact, BankAccount,

DOJ, WorkStatus)
2. Salary (SalaryID, EmployeeID, BasicSalary, Allowances, Deductions, NetSalary)
3. Payroll (PayrollID, EmployeeID, Month, Year, GrossSalary, NetSalary,
PaymentStatus)
4. Deductions (DeductionID, EmployeeID, PF, Tax, Insurance, OtherDeductions)
5. Bonuses (BonusID, EmployeeID, BonusAmount, Reason, Date)

Expected Outcome

A functional salary management database that efficiently processes employee payroll,

tracks deductions and bonuses, generates payslips, and maintains payroll records for
accurate and efficient salary management.

Project no: 5 - Pharmacy Management System (PMS)

Design and implement a Database Management System (DBMS) for a Pharmacy

Management System to efficiently manage medicines, suppliers, sales, and customer
prescriptions.

Problem Description
Pharmacies handle large volumes of medicines, supplier details, sales transactions, and
prescriptions. Manual record-keeping can lead to stock mismanagement, expired drugs, and
billing errors. A DBMS-based Pharmacy Management System is required to ensure accurate
inventory tracking, efficient sales processing, and proper prescription management.

System Requirements
The database should support the following functionalities:
 1. Medicine Management
o Store medicine details (Medicine ID, Name, Category, Manufacturer, Price,
Expiry Date, Stock Quantity).
o Track batch numbers and expiration dates.
2. Supplier Management
o Maintain supplier records (Supplier ID, Name, Contact, Address, Supplied
Medicines).
o Track medicine restocking and orders.
3. Sales and Billing
o Process medicine sales (Sale ID, Customer ID, Medicine ID, Quantity, Total
Price, Date).
o Generate bills and maintain payment records.
4. Prescription Management
o Store doctor prescriptions (Prescription ID, Customer ID, Doctor Name,
Medicines Prescribed, Date).
o Link prescriptions to sales transactions.
5. Stock and Expiry Management
o Track available stock and generate low-stock alerts.
o Identify expired medicines and remove them from inventory.
6. Reports and Queries
o Generate reports on sales, stock levels, expired medicines, and top-selling
medicines.
o Retrieve transaction history for auditing and compliance.

Database Schema (Basic Tables)

1. Medicines (MedicineID, Name, Category, Manufacturer, Price, ExpiryDate,

StockQuantity, BatchNumber)
2. Suppliers (SupplierID, Name, Contact, Address)
3. Sales (SaleID, CustomerID, MedicineID, Quantity, TotalPrice, SaleDate,
PaymentMethod)
4. Prescriptions (PrescriptionID, CustomerID, DoctorName, MedicinesPrescribed,
Date)
5. Billing (BillID, SaleID, TotalAmount, PaymentStatus, Date)

Expected Outcome

A functional pharmacy management database that efficiently stores and retrieves medicine
stock, supplier details, prescriptions, and sales records to ensure smooth pharmacy
operations and accurate inventory control.

Project no: 6 -Transport Management System (TMS)

Design and implement a Database Management System (DBMS) for a Transport

Management System to efficiently manage vehicles, drivers, routes, schedules, and ticket
bookings.
Problem Description

Transport companies need to efficiently manage vehicle details, driver assignments, route
schedules, ticket bookings, and maintenance records. Manual handling of these operations
can lead to scheduling conflicts, inefficient resource allocation, and revenue loss. A DBMS-
based Transport Management System is required to automate and streamline transport
operations for better efficiency and tracking.

System Requirements

The database should support the following functionalities:

1. Vehicle Management
o Store vehicle details (Vehicle ID, Type, Capacity, Model, Registration Number,
Status).
o Track vehicle maintenance and availability.
2. Driver Management
o Maintain driver records (Driver ID, Name, License Number, Contact, Assigned
Vehicle).
o Track driver schedules and performance.
3. Route and Schedule Management
o Store route details (Route ID, Start Location, Destination, Distance, Estimated
Time).
o Maintain transport schedules (Schedule ID, Route ID, Vehicle ID, Departure
Time, Arrival Time).
4. Ticket Booking System
o Store ticket booking details (Ticket ID, Passenger Name, Contact, Route ID,
Date, Fare, Payment Status).
o Track seat availability and cancellations.
5. Maintenance and Fuel Tracking
o Maintain vehicle maintenance records (Maintenance ID, Vehicle ID, Service
Date, Description, Cost).
o Track fuel consumption for efficiency monitoring.
6. Reports and Queries
o Generate reports on revenue, busiest routes, driver performance, and vehicle
maintenance.
o Retrieve travel history and ticket bookings for customer service.
Database Schema (Basic Tables)

1. Vehicles (VehicleID, Type, Capacity, Model, RegistrationNumber, Status)

2. Drivers (DriverID, Name, LicenseNumber, Contact, AssignedVehicle)
3. Routes (RouteID, StartLocation, Destination, Distance, EstimatedTime)
4. Schedules (ScheduleID, RouteID, VehicleID, DepartureTime, ArrivalTime)
5. Tickets (TicketID, PassengerName, Contact, RouteID, Date, Fare, PaymentStatus)
6. Maintenance (MaintenanceID, VehicleID, ServiceDate, Description, Cost)
Expected Outcome

A functional transport management database that efficiently manages vehicle details, driver
assignments, routes, ticket bookings, and maintenance records for seamless transport
operations.

Project No: 7- Student Database Management System (SDMS)

Design and implement a Database Management System (DBMS) for a Student Database
Management System to efficiently manage student records, course enrollments, grades, and
attendance.

Problem Description
Educational institutions need to manage vast amounts of data related to students, courses,
grades, and attendance. Manual record-keeping can lead to data inconsistencies, loss of
records, and inefficient retrieval of information. A DBMS-based Student Database
Management System is required to streamline administrative tasks and provide quick access
to student information.

System Requirements

The database should support the following functionalities:

1. Student Management
o Store student details (Student ID, Name, Date of Birth, Address, Contact,
Enrollment Year).
o Track student status (Active, Graduated, Dropped).
2. Course Management
o Maintain course details (Course ID, Course Name, Credits, Instructor).
o Link courses to students through enrollments.
3. Enrollment Management
o Manage enrollments (Enrollment ID, Student ID, Course ID, Semester, Year).
o Allow adding, updating, and deleting enrollments.
4. Grade Management
o Record grades (Grade ID, Student ID, Course ID, Semester, Grade).
o Calculate GPA based on enrolled courses and grades.
5. Attendance Management
o Track attendance (Attendance ID, Student ID, Course ID, Date, Status
(Present/Absent)).
o Generate attendance reports for each student.
6. Reports and Queries
o Generate reports on student performance, attendance records, and course
enrollments.
o Retrieve student academic history for counseling and advising.

Database Schema (Basic Tables)

 1. Students (StudentID, Name, DOB, Address, Contact, EnrollmentYear, Status)
2. Courses (CourseID, CourseName, Credits, Instructor)
3. Enrollments (EnrollmentID, StudentID, CourseID, Semester, Year)
4. Grades (GradeID, StudentID, CourseID, Semester, Grade)
5. Attendance (AttendanceID, StudentID, CourseID, Date, Status)

Expected Outcome

A functional student database management system that efficiently handles student records,
course enrollments, grades, and attendance, supporting better academic and administrative
management.

Problem no: 8 - Library Management System (LMS)

Design and implement a Database Management System (DBMS) for a Library Management
System to efficiently manage books, members, borrowing transactions, and due dates.

Problem Description
Libraries store a large number of books and need an efficient system to manage book records,
member details, borrowing transactions, and due dates. Manual record-keeping can lead to
lost books, overdue fines mismanagement, and inefficient tracking of book availability. A
DBMS-based Library Management System is required to automate book issuance, return
tracking, and fine management while ensuring seamless library operations.

System Requirements
The database should support the following functionalities:

1. Book Management
o Store book details (Book ID, Title, Author, Genre, Publisher, ISBN, Availability).
o Track book status (Available, Borrowed, Reserved).
2. Member Management
o Maintain member records (Member ID, Name, Contact, Address, Membership
Type).
o Track membership validity and borrowing limits.
3. Borrowing and Return Management
o Store borrowing details (Transaction ID, Member ID, Book ID, Issue Date, Due
Date, Return Date).
o Track overdue books and calculate fines.
4. Fine and Fee Management
o Maintain fine records (Fine ID, Member ID, Amount, Payment Status).
o Apply fines for overdue books and lost/damaged books.
5. Reports and Queries
o Generate reports on book availability, borrowed books, overdue books, and
member activity.
o Retrieve borrowing history of a member or a specific book.
Database Schema (Basic Tables)

1. Books (BookID, Title, Author, Genre, Publisher, ISBN, Availability)

2. Members (MemberID, Name, Contact, Address, MembershipType, ExpiryDate)
3. Borrowing (TransactionID, MemberID, BookID, IssueDate, DueDate, ReturnDate,
FineAmount)
4. Fines (FineID, MemberID, TransactionID, Amount, PaymentStatus)

Expected Outcome

A functional library management system that efficiently handles book records, member
details, borrowing transactions, and fines, ensuring smooth library operations and easy
tracking of books.

Problem no:9 - Sales Management System (SMS)

Design and implement a Database Management System (DBMS) for a Sales Management
System to efficiently manage products, customers, sales transactions, and inventory.
Problem Description

Businesses need an efficient system to manage product stock, customer details, sales
transactions, and revenue tracking. Manual record-keeping can lead to inventory
mismanagement, inaccurate sales tracking, and revenue loss. A DBMS-based Sales
Management System is required to automate sales processing, maintain inventory records,
and generate financial reports for better decision-making.

System Requirements
The database should support the following functionalities:

1. Product Management
o Store product details (Product ID, Name, Category, Price, Stock Quantity,
Supplier).
o Track stock levels and generate low-stock alerts.
2. Customer Management
o Maintain customer records (Customer ID, Name, Contact, Address, Purchase
History).
o Support customer loyalty programs.
3. Sales Transaction Management
o Store sales details (Sales ID, Customer ID, Product ID, Quantity, Total Price,
Date, Payment Method).
o Track sales revenue and generate invoices.
4. Inventory Management
o Maintain inventory records (Stock ID, Product ID, Quantity Available, Restock
Date).
o Link suppliers to inventory restocking.
 5. Reports and Queries
o Generate reports on sales performance, top-selling products, revenue, and
inventory levels.
o Retrieve customer purchase history for personalized marketing.

Database Schema (Basic Tables)

1. Products (ProductID, Name, Category, Price, StockQuantity, SupplierID)

2. Customers (CustomerID, Name, Contact, Address, PurchaseHistory)
3. Sales (SalesID, CustomerID, ProductID, Quantity, TotalPrice, Date, PaymentMethod)
4. Inventory (StockID, ProductID, QuantityAvailable, RestockDate)
5. Suppliers (SupplierID, Name, Contact, Address, ProductsSupplied)

Expected Outcome

A functional sales management system that efficiently handles product stock, customer
details, sales transactions, and financial reports, ensuring better business operations and
revenue tracking.