E-Parking Solution

E-Parking Solution is a web application which allows users to instantly reserve, pay, book, and allocate a free (up-to-date) parking slot while driving to their destinations.

For this project, I had a Scrum approach due to each task taking an average of 2-3 weeks to complete and used Git and Gitlab for version control.

Programming Languages:

• Java
• JavaScript
• MySQL

Markup Languages:

• HTML
• CSS

Features:

• Register and login
• Three types of users
• View parking spaces and the distance to them using the Google Maps API
• Secure payment gateway
• Create Car Parks and Parking Spaces
• Google Maps API
• View/delete/update bookings
• Anti double-booking
• Pagination and sortation
• Submit a request to refund/update a booking to the parking owners
• View the request/message sent from the driver and vice versa from the parking owner
• View metrics for the Parking Owner
• View metrics for the Site Administrator
• Create parking owner accounts by the site administrators
• Being able to disable accounts
• And many more

Prerequisites:

• Spring Boot Framework 2.7.4
• MySQL Server 8.0.31
• Maven 3.8.1

Dependencies:

• Spring Security
• Spring JPA
• Spring Starter Web
• Thymeleaf
• JUnit testing
• Google Maps API
• MySQL Connector
• etc.

Presentation

Landing Page (Slide Show) :

Login Page :

Register Page :

• Address (?)

• Terms and conditions

Driver (normal user) :

Booking Page :

• Update Address

• Address Updated (along with the distances)

• Google Map with the pin points of the Car Parks (+sortation and pagination)

• Google Maps (driving mode directions triggered when pressed on the address)

• Inside of University of Leicester's Car Park

• Booking a Parking Space

• Trying to Double Book

• Anti-double Booking

• Payment Gateway

• Cards to Pay

• Card not Accepted

• Card Accepted

View Bookings :

• View Booking

• Contact the Parking Owner

• Message was Sent

• Inbox Driver

Parking Owner :

Manage Car Parks :

• Add a new Car Park

• View Parking Spaces

• Add Parking Spaces

Parking Owner Inbox :

• View Message

• Reply to Message

• Message was sent

Parking Owner View Bookings :

• Edit Booking

• Booking Updated

Parking Owner Statistics/Metrics :

Site Administrator :

Manage Accounts :

• Disable Account

• Editing Account (Password and Role)

• Account Updated

Create Accounts for Parking Owners :

Site Administrator Statistics/Metrics :

Extras :

ERD Diagram :

This ERD diagram represents the entities and relationships of the E-Parking Solution database.

The "users" table holds information about the users of the system, including their unique user_id, username, address, password, and role. The role column indicates whether the user is a driver, parking owner, or site administrator. This table is necessary to support the login, registration, and messaging functionality of the system.

The "car_park" table stores data about each parking facility, such as its unique car_park_id, name, address, whether it has disabled spaces, and the user_id of the parking owner who manages it. This table is necessary to support the parking space booking functionality of the system.

The "parking_space" table records details about each parking space within a car park, such as its unique parking_space_id, address, floor level, price, and the car_park_id to which it belongs. This table is necessary to support the parking space booking functionality of the system.

The "cards" table holds information about payment cards used for transactions. It includes a unique card_id, a flag for whether payment is accepted, card number, expiration date, and security code. This table is necessary to support the payment functionality of the system.

The "transactions" table stores data about each parking transaction, including the unique transaction_id, amount charged, card number used, start and end date/time, license plate of the car parked, receipt number, transaction status, date and time of transaction, and transaction type (e.g., booking or payment). It also contains foreign keys to the user_id, parking_space_id, and card_id associated with each transaction. This table is necessary to support the payment and booking functionality of the system.

Finally, the "messages" table records communication between users of the system. It includes a unique request_id, message text, date and time sent, and a subject line. It also contains foreign keys to the sender_id and recipient_id of the message. This table is necessary to support the messaging functionality of the system. Overall, this ERD diagram shows the relationships between the different entities in the E-Parking Solution database, and how they interact with one another to facilitate parking transactions and communication between users. In conclusion, the ERD diagram has been designed to support the various functionalities of the E-Parking Solution, including registration, login, messaging, parking space booking, payment etc. Each table and field has been carefully selected and designed to support the requirements of the system.

Use Case Diagram :

The Use Case Diagram presented above is a visual representation of how the E-Parking Solution can be used by its different types of users. The first user identified is the Driver, who is the primary user of the system. To use the E-Parking Solution, the Driver needs to first register on the platform and then log in. Once logged in, the Driver can view the available car parks and parking spaces, choose a parking space, and proceed to book it by entering details such as start and end time, license plate, etc. The Driver can then make the payment for the booking. The Driver can also view their transaction history and contact the Parking Owner for any queries related to their booking. Additionally, the Driver can access their inbox to view and reply to messages. The second user is the Parking Owner, who can also log in to the system. The Parking Owner has access to various features such as metrics/statistics for their Car Parks and Parking Spaces, and can perform CRUD operations for managing them. They can view the bookings made for their Parking Spaces and can refund or edit them if necessary. The Parking Owner can also contact the Driver for any queries related to their booking, and can access their inbox to view and reply to messages. The third user is the Site Administrator, who has overall control over the platform. The Site Administrator can view metrics/statistics for the entire system, create accounts for Parking Owners, and manage accounts across the platform. This includes disabling/enabling accounts for Parking Owners as necessary. In summary, the Use Case Diagram showcases the different types of users that the E-Parking Solution caters to and the functionalities that they can access. It highlights how the platform enables Drivers to easily book parking spaces and Parking Owners to effectively manage their Car Parks and Parking Spaces. The Site Administrator is responsible for ensuring the smooth functioning of the platform as a whole.