Checklist of Checkpoints for "QA Framework: Operational Guidelines"

This version:
This document is an appendix to:
Latest version of "QA Framework: Operational Guidelines":
Dominique HazaŽl-Massieux (dom@w3.org)
Lofton Henderson (lofton@rockynet.com)
See Acknowledgments in QA Framework: Operational Guidelines.


This document is an appendix QA Framework: Operational Guidelines [QAF-OPS] . It provides a tabular checklist of all checkpoints from the specification guidelines, complete with their priorities. Please refer to QA Framework: Operational Guidelines [QAF-OPS] for the full statement and description of the operational guidelines and checkpoints, as well as references to related documents and full credits and acknowledgements of contributors to the operational guidelines work.

Status of this document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

This document is derived from and is an appendix to QA Framework: Operational Guidelines [QAF-OPS] , which document is a W3C Candidate Recommendation (CR), made available by the W3C Quality Assurance (QA) Activity for discussion by W3C members and other interested parties. For more information about the QA Activity, please see the QA Activity statement. Please see the "Status of this document" section of the corresponding specification guidelines [QAF-OPS] , for complete details about the status of the specification guidelines version from which this is extracted and which it accompanies.

Please send comments to www-qa@w3.org, the publicly archived list of the QA Interest Group [QAIG]. Please note that any mail sent to this list will be publicly archived and available. Do not send information you wouldn't want to see distributed, such as private data.

Publication of this document does not imply endorsement by the W3C, its membership or its staff. This is a draft document and may be updated, replaced, or made obsolete by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress".


This checklist includes all checkpoints from the QA Framework: Operational Guidelines [QAF-OPS] presented in a tabular format. The checkpoint priorities are included, and the order of the operational guidelines document is maintained.

The presentation is intended to be convenient for organizers and evaluators of QA projects in W3C Working Groups, to facilitate assessing operational aspects against the checkpoints. The table includes spaces for scoring each checkpoint, "yes" (satisfied), "no" (not satisfied), "n/a" (not applicable).


For a description of the meaning of the priorities in the following table, please consult the conformance clause and the priorities definition section of the operational guidelines ([QAF-OPS], chapter 4 and section 1.8) .

Checklist table

Guideline 1. Commit to Quality Assurance in Working Group activities.

Nbr Checkpoint Priority Yes No N/A

Define QA commitment levels for operations, specifications, and test materials.

[Priority 1]      

Commit to test materials.

[Priority 2]      

Commit to complete test materials.

[Priority 3]      

Enumerate QA deliverables and expected milestones.

[Priority 1]      

Define QA criteria for Recommendation-track advancement.

[Priority 2]      

Guideline 2. Commit to resource level for Working Group QA activities.

Nbr Checkpoint Priority Yes No N/A

Address where and how conformance test materials will be produced.

[Priority 1]      

Address QA staffing commitments.

[Priority 1]      

Request allocation of QA resources to the Working Group.

[Priority 1]      

Guideline 3. Synchronize QA activities with the specification milestones.

Nbr Checkpoint Priority Yes No N/A

Synchronize the publication of QA deliverables and the specification's drafts.

[Priority 2]      

Support specification versioning/errata in QA deliverables.

[Priority 1]      

Guideline 4. Define the QA process.

Nbr Checkpoint Priority Yes No N/A

Appoint a QA moderator.

[Priority 1]      

Appoint a QA task force.

[Priority 2]      

Produce the QA Process Document.

[Priority 1]      

Specify means for QA-related communication.

[Priority 2]      

Define branding policy details.

[Priority 3]      

Guideline 5. Plan test materials development.

Nbr Checkpoint Priority Yes No N/A

Define a framework for test materials development.

[Priority 2]      

Ensure test materials are documented and usable for their intended purposes.

[Priority 1]      

Define a contribution process.

[Priority 2]      

Address license terms for submitted test materials.

[Priority 1]      

Define review procedures for submitted test materials.

[Priority 2]      

Guideline 6. Plan test materials publication.

Nbr Checkpoint Priority Yes No N/A

Ensure a suitable repository location for test materials.

[Priority 1]      

Define the licenses applicable to published test materials.

[Priority 1]      

Describe how and where the test materials will be published.

[Priority 2]      

Provide a conformance verification disclaimer with the test materials.

[Priority 1]      

Promote testing and the publication of test results.

[Priority 2]      

Guideline 7. Plan the transfer of test materials to W3C if needed.

Nbr Checkpoint Priority Yes No N/A

Perform a quality assessment of any test materials that are candidates for transfer.

[Priority 2]      

Identify sufficient staff resources to meet the needs of any transferred test materials.

[Priority 1]      

For any transferred test materials, resolve all IPR issues with the external party that produced the test materials.

[Priority 1]      

Guideline 8. Plan for test materials maintenance.

Nbr Checkpoint Priority Yes No N/A

Provide for the long-term maintenance of the contribution and review procedures.

[Priority 3]      

Specify a test materials update procedure to track new specification versions/errata.

[Priority 1]      

Identify a procedure for test validity appeals.

[Priority 2]      


QA Framework: Operational Guidelines, L. Henderson, D. HazaŽl-Massieux, L. Rosenthal, Eds., W3C Candidate Recommendation, September 2003, available at http://www.w3.org/TR/2003/CR-qaframe-ops-20030922/.