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

Add to QA Glossary

From: Lofton Henderson <lofton@rockynet.com>
Date: Sun, 13 Jun 2004 13:58:52 -0600
Message-Id: <>
To: www-qa-wg@w3.org

QA Glossary Editors --

The following list of definitions (attached at end) comes from 
just-published SpecLite [2].  Either the words do not exist in the QA 
Glossary [1], or exist with a different definitions.

[1] http://www.w3.org/QA/glossary
[2] http://www.w3.org/TR/2004/WD-qaframe-spec-20040602/#glossary

[2] definitions that are not in [1]:  class of product, conformance clause, 
deprecated feature, Dimensions of Variability (DoV), Discretionary Items, 
extension, extensible, implementation, strict conformance, testability.

[2] definitions that differ from [1]:  conformance

This situation has burned us before, specifically in comments from Jeremy 
Carroll.  It will burn us again, if we don't keep QA Glossary synchronized 
with the QAF documents.  The instructions at the beginning of [1] say to 
make specific proposals, including wording.  Accordingly, here are my 
specific proposals.

-- insert into [1] those terms from [2] that do not presently exist in [1] 
(all terms below except for "conformance");

-- for those words that exist in [1] already (only the term "conformance"), 
replace the [1] definition with the [2] definition (alternative 
proposal:  add [2]'s to [1]'s, or else queue an issue for QAWG 
consideration, to choose between [1], [2], or new).

For reference, at the Seattle F2F we resolved:  there should be no conflict 
between [2] definitions and [1] definitions -- where they overlap, they 
should be the same (either via a pointer or with duplicated wording) -- 
although [1] definitions could build upon [2] definitions with exemplary or 
context dependent additions (to explain it in a more useful and 
user-friendly way in the context of the .


Picked directly from [2]:
Class of Product
generic name for the group of products or services that would implement, 
for the same purpose, the specification, (i.e., target of the 
specification). A specification may identify several classes of products.

fulfillment by a product, process, systems, or service of a specified set 
of requirements.

Conformance clause
a section of the specification that defines the requirements, criteria, or 
conditions to be satisfied by an implementation in order to claim conformance.

Deprecated Feature
an existing feature that has become outdated by a newer construct and is no 
longer viable.

Dimensions of Variability (DoV)
the ways in which different products that are conformant to a specification 
may vary among themselves.

Discretionary Items
deliberate and explicit grants of discretion by the specification to the 
implementations, that describe or allow optionality of behavior, 
functionality, parameter values, error handling, etc.

The ability to incorporate additional functionality beyond what is defined 
in the specification. It broadens the possibility of the technology.

The ability of a specification to accept extensions in a define way. A 
specification is extensible if it provides a mechanism for any party to 
create extensions

An implementation is a realization of a technology in accordance to the 
principles defined in the technical specifications for this technology. 
This implementation can be a document, product, application, process, 
service, system, or other entity.

Strict Conformance
conformance of an implementation that employs only the requirements and/or 
functionality defined in the specification and no more (i.e., no extensions 
to the specification are implemented).

A proposition is testable if there is such a procedure that assesses the 
truth value of a proposition with a high confidence level. Whether the 
confidence level is measurable and what confidence level is high enough 
depends on the proposition and its framework. (@@ better definition?  (see 
Wiki page))

Test Assertion
a statement of behavior, action, or condition that can be measured or 
tested. It is derived from the specification's requirements. 
Received on Sunday, 13 June 2004 15:59:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:43:36 UTC