BOOKIT is a full-stack web application that enables customers to search for, book, and manage reservations at local restaurants. It also provides role-based dashboards for restaurant managers and administrators.
| Member | Role | Contribution Highlights |
|---|---|---|
| Indraneel Vishwas Sarode | Frontend | customer UI, Profile UI , customer booking, Home and restaurant pages, AWS and Vercel deployment |
| Vignesh Jetty Ravi | Frontend | manager ui, admin ui, integration with backend |
| Jahnavi Kedia | Backend | Customer and Admin APIs, User Profile APIs, Reviews APIs, Search and list restaurants APIs, Available Restaurants and timeslots APIs, Google Map Integration, Booking stats APIs, Database design, Swagger documentation |
| Shamathmika | Backend | Authentication, email confirmations, manager APIs, booking API, Categories APIs and MongoDB creation with mock data |
- Sprint Duration: 2 weeks
- Total Sprints: 5
- Tools Used: GitHub, Google Sheets, Figma, Zoom, Gmeet
- Communication: Regular standups and sprint retrospectives hybrid mode
Project Board (Backlog & Sprints)
GitHub Repository
- Architecture Diagram
- Class Diagram
- Activity Diagram
- DB Schema (Google Doc)
- MongoDB Sample Data
- Component Diagram
- Deployment Diagram
- Frontend deployed on Vercel
- Backend APIs deployed on AWS EC2
- Database: MongoDB
- Dockerized services for ease of deployment
- Sign up, log in, log out
- Search restaurants with filters (location, Zip, Name, Time, #People)
- Book and cancel reservations
- View profile and edit
- View Reservations
- View Review
- Leave reviews and ratings
- View restaurants on Google Maps
- Receive email confirmations
- Register and manage restaurant listings
- Add/update restaurant details, tables, time slots, images
- View and manage own listings
- Approve or reject new restaurant submissions
- Remove listings
- View analytics dashboard
- Sprint 1: Initial architecture, diagrams, wireframes, DB schema
- Sprint 2: Authentication system, basic frontend, backend setup
- Sprint 3: Restaurant view, search API integration, categories
- Sprint 4: Full booking flow, reviews, profile, cancellation, emails
- Sprint 5: Admin & Manager dashboards, CRUD APIs, AWS deployment
- Sprint Journal
Each sprint concluded with internal testing and code reviews. Features were verified against the user stories, and integration points between the frontend and backend were validated through test bookings and admin flows.