Reporting Documentation developerWorks Getting Started

There are various ways of reporting with the CLM suite. There are no good or bad in this listing, take what fits your needs. There are several overlaps across the various ways of reporting.

Note! Alternatively take a look a "RELM".
Reporting OptionMy Comments, based on my experience and knowledge
DashboardVarious viewlets and queries on 1 screen Very valuable to define viewlets which are used by all team members. Individual dashboards can be created to fit personal needs.
Print featurePrint of individual or hierarchy documents, embedded in the application, little to no options to customize.
Export to PDFRQM Reports can be exported to
  • PDF
  • Postscript
  • Excel
  • Word
  • Powerpoint

Figure: RQM Report, export options.

Reporting with RQM RQM Out of the Box reports
Will cover large deal of reporting request.
Complete list of reports available

Figure: A Basic Test Result report

Query (table & graphs) can be used for RPE post processing.
Documentation is often a deliverable
- Specifications are often written in one project phase and then passed into the following phase, e.g. a requirements document is handed off to a design team
- Specifications may be contractual deliverables, e.g. the completion of a specification may be an exit criteria for a project phase, and trigger a payment
- Specifications may have to comply with standards, e.g. U.S. Defense Standards (MIL-STD,FDA)

Figure: A page from a document generated with the Comprehensive Test Plan Template.

What is the main difference between RPE and RRDI?

Both techniques are very powerfull can for the basic reporting both options are viable. Still there are signifcant diifferences when you take a closer look at both options.

In one line: Textual documents check first RPE technology, when you want to have statistical information start with RRDI.