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.
>----------
>From: Bellinger, Gaye
>Sent: Tuesday, April 22, 1997 4:02 PM
>To: 'Techwr-L List'
>Subject: Business and Technology Requirements documents
>
>Hi all! A few months ago, the company I'm working with began to put in place
>the framework for a more structured application development process. (Up 'til
>then, it was chaos! It isn't much better now, but we're working on it.)
>
>As part of this effort, development team project leads are required to
>produce Business Requirements and Technology Requirements documents at the
>applicable development stages (that is, Define and Design). The problem is,
>none of them have any idea how to write these types of documents; they're
>used to updating the specs and letting them function as the requirements
>documents. Ouch!
>
>Well, now I've been asked to "mentor" the project leads through the process
>of defining the content and designing templates for these documents. BTW, we
>also have to come up with a set of ISO work instructions for writing these
>documents.
>
>I'd like suggestions for how to approach this task, war stories that will
>provide insight about potential rat holes to avoid in the process,
>recommended parties (developers, engineers, testers, business analysts,
>writers) that should be included in the process, and especially samples of
>what you consider to be outstanding equivalent documents (and why you think
>they are outstanding). Just anything you can think of that will make this
>task less onerous!
>
>
>
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
