TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Some have posted on this listserv that it is not possible to have standard
software design processes (without adversely affecting creativity).
However, lack of std design process means that those downstream from design
(including Technical Writers) must constantly deal with inputs of greatly
varying (often very poor) quality.
I believe that developers can work to standard processes. For example, in
every ad-hoc (Level 1 Process Maturity) software organization that I have
worked in (or know about), nobody EVER created a flow chart (or if they did,
it was total nonsense). What's so hard about creating a flow chart
(logical, or DFD - whatever is appropriate) done to accademic standard. I
have created such many-a-time.
This would be a great standard practice! And it would significantly
simplify my work as a Technical Writer.
I am sure that there are many of possible standard practices.
Tony Markatos
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
