A Vehicle Service Management System is a database application designed to store, organize, and manage information related to customers, vehicles, service appointments, service jobs, mechanics, spare parts, and payments in an automobile service centre. The main purpose of the database is to maintain accurate service records, reduce duplication of data, provide quick access to information, and support efficient service-centre operations. For this project, the database should be designed according to the principles of the Third Normal Form (3NF), so that redundancy is minimized and data integrity is maintained. The first step in database design is to identify the major entities involved in the vehicle servicing process. The important entities are Customer, Vehicle, Service Appointment, Service Record, Mechanic, Service Type, Spare Part, Service Part, and Payment. Each entity represents a distinct real-world object or activity and is represented by a separate relational table. The Customer table stores information about vehicle owners. A suitable structure is: `CUSTOMER(Customer_ID, Customer_Name, Phone, Email, Address)` Here, `Customer_ID` is the primary key and uniquely identifies every customer. `Customer_Name`, `Phone`, `Email`, and `Address` contain the customer's personal and contact information. Customer information should be stored only once, even if the customer owns several vehicles. The Vehicle table contains information about vehicles registered with the service centre: `VEHICLE(Vehicle_ID, Customer_ID, Registration_No, Make, Model, Vehicle_Year, Vehicle_Type)` `Vehicle_ID` is the primary key, while `Customer_ID` is a foreign key referencing the CUSTOMER table. `Registration_No` can also be defined as a unique attribute because two vehicles should not normally have the same registration number. The relationship between CUSTOMER and VEHICLE is one-to-many because one customer may own multiple vehicles, while each vehicle belongs to one customer. The Service Appointment table records bookings made by customers for vehicle servicing: `APPOINTMENT(Appointment_ID, Vehicle_ID, Appointment_Date, Appointment_Time, Complaint, Appointment_Status)` `Appointment_ID` is the primary key and `Vehicle_ID` is a foreign key referencing VEHICLE. The attributes store the date and time of the appointment, the customer's reported problem, and the current status, such as Scheduled, Completed, Cancelled, or Pending. One vehicle can have multiple appointments over time. After an appointment, a service job can be created. The Service Record table stores information about the actual service performed: `SERVICE_RECORD(Service_ID, Appointment_ID, Mechanic_ID, Service_Date, Service_Status, Labour_Cost, Remarks)` `Service_ID` is the primary key.