Project Final Delivery - Githubissues

Due 04/30

[ ] Video recording demonstrating your application
[ ] A github link to your source code

Requirements:

[x] Customers shall be able to specify the departure airport they wish to travel from and the arrival airport they wish to travel to.
[x] Customers shall be able to search for flights using departure date, arrival dates and respective time windows within each.
[x] Customers shall be able to reserve flights to travel either one-way (from departure to destination), or reserve a round-trip flight (from departure to destination and back to original departure airport).
[x] The client software shall allow customers to reserve travel from the destination airport to an arrival airport using a series of connecting flights with a maximum of two stopovers.
[x] The client software shall allow flights to be sorted by departure time, arrival time, or travel time to support the customer's flight selection.
[x] The client software shall allow the customer to select flights and confirm the selection prior to the reservation being made.
[x] Customers shall be able to specify the departure airport and arrival airport from a list of possible airports provided by the system.
[x] The client software will only allow travel with stopovers to be reserved if there is at least 60 minutes between the arrival of the arriving flight and departure of the departing flight for each stopover to allow time for passenger and luggage transition
[x] The client software will not allow reservations with stopovers in excess of 24 hours between the arriving and departing flights
[x] The client software shall display departure time and arrival time of each leg in airport local time
[x] The client software shall clearly display flight details after a customer submits a reservation
[x] All backend classes will be unit tested using Junit test cases developed in parallel with application software.
[x] All frontend classes will be unit tested developed in parallel with application software.
[x] The client software shall display an error message in the event that a required resource (such as the backend or database servers) is unavailable.
[x] Response time for any requested actions will be reasonable. Operations in excess of 3 seconds will provide indication to the customer the system is operating.
[x] The client software shall be highly available (99% yearly system availability) and able to run 24/7.
[x] The client software shall support multiple instances running concurrently to allow multiple customers to make reservations at the same time.
[x] The client software backend will use the Java Spring Boot framework for platform independence.
[x] The client software frontend will use the React Javascript framework to support a dynamic user interface.
[x] The client software frontend will interface with the backend using RESTful APIs with JSON responses to keep the components distinct with modern architectural patterns.
[x] The backend will support the provided database schema and associated set of APIs provided by WPI. The client software will use the provided APIs to lock the database, release locks after completing transactions, and wait and retry in the event the database is locked by other clients.
[x] Documentation generated with Swagger
[x] Application will be able to be deployed on an AWS EC2

Mee42 / cs509-project

Project Final Delivery #54