Development documentation

Thanks for the reply and apologies for being unclear. The sentence was an inquiry into two things:
1. Whether the RTC/jazz Team used RTC for creating the documentation of RTC?
2. Is RTC being used for creating documentation for development teams in general?

I am trying to find out whether RTC would be able to support development teams in writing their documentation and storing that in a versioning system.

I found a link today on the website that explains how to manage word docs with RTC and Jazz SCM:
https://jazz.net/learn/LearnItem.jsp?href=content/docs/source-control/compareworddocs/index.html

Do you talk about documentation in general or documentation about our
own development process. It's unclear to me reading the sentence above.

Kai
Jazz Process team


JanVdP wrote:
> Do you guys use RTC for documenting (its) development?

The documentation we do manage with RTC is simple HTML documents stored
as normal files in Jazz SCM. The projects from the SCM are
automatically exported to a external website so that viewing outside of
RTC is easy.

It would probably be possible to make a Jazz extension that has more
official management and tracking of documentation, but I don't know of one.

JanVdP wrote:

Would RTC be useful to create documentation for a development
project?

Do you guys use RTC for documenting (its) development? Have you
considered other options such as Rational Asset Manager, plane word
docs,...?