- From: Karl Dubost <karl@w3.org>
- Date: Thu, 15 Jul 2004 14:37:17 -0400
- To: www-qa-wg@w3.org
- Message-Id: <FF807189-D68D-11D8-BAB6-000A95718F82@w3.org>
This one I'm not sure that it should be included in SpecGL Lite and I need more input from the QA WG participants. If you think you can develop more ideas and specifically techniques and examples, it means it's useful, if not, we will drop it. Good Practice: Use formal language What does that mean? It is possible using formal languages (e.g., XML Schema, UML) to check for correctness of the specification and that requirements are specified clearly and unambigiously. The checking can be done via automated tools. Why should I care? Using a formal language to define a technology means that there is an abstract model of your technology and therefore it will be easier to develop and write the feature in a consistent manner. If the abstract model of the technology doesn't exist, using a formal language will help to define it. Related: @@References about UML to define technical specifications@@ ? Techniques: 1. Define an abstract model of your technology with a formal language 2. Use automatic tools to check the consistency of your technology Examples: Examples? For formal language specifications - test the formal language. (wiki FormalLanguageVsProse) -- Karl Dubost - http://www.w3.org/People/karl/ W3C Conformance Manager *** Be Strict To Be Cool ***
Received on Thursday, 15 July 2004 18:18:25 UTC