The IDEAL Assistive Technology (AT) SmartDrive^® Development Processes

Quality Assurance Plan
Last updated on October 16, 2006

A. Budget

B. Project Plan

C. Communication Plan

D. Issues-Log

E. Functional Requirements

F. Technical Specifications

G. User Documentation

H. Training Materials

I. Alpha and Beta testing Scripts

J. Final Deliverable Review Plan

K. Post-Implementation Review

I. Objective [Top]

The objective of Access Tomorrow’s assistive technology (AT) software U3 migration Quality Assurance (QA) plan is to:

Ensure that all steps of the AT U3 migration process are monitored for quality.
Ensure the use of proper user acceptance testing protocols for each AT migrated.
Determine sign-off procedures for milestone achievements

II. Required Entities [Top]

Test teams, one for each of the following disability groups:

Deaf and Hard-of-Hearing

Blind and Vision-Impaired

Mobility

Learning

Advisory Board comprised of technology experts from each of the above disability groups in addition to other experts.

III. Process [Top]

QA will be maintained through Alpha testing, correction/enhancements, Beta-testing, final correction/enhancements and final reviews.

IV. Application Evaluation [Top]

For application evaluation:

Alpha and Beta testers will use scripts that were designed to test the success of the U3 migration
All testing will be recorded and the results thoroughly documented.
Technical staff will make U3 programming changes as necessary.

V. Quality Assurance Processes [Top]

The Quality Assurance process will include the following:

A. Budget [Top]

Budget will be reviewed by advisory committee for:

cost overrun potential;
actual cost overruns; and,
actual vs. budgeted dollars YTD

B. Project Plan [Top]

The PI, development team and the advisory committee will review the project plan:

to ensure milestone dates are on target,
for any changes in scope, and
for possible trouble spots.

C. Communication Plan [Top]

The communication plan will be monitored by the advisory committee to ensure that communications among project staff is sufficient and effective.

D. Issues-Log [Top]

The project team will review the log document on a daily basis (PI weekly review) to ensure that:

target dates for resolution are being met;
high-priority actions are being resolved first; and,
the project is not put in jeopardy for any reason.

E. Functional Requirements [Top]

PI, members of the advisory committee, project team members and user groups will ensure that all functions of the source AT port successfully to the U3 platform.

PI sign-off required.

F. Technical Migration [Top]

The development team will document the U3 migration process. The PI, members of the advisory committee, development team and user groups will review the U3 migration process.

PI sign-off required.

G. User Documentation [Top]

Users, the PI, members of the advisory committee, and project team members will test (users only) and review the user documentation.

PI sign-off required.

H. Training Materials [Top]

PI, members of the advisory committee, and project team members review the training materials.

PI sign-off required.

I. Alpha and Beta testing Scripts [Top]

Project team to develop testing scripts based upon the specifications by disability.

PI sign-off required.

J. Final Deliverable Review Plan [Top]

PI, members of the advisory committee, and project team members review final deliverables to insure that they ported to U3 successfully and passed all user tests.

PI sign-off required.

K. Post-Implementation Review [Top]

A post implementation review will take place among the PI, members of the advisory committee, and project team members to document what was done right and wrong and what needs to be improved.

PI sign-off required.