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: Rational SoDA From:Brent L Jones <brent -dot- jones -at- jadesolutions -dot- com> To:"'Shannon Folena'" <shannonf -at- realtyplusonline -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 14 Feb 2000 12:13:32 -0700
[question about SoDA general info snipped]
Essentially, SoDA is a customizable reporting tool that generates Word
documents based on data in Rational RequisitePro and Rational Rose
repositories.
If you don't use one or both of those tools, it's not useful at all. If you
do, it's worth its weight in gold for 'internal' documentation, such as
lists of stakeholder requirement requests (ReqPro) or use case realizations
(Rose).
It isn't at all useful for producing/automating external docs (user guides,
etc.), although some of the information in the reports it produces might be
useful in a tangential way.
In other words, although your requirements database and design models inform
your user docs, how often are you going to take information directly from
those repositories and spit it programatically into a user guide?
