Enter and select your city of departure and arrival.
Choose your journey type is one way or a round trip.
Select your departure and arrival date in case of round trips and select departure for one way trips.
Enter the number of your associated travellers, specify whether you are travelling with infants, children or adults.
Quickly search for flights with the information you input, and see the resulting flights from your search.
View your reserved flight information.
The system will feature a very easy to use search panel that allows travellers
to search for flights in
real time. They will be able to select their departing and arrival cities of choice accompanied with their
airport codes for accuracy in city names allowing the travellers to only be able to see cities that are
serviced by the airlines, hence saving time. Travellers will also be able to select their journey type from
either round trips or one way trips with an additional feature of multi-cities trip in the future releases.
The system will allow the traveller to select the dates of departure and arrival in a very easy to see
calendar view. They will also be able to include the number and type of travellers i.e., infants, children
and adults.
With these features the system will be able to display all the available flights tailored
to the travellers requirements and arrange the flights from cheapest to most expensive to ease the
travellers flight making decision. Once the traveller selects a flight of choice they will finalize the
booking process by entering their personal information and will be prompted to proceed with payment which
will direct the traveller to that airline's final reservation page ensuring secure transactions as they
enter their payment information. Once the transaction is complete they will be able to receive their flight
reservation information and itinerary. This information will be displayed on the system for future reference
by the traveller.
The ARS is primarily designed for airline travellers who need to be able to make travel plans anytime without the need of going to a travel agency or making bookings at constrained business hours at fixed locations. The ARS will be featuring domestic flights within Canada in its initial release featuring WestJet and Air Canada since these are the nation’s major airlines. There will be the possibility of expansion to include other domestic airlines and also an expansion to account for international flights as well in future releases.
The ARS displays multiple flights with corresponding prices, available seats which are further classified into classes like first class, premium economy, business and different prices are reserved for different classes and finally flight times so the travellers will be able to save money while also making a more informed flight decision. The system will also be easy to use for the travellers with its very minimal user interface which allows the traveller to only enter and view relevant information.
The system will be considered successful based on meeeting two criteriums. The first criteria is if the ratio of user searches converted to bookings is greater than 25% in the first three months of upload. The second success criteria is if the system has a very good and minimal user interface.
According to velocity, the time spent on each iteration grows, both in estimated and actual time. The
overall time spent shows an upward trend. This is related to the number and difficulty of tasks processed at
each iteration. Second, it can be seen from the graph that the actual time spent on each iteration is more
than the estimated time, which shows that we always underestimated the time spent during project. (Except in
Interation 3, we overestimated time result in less time spent on project).
For iteration 1, this is our first time to use Android studio, and we spent lots of time on learning Android
development skills. For instance, UI layout, android version, 3-tier architecture, etc. For iteration 2, we
spent much time on version control. Especially on solving merge conflict and commit graph. For iteration 3,
we spent plenty of time on refactoring code by using design pattern.
We used the 3-tier architecture involving the presentation layer, business layer and persistent layer to help organize our code.
Yes, the project did change slightly as we dropped some features that were solved intuitively changed with our
design such as;
Passing trip type so that we can return one way flights or two way flights. We dropped it because we were
only accounting for round trip flights.
We also dropped the search alternate flights as our development
design was different than we initially planned out and would not make sense to do account for this.
Design pattern. In service class, we used Singleton. In RecFlightsAdapter class and MainActivity class, we used Adpater in these 2 activity for show search flight list data. In MainActivity class, we used builder here to build a date picker.
UI / Frontend
Database / Backend
Backend / Test
Product / Test
Backend / Test