**Prioritized User Stories and Project Progress:<br>**
**Preliminary Product Deliverables*
1. Searching for flights ✓<br>
2. Retrival of reservation ✓<br>
3. Usability of web pages ✓<br>
4. Origin Time Indication ✓<br>
5. Displaying search results ✓<br>
6. *Language options of pages:* **Blocked** - *Postponed* due to TIME limitaiton, will be launched with the Final Product<br>
7. Security of payment page ✓<br>
8. About page of the company: ✓<br>
<br>
**Quality Assurance Plan (testing, inspection, acceptance)**
-----------------------------
***Quality Assurance Plan**<br>*
<br>
**Introduction**<br>
Our team is developing a website for a flight reservation system; therefore we will be combining the conventional testing strategies of software and the innovated Web Application Testing.<br>
<br>
**Scope**<br>
*Reference of FURPS+*<br>
**FURPS*:
***F**unctionality
***U**sability
***R**eliability
***P**erformance
***S**upportability
**The Plus +*:
* Design constraints
* Implementation requirements
* Interface requirements
* Physical requirements
***Functional**:<br>
All eight ranked user stories with eligible acceptance tests (from Milestone 5 [Storyboard]).
***Non-Functional**:<br>
The font size of text, webpage loading speed, etc.
<br>
**Quality Objective**<br>
An easy-to-use web application for not just markers but everyone who has basic technology of computer.<br>
<br>
**Roles and Responsibilities**<br>
**Ali and Jordan*:<br>
All Back-End relevant testings of the codes they implemented: the database, Nodejs, Javascripts, etc.<br>
**Wes and Nick*:<br>
All Front-End relevant testing of the systems they implemented: the HTML pages with CSS stylings, shared responsibilities of testing of Nodejs, Javascripts, etc.<br>
**Wes*:<br>
Overall testing and Web Application Testing of the entire project.<br>
<br>
**Quality Assurance Plan (testing, inspection, acceptance)**
-----------------------------
**Test methodology**<br>
* Deliverables:
* A fully-functioning system without bugs
* Testing approach:
* White-box testing
* Black-box testing
* Testing levels:
* Unit testing
* Integration testing
* System testing
* Operational acceptance testing
* Testing types:
* Installation testing
* Compatibility testing
* Regression testing
* Acceptance testing
* Alpha testing
* Beta testing
* Functional vs non-functional testing
* Test tools with bug repoarting:
* Brackets without debugger
* Visual Stduio with debuger
* Browsers: Chrom, Firefox, Edge, etc.
<br>
**Inspection methodology**
* Deliverables:
* A well-developed website ready to be used
* Inspection approach:
* Planning
* Overview meeting
* Preparation
* Inspection meeting
* Rework
* Follow-up
<br>
...
...
@@ -135,23 +219,100 @@ Miely:<br>
**Source Code**
-----------------------------
Notes:
Notes to self: Source code Organizing:
indentation
better format
more inline comments
**Readme to build, run and test product**
-----------------------------
**ReadMe<br>**
<br>
## Getting Started
Instructions to get the web application running on a local machine.
