Team341's Car Rental Application!

This project is a Car Rental Application for Customers, Customer Service Representatives and System Administrators

Deployed URL: https://team341-soen341project-w2024-lm14y6tqc-soen341.vercel.app/

Description

1. Customers

• Browse vehicles
• Create, modify or cancel reservations
• Provide feedback (reviews)

2. Customer Service Representatives

• Manage check-in and check-out processes
• View existing reservations
• Handle reservations and payments

3. System Administrators

• Oversee vehicle and user management
• View existing accounts/reservations
• Create, modify or delete users/vehicles

This comprehensive system enhances efficiency and user experience in the car rental industry.

Team Members

• Hrag Bankian (40245363): Quality Control, Organizational Manager, Full Stack Developer
• Sevag Merdkhanian (40247912): Full Stack Developer
• Élian Gadbois-Roy (40208293): Meeting Secretary, Full Stack Developer
• Johnny Dang (40245598): Scrum Master, Full Stack Developer
• David Cohen (40130406): Full Stack Developer
• Harun Slahaldin Omar (40250981): Full Stack Developer

Built With

• Next.js
• React
• MongoDB

Usage Guidelines/Getting Started

Here is a list of steps to take to run the project.

• Install Git

• Clone this repository: In a folder on your computer, open a terminal (ex. Git Bash) and run this command:

   git clone https://github.com/egadb/Team341-soen341projectW2024.git
  

• Install pnpm

• Install all the dependencies

  pnpm install
  

• Now, go to the folder you clone the repo in, find the project folder (soen341-rentalapp) and run this command:

  pnpm run dev
  

• Open your localhost, and you're done!

Git Rules

This project uses standard version control practices. Contributors must create separate branches from main, relating to an already created Issue, work on their contribution, and submit detailed pull requests to merge their code.

Here are some branch guidelines:

• Make sure the branch you are working on is named after the Issue # and the title of the Issue for clarity.
• If there is a branch already created for the Issue you are working on, make sure to work on that branch. Make sure no one else is working on that branch to avoid conflicts. This is most applicable to updates you may want to make to an already approved PR, or a PR that is yet to be approved.

Here are some PR guidelines:

• Must fix any merge conflicts before submitting a PR.
• Title: Should mention the Issue # as well as the title of the Issue for clarity.
• Description: Should mention all significant changes, expected behavior of those changes, and how to test the changes.

PRs must be approved by 2 different team members. Members should only approve PRs after they have thoroughly tested the changes made in the PR.

Wiki

Here is a link to the project's wiki page