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

SpecGL: 1.1B conformance model techniques

From: Lynne Rosenthal <lynne.rosenthal@nist.gov>
Date: Mon, 08 Nov 2004 11:29:29 -0500
Message-Id: <6.0.0.22.2.20041108112602.01cefe10@wsxg03.nist.gov>
To: www-qa-wg@w3.org

Below is the assignment from Mark and me - new Technique for 1.1B 
Conformance Model

It is 1 technique with 4 steps and multiple substeps

1.      List the classes of products that are targeted by the specification
a.       Identify the types of products will implement the specification
b. If not already done (above step), group the products into a generic 
category – this is the class of product.  (e.g., content, user agent, 
protocol, API, specification)

2. List conformance designations or conformance concepts.  To help realize 
this, consider these questions.
a.  Does conformance mean something different for different classes of 
products?
b. Is more than 1 type of conformance defined – e.g., different 
designations (well-formed, valid) or degrees of conformance (A, AA, AAA)?
c. Is conformance tied to the class of product and similarly named (e.g, 
host-language conformance, document conformance)?

3. Create a name for each way that conformance can be qualified – i.e., 
label it
a. If the specification is subdivided into modules, profiles and/or levels, 
is there a conformance designation associated with each type of subdivision?
b. If the specification has options and extensibility, will these have an 
affect or be affected by the conformance designation?

4. Draw a diagram to put it all together – sometimes its easer to work from 
a picture
a.  diagram the classes of products with associated conformance designations,
b. add the subdivisions and any other variability (e.g., options, 
extensibility)
c. extract from this diagram and define the conformance model.
d. Write the description into the specification.  Bonus - if the diagram 
help to understand the model, include it. 
Received on Monday, 8 November 2004 16:29:48 GMT

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