Team Dementors :

Github | Sprint Sheet | Project Journal | Project Board

Team Members:

1. Ashika Anand Babu
2. Ramya Mahesh
3. Anusha Gangasani
4. Shruthi Srinivasan

Tech Stack:

Project Files:

1. Architecture Diagram
2. Class Diagram
3. DB Design
4. Wireframes
5. [Deployment Diagram] (https://github.com/gopinathsjsu/team-project-the-dementors/blob/main/Deployment.pdf)

Team Member Contributions:

1. Anusha Gangasani:

1. Implementation, Integration and testing of user, login and registration api
2. Implementation, Integration and testing of saveBooking and updateBooking api.
3. Implementation, Integration and testing of saveCustomer, updateCustomer api.
4. Deployment of backend service in AWS.
5. Deployment of RDS and populating mock data.
6. UI Integration
7. Bug Fixes.

2. Ashika Anand Babu:

1. Implementaion, Integration and testing of Cancel screen
2. Implementaion, Integration and testing of Confirm screen
3. Implementaion, Integration and testing of Bookings by a customer screen
4. Implementaion, Integration and testing of Bookings for an hotel screen
5. Implementaion, Integration and testing of Profile screen

4. Ramya Mahesh:

1. Implementation, Integration and testing of getHotels, getHotelBooking and getRooms api
2. Implementation, Integration and testing of checkRoomAvailability api.
3. Implementation, Integration and testing of getAmenities, getAmenities api.
4. Implementation, Integration and testing of dynamic pricing.
5. Deployment of backend service in AWS.
6. Deployment of RDS and populating mock data.
7. UI Integration
8. Bug Fixes.

5. Shruthi Srinivasan:

1. Implementaion, Integration and testing of Login screen
2. Implementaion, Integration and testing of Signup screen
3. Implementaion, Integration and testing of Search screen
4. Implementaion, Integration and testing of List of hotels screen
5. Implementaion, Integration and testing of Hotel Details screen
6. Implementaion, Integration and testing of Booking Confirmation screen

XP values followed:

1. Communication : Communicated openly on the expectations of each stories, dependencies and implementation methods. We used to meet once in a week on Mondays, to discuss the status, issues/blockers and what has been worked on till date. Prioritize the features which has more dependency. Highlight Blockers.

2. Feedback : Every feature was discussed on implementation details and pick the one which suits our project the best. Frequent PR reviews.

3. Simplicity : Implemented only the features that has been asked for. Keep the Backend, UI and Database design simple.

4. Sit together : Debug the issues together and fix it. Give the demo of the features implemented once a sprint.

5. Pair programming : Architecture design, DB Design, Wireframes and Deployment designs were discussed and finalised on Monday syncup calls.

6. 2-weeks sprint/bi-weekly cycle: We followed two week sprint acitivity and developed the product in 4 sprints.

Project Flow:

1. Our web application starts at:

2. We can register an user or login 3. On login: we are presented with search page:

4. Select your city, rooms, dates and continue search - we are provided an option to select the hotel from list of hotels:

. 5. Select the hotel of your choice and then select the type of room here:

6. After selecting the type of room, select the amenities you need and if you would like to book using rewards points:

7. Chechout and confirm booking:

8. You can manage all your bookings at:

9. Edit booking date:

10. Delete bookings:

11. View your profile:

12. Sign out 13. If you are an employee, login and view all the bookings of an hotel as:

Implemented the Backend using: Model View Controller

MVC (Model-View-Controller) is a pattern in software design commonly used to implement user interfaces, data, and controlling logic. It emphasizes a separation between the software's business logic and display. This "separation of concerns" provides for a better division of labor and improved maintenance. Some other design patterns are based on MVC, such as MVVM (Model-View-Viewmodel), MVP (Model-View-Presenter), and MVW (Model-View-Whatever).

The three parts of the MVC software-design pattern can be described as follows:

• Model: Manages data and business logic.
• View: Handles layout and display.
• Controller: Routes commands to the model and view parts.