Action Plan
Fantastic 4:
All team members actively participated in two weekly team meetings this week and contributed to the Prioritized Product Backlog with their individual thoughtful opinions.
Ali:
Created DataBase Schema and will continue to work on setting up Database and continuous implementation
Jordan:
Scheduled and booked team meeting rooms, defined Glossary of Milestone 4 and partially involved in UML diagram creation and development in the next couple weeks.
Nick:
Created a preliminary UML diagram from the previous team meeting for this stage. Created Milestone 4 at Wiki page with Prioritized Product Backlog and initial formatting of the Milestone 4. Will be focusing on sketching and storyboarding for the next Milestone.
Wes:
Summarized Action Plan and started looking into the sketching and storyboarding, finished the final formatting of the Milestone 4. Completed a team contract for next week's Tuesday team meeting.
Domain Model
Database Schema
Flight Route Schema:
Saskatoon——><———Toronto
Saskatoon———><——— Montreal
Saskatoon———><———Vancouver
Saskatoon———><———Los Angeles
<Saskatoon——-><———Calgary> [Departure Flight]
(Calgary is the connection airport for most international destinations)
Calgary———><————-Seattle
Calgary——><——-Los Angeles
Calgary———><———Houston
Calgary————><———Yellowknife
Calgary———><———Chicago
Calgary——><———New York
Calgary——><——-Miami
Calgary——><——-Mexico City
Calgary——><——Cancun
Calgary——><——Paris
Calgary----><—-Frankfurt
Calgary——><—— London
Calgary———><———Barcelona
Calgary———><———Prague
Calgary——-><——Amsterdam
Calgary——><——Stockholm
Calgary——><——Rome
Calgary—><—-Munich
Calgary—-><—— Beijing
<Calgary——><——Saskatoon> [Return Flight to Calgary then back to Saskatoon]
Prioritized Product Backlog (Ranking starts from most important to least important)
-
As a customer, I want to be able to easily search for flights based on the desired destination, origin, departure date/time so I can book flights with minimal technological ability.
-
As a customer, I would like to see all of the details related to my reservation including terminal number, luggage added, booking reference, etc. so check-ins are easier and I feel prepared
-
As a customer, I want a website that is visually appealing and doesn’t require any extra digging for information, so I can save time and effort.
-
As a customer, I want to see the current time at my origin/destination and what time it will be when I arrive, so I can plan my trip accordingly.
-
As a customer, I would like to know the exact trip length and the exact final price before booking, so I have a sense of awareness.
-
As a customer, I want different language options so I can choose a language I’m most comfortable with.
-
As a customer, I want to know that my financial information is secure when booking a flight, so I’m not concerned about my information being leaked.
-
As a new customer, I want an “About” section where I can learn about the company before I book with them so I can feel more connected and develop trust.
Glossary
- Customer: Someone who can use the application to book flights
- Tickets: Contains all the relevant information about the tickets
- Flights: Contains information about the flights a customer books or is interested in booking
- Booking: A container used to store all the tickets a customer has bought
- Bus: It contains all the information about the buses a customer books or is interested in booking.
Technology
- HTML, CSS, JavaScript, SQL, and Node.js
- Docker Hub: Team Container of Applications
- GitLab: Development Platform
- Excel Spreadsheet: Store Data for Simulation/Testing
- StackOverflow.com: Resources of Coding Solution
- YouTube: Coding Tutorial Videos