Re: Format for QAF principles

Le 03 mars 2004, à 03:51, Lynne Rosenthal a écrit :
> or be necessary for each and every principle.   I wasn't able to find 
> Karl's QAF to FAQ to ensure that I captured his ideas - but I think I 
> have.
>
> +++++++++++++++++++++++++++++++++++++
> Storyboard (story, situation)
> Preconditions or assumptions
>
> [PRINCIPLE]
> Descriptions
> Benefit of applying principle
>
> Examples, more examples
> Template and/or tool to implement
> [good practices]
> [constraints  exemptions, caveats]
>
> Assessment: Have I got it right  how do I know
> +++++++++++++++++++++++++++++++++++++++++
>


Yes something to add in the same train of thoughts that I have already 
send to the QA chairs in the past. It doesn't mean it has to be like 
that, but it gives an idea of questions we should ask ourselves each 
time we are designing something.


	+ Scope
		- What does that mean?
			Theory and examples
		- How can I write it?
			Templates
		- What tools can help me to do that?
			XMLSpec, Amaya, HTML, scripts perl?
		- How can I encourage one method on another one?
			Benefits of using a common method, Access
			to the information with ease, extraction of
			what others have done.
		- Reference to other pieces
			For example, in scope you might need to
			use "class of products", if you don't know
			what is it, but not necessary.
	+ Class of Products
		- ...
		- ...
	+ Extensions
		- ...
		- ...
	+ Test Assertions
	+ Test Case
	+ Charter
	+ Conformance Section
	+ etc... a lot of them like that.


-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager
*** Be Strict To Be Cool ***