RE: Documentation in Rational Unified Process; SoDA

["Michael Collier" <mcollier -at- arlut -dot- utexas -dot- edu>]

Brent wrote:

> Our company is evaluating the Rational Unified Process (RUP) and its
> associated tools as a possible internal development process.
>I see little provision, either in the process itself or the
> tools, for the tasks involved in producing end-user materials.

I'm not sure what you're expecting to see from Rational regarding the
production of end-user documents. The Rational process is for software
engineering, and as we all know,  well-engineered software has no need for
user docs (or users, for that matter? -:)

I haven't been exposed to any recent versions of Rational, but as I recall
it's documentation provisions are for engineering docs, as you've noted. But
others more familiar with it have have more to say about what it can do.

One thing to check for is some kind of traceability tool that forces a
mapping of requirements and use cases to design. You may be able to export
some of this data to an office application and outline your user docs from
there.

What exactly would you like to see Rational (or products like it) provide
for the production of user docs? Perhaps a CASE vendor will be willing to
listen and implement something useful.

...........................................................................
...
Michael Collier                 	Phone:  512-835-3408
Information Systems Laboratory  	FAX:    512-490-4254
ARL			 		Office: AX207
University of Texas at Austin   	email:  mcollier -at- arlut -dot- utexas -dot- edu
...........................................................................
...
>