Re: Bi-directional traceability and docs
We're going thru the pains of CMMi here, and one of the objectives is to
institute "bi-directal traceability", which, in a nutshell, means that the
spec points to the places in the code and doc that need to change to meet
a user req, and the code and the doc reflect the user req that prompted a
change. And my group here has been asked to consider implementing this
traceability in our doc.
A little background. We release new software versions every 6 months, each
new version consisting of a number of user req "enhancements", which are
then summarized in Release Notes, and propogated throughout the
installation, configuration, and user doc. The Release Notes list each
"enhancement" that goes in a version, but the other docs do not mention
specific enhancements by number. The request is that the other pieces of
doc also begin mentioning the specific "enhancements".
I can come up with good reasons to do so - it helps our users and our
business analysts track how an enhancement ripples through our system.
OTOH, I can see this turning into a big pain in the tuckus.
Well, I'm not sure I entirely understand, but I infer that what's desired is content in the documentation that not only tell users what to do, how to do it, and why they should make specific choices or enter specific information, but content that tells users what revision of the software a particular feature was added or modified.
I touched on this in another response: docs should give users the information they need, when they need it.
Anything else is visual clutter.
If you're using version 6.1 of the product, and you need help and open the docs, you could care less that the particular feature you're using was added in version 5.0. From a user's perspective, that information is entirely irrelevant to their goals.
User Assistance & Experience Engineer
twriter "at" sonic "dot" net www.writeforyou.com
"I see in your eyes the same fear that would take the heart of me.
The day may come when the courage of Men fail, when we forsake our
friends and break all bonds of fellowship. But it is not this day!
This day, we fight!"
"All you have to decide is what to do with the time that is given you."
SEE THE ALL NEW ROBOHELP X5 IN ACTION: RoboHelp X5 is a giant leap forward
in Help authoring technology, featuring Word 2003 support, Content Management, Multi-Author support, PDF and XML support and much more! http://www.macromedia.com/go/techwrldemo
COMPONENTONE DOC-TO-HELP 7 PROFESSIONAL: From a single set of Word documents, create online Help and printed documentation. New version offers yearly subscription service, Natural Search, Modular TOC Utility, Image Map Editor, Theme Designer, Context String Editor, plus more. http://www.componentone.com/doctohelp .
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.
Previous by Author:
Re: How do you read a User Manual
Next by Author: Re: TECHWR-L ADD Therapy
Previous by Thread: RE: Bi-directional traceability and docs
Next by Thread: Re: Bi-directional traceability and docs
Search our Technical Writing Archives & Magazine