Information Retrieval and Domains

When you create a ProjectConsole Template Builder template you must determine what information will act as sources to the Web page. ProjectConsole uses special programs called domains to extract information. Each domain understands a single source of information, such as Rational Rose and the File System.

Embedded in each domain is the knowledge of how information is modeled by that source, using classes, attributes, and relationships. For example, the Rose domain understands that a class category:

§  Has attributes of name and documentation

§  Contains relationships to classes

§  Has import relationships to other packages

This domain-specific knowledge enables you to retrieve the specific information you want to document.

ProjectConsole supports multiple domains, even within the same Web page. This means that project team members need to use (and learn) only one documentation tool throughout the software lifecycle, rather than using different tools that are unique to design, coding, or testing.

Dynamic Domains

Some domains, most notably ClearQuest and RequisitePro, are dynamic domains. Both of these domains have a small number of default objects. As these products are implemented, additional site-specific, dynamic, objects are added—database specific objects for ClearQuest and project-specific objects for RequisitePro. When you design templates, these custom objects become available for reporting.

Source Domain Schema

Each domain that ProjectConsole Template Builder uses is defined by a source domain schema. The schema contains information about all of the objects in the domain and the relationships of those objects to one another. Schemas are defined using object-oriented methods. Therefore, the concepts and terminology used to describe schemas are also object oriented.

You can extend the schema of source domains. See Domain Extensions for information.

To get reference information about each domain, click Help > Help on Domains, then click the specific domain