... | ... | @@ -44,10 +44,12 @@ combine the above into "Product Vision" |
|
|
|
|
|
|
|
|
|
|
|
**Architecture**
|
|
|
**Architecture??**
|
|
|
-----------------------------
|
|
|
|
|
|
|
|
|
**System Architecture**
|
|
|
<br>
|
|
|
* **UML Component Diagram: <br>**
|
|
|
![M5-UML-REV2](uploads/31c6b93d10525e2fcf92ad7aaee803b3/M5-UML-REV2.jpg)
|
|
|
|
|
|
|
|
|
**Personas/Roles**
|
... | ... | @@ -100,21 +102,103 @@ Miely:<br> |
|
|
|
|
|
**User Stories implemented**
|
|
|
-----------------------------
|
|
|
**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>
|
|
|
|
|
|
**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>
|
|
|
|
|
|
**Quality Assurance Plan (testing, inspection, acceptance)**
|
|
|
-----------------------------
|
|
|
**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.
|
|
|
|
|
|
### Prerequisites
|
|
|
|
|
|
What must be installed to run the software:
|
|
|
|
|
|
```
|
|
|
nodejs, sqlite3, express, ejs, nodemailer
|
|
|
```
|
|
|
|
|
|
### Installing
|
|
|
|
|
|
How to run the application:
|
|
|
|
|
|
**Readme to build, run and test product**
|
|
|
-----------------------------
|
|
|
Clone the git branch
|
|
|
|
|
|
```
|
|
|
git clone https://git.cs.usask.ca/yol474/cmpt370-fantastic-4.git
|
|
|
```
|
|
|
|
|
|
Download and install nodejs
|
|
|
|
|
|
```
|
|
|
https://nodejs.org/en/download/
|
|
|
```
|
|
|
|
|
|
Navigate to the **air370proj** folder that contains **app.js**
|
|
|
|
|
|
```
|
|
|
cmpt370-fantastic-4\air370proj\AirPararies370proj\air370proj
|
|
|
```
|
|
|
|
|
|
Use npm to install the following requirements.
|
|
|
|
|
|
```
|
|
|
npm init
|
|
|
npm i sqlite3
|
|
|
npm i express
|
|
|
npm i ejs
|
|
|
npm i nodemailer
|
|
|
```
|
|
|
|
|
|
Run app.js using command line
|
|
|
|
|
|
```
|
|
|
node app.js
|
|
|
```
|
|
|
|
|
|
Application will be live on port 2020
|
|
|
|
|
|
```
|
|
|
localhost:2020/
|
|
|
```
|
|
|
|
|
|
If you would like a reference when booking a flight be sure to use a real email in the form.<br>
|
|
|
The site may need to be reactivated to have the latest booking information since
|
|
|
it is local.
|
|
|
|
|
|
### Wiki
|
|
|
|
|
|
Features details for all milestones and group members<br>
|
|
|
|
|
|
https://git.cs.usask.ca/yol474/cmpt370-fantastic-4/wikis
|
|
|
|
|
|
|
|
|
**Acceptance test results**
|
|
|
-----------------------------
|
|
|
From M10? What about M8?
|
|
|
**Testing of User Stories:**
|
|
|
* *Following the order of the above*
|
|
|
|
|
|
* 1. Searching for flight routes: null, existing, non-completed, completed, duplicate, etc.<br>
|
|
|
* 2. Retrieval of reservation: retrievable, correct, incorrect, multiple, etc.<br>
|
|
|
* 3. Usability of web pages: general web application testing will be applicable here. <br>
|
|
|
* 4. Origin Time Indication: check if both origin time displaying or not, the correctness of the time, etc.<br>
|
|
|
* 5. Displaying search results: check if the results will show up or not, the correctness of the results, etc. <br>
|
|
|
* 6. *Language options of pages:* **Blocked** - *Postponed* as indicated above<br>
|
|
|
*Check if language choices exist, choices are clickable or not, etc.* <br>
|
|
|
* 7. Security of payment page: check if payment information still exist in database or not, etc. <br>
|
|
|
* 8. About page of the company: Responsiveness, completeness, etc.<br>
|
|
|
<br>
|
|
|
|
|
|
From M3???
|
|
|
**Eight User with Acceptance Tests and Estimates**<br>
|
|
|
Estimates made on a scale of 1-5.<br>
|
... | ... | @@ -276,9 +437,6 @@ Estimates: <br> |
|
|
Estimate Score = 2
|
|
|
<br>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**Domain Diagram**
|
|
|
-----------------------------
|
|
|
**Domain Model**
|
... | ... | @@ -288,14 +446,20 @@ Estimate Score = 2 |
|
|
|
|
|
**Class Diagram**
|
|
|
-----------------------------
|
|
|
|
|
|
**UML - Class Diagram (Expanded)**<br>
|
|
|
![F4_UML_M6](uploads/6eb6441a74282dbac7b08a5934c788a0/F4_UML_M6.jpg)
|
|
|
<br>
|
|
|
|
|
|
|
|
|
**Interaction Diagrams**
|
|
|
-----------------------------
|
|
|
**UML - Sequence Diagram**<br>
|
|
|
![Sequence_Diagram_2](uploads/32d7431c9b94c682b5a314ff7984e73d/Sequence_Diagram_2.png)
|
|
|
<br>
|
|
|
|
|
|
|
|
|
|
|
|
**UML - Activity Diagram**<br>
|
|
|
![Activity_Diagram](uploads/82d0ef3163e9ef4864ef142a34578013/Activity_Diagram.jpg)
|
|
|
<br>
|
|
|
|
|
|
|
|
|
**Database Schema**
|
... | ... | |