Car Workshop Appointment System

01

Overview

The system addresses a common problem in workshops that still rely on first-come, first-served service. Unstructured scheduling can create crowded time slots, missed appointments, unclear service information, and extra work when bookings need to be changed or cancelled.

I developed a standalone C++ application that connects to a MySQL database. Customers can browse services and manage appointments, mechanics can view assigned work and update completion status, and administrators can manage the workshop's records and generate an annual summary.

Project scope

This is a console-based database application, not a website. XAMPP and phpMyAdmin were used as local development tools for the MySQL data.

02

Objectives

Build modular CRUD functions

Implement at least three modules that let users create, read, update, and delete the data relevant to their role.

Calculate customer payments

Total the prices of completed services and present tax and final payment values in a generated receipt.

Make service information accessible

Keep service names, prices, availability, and appointment details organized in one system.

03

Users and modules

Administrator

Add, view, update, and delete mechanic records
Add, view, update, and delete workshop services
View registered customers
View or delete appointments
Generate an annual performance summary

Mechanic

View assigned appointment information
Review customer plate, service, and date details
Mark completed service appointments
View and update profile information

Customer

Register and log in
Browse services and prices
Book or cancel an appointment
View appointment details and receipts
View and update profile information

04

System design

Structure chart showing customer and administrator modules — **Structure chart**Role-based modules and the operations available to each user.

Flowchart for login, administrator, mechanic, and customer actions — **System flowchart**The application flow from login through each role's tasks and logout.

Entity relationship diagram linking admin, service, appointment, customer, and mechanic tables — **Entity relationship diagram**Five MySQL tables connected through the central appointment record.

05

Database structure

AppointmentAppointment ID, service ID, mechanic ID, customer ID, service name, date, time, and status.

CustomerCustomer ID, vehicle plate number, name, password, address, phone number, and email.

ServiceService ID, service name, and price.

AdministratorAdmin ID, password, name, phone number, and email.

MechanicMechanic ID, name, specialization, and phone number.

06

Administrator workflow

Administrator menu with mechanic, service, customer, appointment, and reporting options — **Administrator menu**Central access to mechanics, services, customers, appointments, and reports.

Customer records displayed without passwords — **Customer records**Registered customer data is displayed while passwords remain hidden.

Annual summary showing appointments, sales, customers, popular services, completion rate, and monthly revenue — **Annual summary**Appointments, sales, customer count, popular services, completion rate, and monthly revenue.

07

Staff and mechanic workflow

Staff login screen offering administrator and mechanic roles — **Staff role selection**Staff continue as either an administrator or mechanic.

Mechanic menuAccess to assigned appointment information and mechanic profile details.

Mechanic appointment list with status update controls — **Appointment status update**Mechanics review assigned jobs and mark completed appointments by ID.

08

Customer booking workflow

Customer login screen with registration and back options — **Customer access**Existing customers log in; new customers can begin registration.

Customer menuBooking, appointment details, cancellation, and profile management.

Service selection menu listing engine, tire, brake, electrical, and cooling system services — **Service selection**Customers choose from engine, tire, brake, electrical, and cooling system services.

Engine service booking flow showing services, mechanics, date, time, and confirmation — **Booking flow**Select a service and mechanic, enter a date and time, then confirm the appointment.

09

Appointments, receipts, and profiles

List of dates with booked appointments — **Appointment dates**Customers choose a booked date to inspect its appointment details.

Completed appointment details and generated receipt with price, tax, and total — **Details and receipt**A completed appointment produces a receipt with price, tax, and total payment.

Customer profileCustomers can review and update their personal and vehicle information.

Exit screen thanking the user for using the system — **Session close**A clear confirmation marks the end of the application session.

10

C++ implementation

The implementation uses modular functions, global login state, MySQL result rows, control structures, and C-style query pointers. Input validation checks values such as vehicle registration numbers before records are accepted.

C++ global variables for MySQL results and logged-in user IDs — **Application state**MySQL handles and logged-in role identifiers.

C++ function declarations for administrator, service, customer, and login operations — **Modular functions**Operations are separated by entity and user role.

C++ MySQL query result processed as rows to build a monthly sales chart — **Result processing**Database rows feed the annual summary calculation.

C++ do-while selection logic for adding another mechanic — **Selection logic**Validated choices control repeated administrator actions.

C++ do-while loop continuation condition — **Loop control**A do-while condition keeps repeated tasks active until the user chooses to stop.

C++ switch statement routing administrator menu choices — **Menu routing**A switch statement maps administrator choices to functions.

C++ pointer and mysql_query code used to verify administrator credentials — **Database query pointer**A C-style string is passed to mysql_query for authentication.

C++ vehicle registration validation code — **Registration validation**Vehicle plate input is checked for empty, overlong, or incorrectly formatted values.

Console output showing invalid vehicle registration input and retry messages — **Error feedback**Invalid values produce specific messages and a chance to retry.

11

Constraints and next steps

01

Local development environment

XAMPP and phpMyAdmin are suitable for development and demonstration, but the current setup is not intended as a secured production deployment.

02

Data reliability

A production version would need stronger protection against data loss or corruption, plus backup and recovery processes.

03

Future improvements

The report proposes cloud-hosted infrastructure, customer rewards, and post-service feedback to improve scalability, reliability, and customer retention.

12

Project timeline

13

Links

Back to portfolio ikhwanuddinworks@gmail.com github.com/wanpenter

Source code and a full walkthrough demo video are coming soon.