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.
I need to draw on the experience of those writers who write requirements.
Brief background: A QA department is starting up a Tech Docs group. Among
the tools they (the QA people) are selecting is DOORS(R) Enterprise
Requirements Suite (ERS) from QSS. Their current plan is to have the Tech
Writers use this tool for writing requirements.
What I would like to find out is:
1) How long have you been writing requirements?
2) Have you ever used DOORS? If so, for how long?
3) What are the pros/cons of using DOORS?
4) Who primarily uses DOORS (writers, developers, Project Managers, etc.)?
Until this past Friday I had never seen or heard of this tool (I looked at
the QSS web site this morning). The Director of the QA group likes DOORS
because it is compatible with the other QA and testing tools his dept. uses
(it was also mentioned that DOORS is compatible with FrameMaker).
He knows little to nothing about Tech Writing and doesn't have any Tech
Writers that he can discuss this with (he understands the hazards of
selecting a tool for someone when the someone(s) aren't represented). I
offered to find out for him the general opinion and experience of Tech
Writers regarding DOORS. He appreciated this and is eager to find what