RE: Value of design documents (was: New TECHWR-L Poll Question)

["Susan Ahrenhold" <sahrenhold -at- winspc -dot- com>]

>>>That's the problem. The spec was NOT written in formal language; it was
>>>written in natural language that (as stated in my original post) has a
>>>propensity for introducing ambiguity, inaccuracy, and inconsistency. A
>>>formal language for spec development that's made more usable is a spec
>>>written in a natural language. It's like being a little bit pregnant:
either
>>>you are or you aren't! ; )

I've worked with specs in formal language, with an explanation and
commentary in natural language. This is very useful for a writer, because it
really lets you test your understanding of the specification language
constructs; also many implementations add features or do not support
specific parts of a specification; this is a real good way to note this.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-Based Help with Macromedia Dreamweaver 4 ($100 STC Discount)
**WEST COAST LOCATIONS** San Jose (Mar 1-2), San Francisco (Apr 16-17)
http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.

Sponsored by DigiPub Solutions Corp, producers of PDF 2001 
Conference East, June 4-5, Baltimore/Washington D.C. area.
http://www.pdfconference.com or toll-free 877/278-2131. 

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.