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.
Now if I could only convince the analysts to write the specs in a
comprehensible manner, it would be paradise!
Tony Markatos comments:
In what is undoubtedly a very unusual situation, I work for a software
company whose system requirements specs are much more comprehensible than
the end user documentation. (What makes them so is that they are much more
task oriented.)
I write the specs. The key to my success is focus and prioritization. More
specifically, I suffer from Data Flow Diagrams on the brain.
I first create and verify the DFD's and then use them to organize my specs.
This is a very potent approach.
Tony Markatos
(tonymar -at- hotmail -dot- com)
Discover the true meaning of life: always drive within posted speed limits
-- A. Markatos
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
