The sample catalog contains implementations for user databases
based on the default ALM and Enterprise databases. In a customized
user database, the relationship between artifacts would be different
from the default implementation in the sample catalog but you can
create new builds or customize existing builds to load the relationships
in similar manner.
Because Rational® ClearQuest® data service has
the facility of retrieving the only that data which has changed since
a specific time, delta load is implemented in the sample ETL for ClearQuest data.
The default Enterprise schema does not have the concept of a project
concept but there could be a need to differentiate the data from different
user databases. Therefore, in the sample catalog, the names of the
resource group for the ClearQuest user
database in the XML Data Configuration file are treated as the names
of projects, and all artifacts from the user databases are associated
with these projects. For artifacts from the ClearQuest database, the dbid is used
as natural key and mapped to EXTERNAL_KEY1 in the tables in the data
warehouse.
State transition history data
In Rational ClearQuest, state transition history is
maintained for stateful record types. The loading of data to the sample
catalog happens as follows:
- Enterprise schema: history data for Defect and EnhancementRequest
- ALM schema: ALM request, task, and activity
The raw history data from the ClearQuest databases is stored in the
temporary tables in the data warehouse. During the ETL process, the
data is used for calculating the days a record remains in that state
and for mapping to
REQUEST_STATE_HISTORY,
TASK_STATE_HISTORY,
and
ACTIVITY_STATE_HISTORY. The data is used later
to populate the metrics related with the state transition trending.
Integrations
ClearQuest can be integrated with RequisitePro® and ClearCase®. Therefore, requirements
from RequisitePro and
configuration management artifacts from ClearCase can be associated with requests
and tasks in ClearQuest.
These relationships are available in ClearQuest data service if the integration
is configured in the products.
The sample catalog implements ETL
builds to load these relationships. The following keys are used as
the natural keys for the mappings:
- dbid and DATASOURCE_ID,
to match ClearQuest data
in the data warehouse.
- GUID for requirements, which should be globally
unique, to match requirement data from RequisitePro in the data warehouse
- global unique ID, to match ClearCase data in the data warehouse.
The ETL builds for these integrations are not included in
the ETL jobs of the sample catalog because the ETL process will fail
if the integrations are not setup in your environment. You can add
these builds to the jobs according to your measurement needs.
- Integration with RequisitePro
- ALM schema: The sample catalog implements the builds to load relationship
between ALM request and task, and requirements. The build names are CQ_ALM_Request_Requirement_Lkp and CQ_ALM_Task_Requirement_Lkp.
- Enterprise schema: The sample catalog implements the builds to
load relationship between:
- defect and enhancement request, and requirements. The names of
the builds are CQ_ENT_Defect_Requirement_Lookup and CQ_ENTEnhancement_Req_Lookup
- testplan, testcase, and configured testcase, and requirements.
The names of the builds are CQ_ENT_Requirement_TestPlan, CQ_ENT_Req_TestCase_Lookup,
and CQ_ENT_Require_CfgTest_Lookup.
- Integration with ClearCase
When ClearQuest is integrated with ClearCase in base mode, the ClearQuest artifacts are
associated with special changeset object in ClearQuest. The ClearQuest artifacts are associated with
information about source codes from ClearCase through relationship between changeset and
file versions in ClearCase.
The builds are:
- CQ_ALM_BaseCC_ChangeSet, CQ_ALM_Request_ChangeSet_Lookup,
and CQ_ALM_Change_FileVersion_Lookup for ClearQuest ALM integration
with ClearCase in base
mode.
- CQ_ENT_BaseCC_ChangeSet, CQ_ENT_Request_ChangeSet_Lookup,
and CQ_ENT_Change_FileVersion_Lookup for ClearQuest Enterprise integration
with ClearCase in base
mode.
When ClearQuest is
integrated with ClearCase in
UCM mode, the ClearQuest artifacts
are associated with UCM activity in ClearCase. The builds are:- CQ_ALM_Request_UCMActivity_Lkp for ClearQuest ALM integration
with ClearCase in UCM
mode.
- CQ_ENT_Defect_Activity_Lookup for ClearQuest Enterprise integration with ClearCase in UCM mode.