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.
Subject:RE: Kovitz vs Traditional From:kimber_miller -at- acs-inc -dot- com To:<techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 04 Feb 2000 11:59:00 -0600
I have worked with the labels that Kovitz applies. The functional spec I work on
with the client--refining their wish list of what they want the app to do. Then
comes the design phase when the developers/designer sits down and figures out
how to make their wishes come true. Then comes the design doc that tells the
client how the application will behave to obey their wishes.
Sorry about the Alladin metaphor. It's Friday.
kimber_miller -at- acs-inc -dot- com
Affiliated Computer Services
"The truth shall set you free, but first it's going to piss you off."
From: "Charter Tara M." <Charter -dot- Tara -at- mayo -dot- edu>
Sent: Thursday, February 03, 2000 8:43 AM
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Subject: Kovitz vs Traditional
Although I'm inclined to go Kovitz' way, I'm wondering how you have declared
the 'what' and the 'how' in your endeavors to provide useful documentation.