Design and implementation of a web application for queue management.
This system allows users to select a service (e.g., utilities, banking), choose a location, and track their position in a service queue. The platform displays:
- E-ticket number
- User's position in the queue
- Number of people ahead
- Current ticket being served
Agents manage queues via an interface (e.g., move to next/previous client), and administrators access a backoffice dashboard to monitor all ongoing queues.
- Client: Beneficiary requesting services
- Agent: Service provider managing clients
- Admin: Administrator overseeing all queues
fig: use case diagram
- Select service
- Choose location
- Agents call next/previous client
- View ongoing queues and current ticket numbers
- Person
- Client
- Agent
- Admin
- Service
- Queue (FileAttente)
- Location
- A Service can have multiple Locations.
- A Queue is linked to one Service but can contain multiple Clients.
- Agents serve clients in a queue.
- Admins have a global view over all queues.
fig: relationships between main classes
- Frontend : Next.js 15, Tailwind CSS
- Backend: Spring Boot, MySQL, Spring Data JPA, Hibernate, RESTful API
- Clone this repository.
- Install required dependencies: Java, Maven, MySQL (MariaDB).
- Run
docker-compose up -d mariadbto start the MariaDB container. - Run
CREATE DATABASE IF NOT EXISTS queueManagementDB;in MariaDB before starting the project. - Run the project using
mvn spring-boot:run. - Access via
localhost:8080.
- Read
CONTRIBUTING.mdfor contribution guidelines. - To participate in Hacktoberfest, look for issues tagged with
hacktoberfestorgood first issue. - Please adhere to the
CODE_OF_CONDUCT.md.
MIT License, © sdley Souleymane DIALLO 2025
- Inspired by real-world queue management needs.
- Thanks to all contributors and the open-source community enthusuasts.
For questions or support, reach out via GitHub Issues or contact sdley Souleymane DIALLO.
