<TapChat AAC>

Radford University
Advanced Topics in Software Engineering
Unspoken 2.0
Reflective Quality Plan
Project Name: ________TapChat AAC_________
Prepared By: _________Unspoken 2.0________
Date: ______11/10/2015________

Project Scope

Describe the project, either by inserting the Project Scope Statement or by providing a summary description of the overall
project, its objectives, its customer, and its customers business needs.
Specifications: Android only (Java and XML).
Expected Audience: people who are nonverbal, or have difficulty communicating verbally, including stroke patients.
We will refine an Android application that allows people, who are nonverbal or have difficulty communicating verbally,
including stroke patients, to select a series of pictures that will then be converted into a phrase to be read aloud by the
users device. The Client has requested the developers to make these changes in order to make this application more
convenient to the usability of our users.

Deliverable Description

Describe project deliverables, including contract deliverables and milestone checklist.

The Team will deliver an Android application that prescribes to the requirements laid out in the User Stories and
Acceptance testing documents. In addition, each iteration should deliver a working version with the most recent
additions and upgrades being demonstrated to the Client.
Deliverable:
September 1 Work Day Policies and Procedures Document
September 8 Update User Stories Document
September 15 Update Iteration (Release) Planning Document
September 15 - Team Website Creation
September 22 Software Quality Document
September 22 Iteration 1 Testing and Bug Report
September 29 Iteration 1 Presentation
September 29 Iteration 1 Testing Report
October 13 Iteration 2 Manager Report
October 20 Iteration 2 Testing and Bug Report
November 3 Iteration 2 Presentation
November 3 Iteration 2 Testing Report
November 10 Reflective Software Quality Plan
November 17 Iteration 3 Initial Testing Report
December 1 Iteration 3 Final Presentation
December 1 Iteration 3 Final Testing Report
December 8 User Manual
December 8 Final Code Submission
December 8 Final Project Reflections
Milestone Checklist:
Complete:
-Text to speech on the image
-User can change the images to their own images
11/14/2015
TapChat AAC Reflective Quality Plan

Page 1
Department of Information Technology, Dr. TL Lewis - Project Management

<TapChat AAC>
-Text underneath images
-Dynamic screens and text
-Drag and drop buttons
-Custom buttons with new text
-Dedicated tab for text-to-speech of user inputted phrase
Incomplete:
-Change languages

Acceptance Criteria

Describe how well your team has meet the acceptance criteria for deliverable, so far. List relevant quality standards.
The acceptance criteria for all user stories shall be that the user story has a pass rate of 90% on all acceptance tests. No
user story shall be considered complete until the Client, the Tester, the Project Manager, and the Team as a whole agrees
that the required tests have passed.
All deliverables so far have met the acceptance criteria as defined by the following quality standards
Quality Standards:
-Screen does not scroll
-Buttons speak when pressed
-Button images can be changed for certain text
-Images are relatable
-Emotions separated by category positive, neutral, negative
-Images can be reset to default after customization
-Images rescale dynamically
-Buttons reorder correctly when dragged and dropped
-API 11 is used to ensure greatest compatibility with all devices

4. Quality Assurance Activities

Create a scale (eg. high, med, low) to assess how well your team is following the Quality Assurance activities outlined in
the initial quality report.
Quality Assurance activities shall consist of the Tester and Project Manager working to ensure that the product is being
developed to the highest of standards. Working in coordination with the Client, the Tester, Customer Testers, and Project
Manager will relay both their own concerns and the concerns of the Client to the Development Team. The team met a
high level of quality in this area due to coordination between the Client and the Team.
The Team shall make continuous updates to the program as the APIs evolve, change, and become outdated to ensure
that the program remains functional throughout its entire lifetime. The Team achieved a medium level of quality in
this area due to current use of deprecated values and methods.
Documentation shall include the Test Cases Document, Acceptance Test Document, and Bug Report, provided by the
Tester. These documents shall be presented upon completion, and will be amended as test cases and acceptance tests
are fulfilled and passed. The milestone checklist shall also be updated as milestones are completed or added. Document
reviews will be performed. The Team succeeded in maintaining a high quality due to creation and maintenance of
testing documents.
The requirement verification process shall consist of the Team working together as a whole to ensure that all test cases
from the Test Case Document and Acceptance Tests Document have passed. The team achieved a medium level here
due to much of the testing being done by the Tester or the Client and Customer Testers.

Project Team Quality Responsibilities

Review and re-plan the quality-related responsibilities of the project team including specific tasks such as acceptance
test, audit, review and checklist responsibility assignments for the final iteration.
11/14/2015
TapChat AAC Reflective Quality Plan

Page 2
Department of Information Technology, Dr. TL Lewis - Project Management

<TapChat AAC>
The Program will be demonstrated to the Team as a whole upon completion of any major feature or refactor. The Team
will note any and all concerns and recommendations named by any members, and those items will be discussed and
considered for later implementation into the Program.
Control information will be collected during internal demonstrations of the program. This information will be used to
ensure that the quality standards of the application are consistent throughout the development process within an iteration
and throughout multiple iterations. Reviews should be conducted internally prior to any iteration release, and audits shall
be conducted at the discretion of the Project Manager or Tester.
The Client will review any and all acceptance tests provided for each iteration. The client will be the final judge is to
whether an acceptance test has met its requirements.
The Designer will be responsible for auditing the code to ensure that coding standards are followed. Code review will also
be performed by the Designer along with the Developers.
The Project Manager will be responsive for ensuring that all deliverables are met and velocity is maintained for user
stories for each iteration.
Variance to acceptable criteria will be reported by anyone who discovers such a problem. As the Development Team
moves forward with progress, if any member feels unsure about whether or not the work they are doing will meet the
requirements for acceptable criteria, they should call a meeting or wait until the next official meeting to bring up their
concerns.

11/14/2015
TapChat AAC Reflective Quality Plan

Page 3
Department of Information Technology, Dr. TL Lewis - Project Management