W3C home > Mailing lists > Public > www-qa-wg@w3.org > April 2004

QA Handbook "Pink" Rewrites

From: Mark Skall <mark.skall@nist.gov>
Date: Fri, 23 Apr 2004 10:12:57 -0400
Message-Id: <5.1.0.14.2.20040423091257.01fe1d80@mailserver.nist.gov>
To: www-qa-wg@w3.org
QAWG,

The following is my attempt (as per my action item) to rewrite the "pink" 
text from the QA Handbook draft.  The first part of each duo is the old 
"pink" text (preceded with a "C" for "current".) The second half of the duo 
is the suggested new text (preceded with an "S" for "suggested text".)

Mark




(C) handbook about the process and operational aspects of the quality 
practices of W3C's Working Groups (WG)/WG life.
(S) handbook about the process and operational aspects of applying good 
practices for developing recommendations and conformance tests.

(C) Each presents advice and guidance about some part of the WG's test and 
quality activities.
(S) Each presents advice and guidance about some part of the WG's 
application of good practices to defining requirements and developing 
conformance tests.

(C) It might seem logical to have started by motivating the QAH audience 
with a review the benefits of sound quality practices.
(S) It might seem logical to have started by motivating the QAH audience 
with a review the benefits of good practices

(C) Plan for and commit to your QA deliverables as early as possible.
(S) Plan for and commit to your deliverables that are needed throughout the 
Rec track as early as possible

(C) Think about and enumerate the QA activities & deliverables that might 
help you through the Rec track. Minimally, you should commit to assuring 
the timely existence of test materials.
(S) Think about and enumerate the activities and deliverables that might 
help you through the Rec track. Minimally, you should commit to assuring 
the timely existence of test materials.

(C) Different kinds of QA deliverables might include:
(S) Different kinds of deliverables might include

(C) Test materials are by far the most common QA deliverable
(S) Test materials are by far the most common deliverable

(C) Synchronize your QA deliverables
(S) Synchronize your deliverables

(C) Consider whether the WG should tie any quality criteria to Rec-track 
advancement
(S) Consider whether the WG should tie any criteria enumerated in the QA 
framework to Rec-track advancement

(C) the specification cannot advance unless the committed test or other 
quality criteria are met.
(S) the specification cannot advance unless the committed QA framework 
criteria are met.

(C) Put some thought into how you're going to staff the WG's QA plans.
(S) Put some thought into how you're going to staff the WG's plans for QA 
framework deliverables.

(C) Consider: asking in CfP for extra people who would specifically be 
tasked to work on QA deliverables
(S) Consider: asking in CfP for extra people who would specifically be 
tasked to work on QA framework deliverables

(C) a shopping list of QA deliverables
(S) a shopping list of QA framework deliverables

(C) particularly aspects related to all-important test and quality processes
(S) particularly aspects related to all-important processes to enhance the 
quality of testing

(C) Put all of your important test and QA-related information
(S) Put all of your important test and QA framework-related information

(C) QA-related business
(S) QA framework related business

(C) Good Practice: Identify Web page(s) for test suites, announcements, and 
other QA deliverables.
(S) Good Practice: Identify Web page(s) for test suites, announcements, and 
other QA framework deliverables



****************************************************************
Mark Skall
Chief, Software Diagnostics and Conformance Testing Division
Information Technology Laboratory
National Institute of Standards and Technology (NIST)
100 Bureau Drive, Stop 8970
Gaithersburg, MD 20899-8970

Voice: 301-975-3262
Fax:   301-590-9174
Email: skall@nist.gov
**************************************************************** 
Received on Friday, 23 April 2004 10:13:30 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:15 GMT