|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Milestone 9: Code Inspection and Improvement Plan Due March 13, 2020 (7:00pm Friday)
|
|
|
|
|
|
Design a code inspection document/checklist and appropriate improvement plan.
|
... | ... | @@ -63,6 +70,90 @@ Quality Criteria and Inspection Items. |
|
|
10. Instrumentation
|
|
|
1. Every class has a parameterless toString method which returns a String containing a dump or summary of an instance of the class.
|
|
|
|
|
|
Copy and paste from Milestone 7
|
|
|
|
|
|
***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>
|
|
|
|
|
|
**Inspection methodology**
|
|
|
|
|
|
* Deliverables:
|
|
|
* A well-developed website ready to be used
|
|
|
* Inspection approach:
|
|
|
* Planning
|
|
|
* Overview meeting
|
|
|
* Preparation
|
|
|
* Inspection meeting
|
|
|
* Rework
|
|
|
* Follow-up
|
|
|
<br>
|
|
|
|
|
|
|
|
|
**Action Plan**<br>
|
|
|
|
... | ... | |