team-project-codebrigade

Team Name: Codebrigade

Members:

• Aishwarya Ravi
• Sarinder Virk
• Supreetha Ajay Mariyappal
• Dharahasini Gangalapudi

Contributions:

• Aishwarya Ravi(mailto:aishwarya.ravi@sjsu.edu):

  • Designed database schema for the application and worked on RDMS(AWS RDS- MYSQL) set up.
  • Spring Boot Architecture set up for backend (Introduced controller, service, repository and mapper layers, persistence & domain classes)
  • Worked on ORM(Object Relational Mapping) set up.
  • Worked on Sprint Boot unit tests set up.
  • Designed and Implemented backend modules for the following:
    • Search Hotels module
    • Hotel Rewards account module
    • Enrolling as a new customer module
    • Edit/change reservation feature in My trips(Bookings) page
    • Delete/Cancel reservation feature in My trips(Bookings) page
    • Worked on Dynamic Pricing backend design (Introduced strategy pattern).
    • Implemented pricing strategy to see the changes in prices dynamically based on weekends, weekdays and holidays.
    • Implemented pricing strategy to see the changes in prices dynamically based on winter season.
    • Implemented pricing strategy to see the changes in prices dynamically based on room types, number of guests and rooms.
    • Introduced payment validations for booking module (Used Chain Of Responsibility pattern).
    • Introduced singleton pattern for validation & pricing handler instance creation.
    • Display of customer details in Admin page
  • Worked on Integration of Hotel rooms UI with backend.
  • Worked on Unit tests for Hotel controller.
  • Performed the role of Scrum master in Sprint 3 (March 28th - April 11th of 2022)

• Sarinder Virk:

  • initial AWS infrastructure setup
  • intial React app setup
  • initial Atlassian setup
  • scrum master role in Spring 1
  • Booking wizard setup (Step 1, 2, 3)
  • Step 2 accordian UI
  • integrate 'amenities' portion of the UI
  • add 'amenities' to 'hotels' api
  • integrate 'checkin/checkout dates' portion of the UI
  • Integrate reservation details page
  • unit tests

• Supreetha Ajay Mariyappal

  • Design(Wireframes) and UI Implementation of:
    • SignIn & SignUp screens
    • Choice of Login for Users and admin
    • Welcome screen with search bar
    • Edit reservation feature in My trips page
    • Delete/Cancel reservation feature in My trips page
  • Integration of Booking api with all the necessary post state maintained in reducers
  • Implemented redeeming of rewards feature in the payment workflow
  • Implemented pricing Strategy to see the changes in prices dynamically based on peak seasons
  • Performed the role of Scrum master in Sprint 2 (March 14th - 28th of 2022)

• Dharahasini Gangalapudi:(mailto:dharahasini.gangalapudi@sjsu.edu)

  • Developed Login and Signup using Amazon Cognito
  • Done UI implemntation for Search List page
  • Done UI implementation for rewards page
  • Worked on integrating Rewards UI with backend
  • Done UI implmentation for Customer List page and integrated that page with backend
  • Worked on database Cleanup
  • Performed the role of scrum master in Sprint 4 (April 14 - May 2nd of 2022)

Tech Stack:

• Front End : React JS
• Back End : Java
• Database: AWS RDS (MYSQL)
• Cloud Services: AWS (Cognito, CloudFront, S3, EC2, ELB, CodePipeline)
• UX: Framer

GitHub Repo

Design Decisions

• MVC pattern (Spring boot) for backend
• Front end uses 'react-redux' which updates the screen upon changes - as per Observer pattern
• Strategy pattern for Dynamic pricing
• Chain of Responsibility pattern for booking and payment (Credit Card) validations
• Singleton pattern for retrieving Validation handler

Project Folder Description

• wireframes - contains the wireframes of the UI screens planned.
• react - contains the frontend apps codebase in react.
• hotel-ws - contains the backend apps codebase a maven project.

Scrum Meeting

We follow bi-weekly meetings on Mondays and Thursdays, each sprint starting from Mondays and lasting for two weeks. At the end of each sprint we had a retrospective meeting to look back on what went wrong and what went well. The retrospective captured in the Jira project-pages (attached screenshot of each sprint's retro document)

JIRA Project Board

Feature Set:

• Sign up and Sign in (Separate flow for Hotel Employees and customers)
• Enrolling a new customer
• Choice of Login for Users and admin
• Welcome screen with search bar to Search Hotels
• Manage Rewards account - MyRewards screen
• Hotel rooms Booking & all validations - Booking flow
• Amenities selection while booking
• Redeem rewards
• View all bookings (My trips page for customers)
• Edit & Cancel reservations/bookings
• Dynamic Pricing (based on weekdays, weekends, holidays, customer loyalty, summer & christmas seasons and no. of rooms, guests, and room types)
• Admin workflow - List of customers registered and their details

XP Core Values

Communication:

We have a clear communication among us and the bi-weekly scrum calls helped majorly and if any person was not able to attend the same, they provided offline status update through Whatsapp. We worked together to ensure each one of us is aware of where the project stands and what is their responsibility as a team member.

Simplicity:

We periodically ensure we are doing what is asked for and no more. We strive to keep the code base simpler and easier to be understood by everyone. We insert comments in places which need explanation. We refactor the code as and when needed to ensure the goal of simplicity is met and thereby debugging any issue that comes up should be simple.

Architecture Diagram

Deployment Diagram

Roadmap / Epics:

Sprint burndown:

Sprint board screenshot:

Cumulative flow diagram:

Sprint 1 Retrospective:

Sprint 2 Retrospective:

Sprint 3 Retrospective:

User Access to Jira: