W75p7 - Web Site Plan 7: Feature Set

W75p - Web Site Plan and Specification Project

Details for Part 7: Quality Assurance Plan

Quality Assurance Plan - An overview of the steps to be taken to assure that the site meets specifications, conforms to standard grammar and spelling rules, and has all links working correctly.

The IEEE Software Quality Assurance Plan Standard

The IEEE has standards for many things, including software development. Many of the features of their Quality Assurance Plan Standard are applicable primarily to large, public software projects, but the general idea is applicable to developing Websites as well. To see the standard, you can download the PDF version from: http://www.csc.calpoly.edu/~jdalbey/205/Resources/IEEE7301989.pdf.

QA Plan Sections for Small Websites	Complete IEEE Standard (for reference)
Purpose Test Problem reporting and corrective action Tools, techniques and methodologies Training	a) Purpose; b) Reference documents; c) Management; d) Documentation; e) Standards, practices, conventions, and metrics; f) Reviews and audits; g) Test; h) Problem reporting and corrective action; i) Tools, techniques, and methodologies; j) Code control; k) Media control; l) Supplier control; m) Records collection, maintenance, and retention; n) Training; o) Risk management.

PURPOSE

What are the general aspects of the site that we'll be testing?

TEST

List specific details that will be tested.

PROBLEM REPORTING AND CORRECTIVE ACTION

When problems are found, how will the be communicated, and to whom? Who has the responsibility for corrective any given type of problem?

TOOLS, TECHNIQUES, AND METHODOLOGIES

What software and hardware will be needed for testing? How will we carry out these tests?

TRAINING

What training is necessary to insure that the quality tests can carried out correctly?

Example:

Quality Assurance Plan

Purpose: Quality Assurance (QA) testing will be carried out to ensure that code is well-formed and valid, that all links are operational, and that both users and customers are satisfied with the appearance and functioning of the site on various computer system and with various browsers.

Test: The following aspects will be tested:

All links: tested for operability
All code: validated against W3C standards
Compatibility: site rendering will be checked on Internet Explorer 5-present and Netscape 4-present, both on Windows and Macintosh systems
User testing is described in the previous section (section 6)
Customer satisfaction will be an issue of ongoing importance throughout development

Problem reporting and corrective action: The QA tester (Robert McBride) and usability testers (Sandy Bergholt and George Yamashida) will report all problems to the Project Manager, who will assign a coder or graphic designer to correct the problem.

Tools, techniques and methodologies:

Links will be tested manually and using Website maintenance software such as Dreamweaver to automatically check links.
The W3C validator (http://validator.w3.org/) will be used to validate code.
Compatibility testing will be carried out using browsers and computers at the firm's office.

Training: Our staff are already trained in the use of all necessary tools and techniques.

This document is part of instructional module W75p: Web Site Plan and Specification Project
Previous Detail Section	W75p Project Overview	Next Detail Section
	About this series of documents