Rational Insight sample metadata model

Creating a data model for use by a business intelligence reporting tool is an involved process that requires a deep understanding of the business process being studied. IBM® Rational® Insight provides sample data models that can be customized by users to build their own models.
The metrics provides a means of measuring activities in the software lifecycle management. It contains data for over a period of time. You can therefore establish a trend. Some of the metrics also capture the current snapshot. These contain only the latest data. metrics

Change management

The change management data model contains metrics about requests and tasks.

Request aging (includes current snapshot)

This metric is a measure of the maximum, average, and minimum days that requests spend in a particular state and the number of requests in a particular state.

Request creation

This is a measure of the arrival rate of requests.

Request closure

This metric is a computation of the closure rate of requests.

Request failure (includes current snapshot)

This is a measure of the number of requests failing at a particular time or over a given period.

Request (includes current snapshot)

The measurement includes the total number of requests and blocking requests planned and actually handled.

Request turnaround (includes current snapshot)

This is a set of measures defined by the maximum, average, and minimum days for a request to move from the Submit state to Resolve state, and the number of requests that move from one state to the other over a given period.

Request Resolution This metric provides information about the resolution rate of requests. It is measured by the total number of requests.

Some of the other request metrics in this model are:

Task (includes current snapshot)

This metric is defined as the number of tasks active at a particular time or during a given period.

Task creation

This metric is defined as the rate of arrival of tasks.

Task closure (includes current snapshot)

This metric is defined as the rate at which tasks are closed.

Task closure with component

This metric is defined as the rate at which tasks are closed with respect to a component.

Time to market release

This metrics defines total days that a project or a product it takes from beginning to release.

Report Planned Data

This metrics is for users to input planned data, then to combine and compare with actual data. It provides target, upper limit and lower limit

Some of the other task metrics in this model are:
  • Task with component (includes current snapshot)
  • Task creation with component
  • Task closure with component

Configuration management

This subject model tracks metrics about activities, builds, and file versions.

Activity (includes current snapshot)

This metric computes the number of activities of various kinds active at any point or over a given period.

Activity creation

This is a measure of the arrival rate of activities.

Build execution

This is a set of metrics containing the number of builds executed, the number failed, and the number succeeded, based on the end time of the build.

Build (includes current snapshot)

This is a set of metrics containing the number of builds executed over a given interval, the number failed, and the number succeeded.

File stream (includes current snapshot)

This is a set of metrics that provides a summary of the content under configuration management system at any particular point in time or over a given interval. The measurements include total item count, compressed total content, and uncompressed total content.

Text file change (includes current snapshot)

This is a set of metrics that provides information about content changes under a configuration management system based on date. The measurements include change set addition count, change set deletion count, file addition count, file deletion count, file modification count, folder addition count, folder deletion count, folder modification count, size decrease, and size increase.

Text file version

This metrics provides information about file versions under a configuration management system at a particular time or over a period of time. The measurements include total SLOC in the version and number of SLOC changed from the previous version.

Text file version creation

This metric provides information about file versions under a configuration management system based on the creation date of the file version. The measurements include total SLOC in a version and number of SLOC changed from the previous version.

Some of the other metrics in this model are:
  • Activity creation with iteration
  • Activity creation with requirement
  • Build with request (includes current snapshot)
  • Build with requirement (includes current snapshot)
  • Text file version (includes current snapshot)
  • Text file version with request (includes current snapshot)
  • Text file version creation with request

Project Management

Project Performance Metrics

This sample model contains metrics about project performance. It contains measurements such as Actual cost of work performed (ACWP), Budgeted at completion (BAC), Budgeted cost of work scheduled (BCWP), Cost performance index (CPI), Cost variance (CV), Estimate at completion (EAC), Schedule variance (SV), and Variance at completion (VAC).

Quality Management

This sample model tracks metrics about test information, execution results, test cases, test suites, and builds.

Execution result date

This metric provides information about execution results (test logs) based on their generating date. The measurement is the total number of execution results (test logs).

Execution result (includes current snapshot)

This metric provides information about execution results (test logs) at a particular time or over time. The measurement is the total number of execution results (test logs).

Execution result point

This is a set of metrics containing the number of builds executed over a given interval, the number failed, and the number succeeded.

Execution work item (includes current snapshot)

This metric is defined by the number of execution work items (configured test cases) and their total weight at any point or over a given interval.

Lab utilization

This metric provides information about utilization of lab resources based on their reservation date. It is includes the number of machines and reserved machines.

Test case (includes current snapshot)

This metric is defined by the number of test cases active at any point or over a given interval.

Test suite This metric is defined by the number of test suites.

Some of the other metrics in this model are:
  • Execution result with iteration (includes current snapshot)
  • Execution work item with iteration (has both history trending and current snapshot)
  • Execution work item with requirement (has both history trending and current snapshot)
  • Job execution

Requirements Management

This sample model tracks metrics on requirements.

Child requirement (includes current snapshot)

This metric is defined by the number of child requirements at a particular point or over a given period.

Requirement (includes current snapshot)

This is set of metrics that includes the number of requirements and the number of changes to them measured over any given period.

Requirement traceability

This is not a metric, it provides detailed information about requirement related resources, such as, trace to requirement, trace from requirement, parent requirement, child requirement, customer, request, test case, test plan, test suite, execution work item, activity, and task.

  • Requirement with test case (includes current snapshot)
  • Requirement with test plan (includes current snapshot)

Operational Data Store

operational data store
This contains operational data from the data source and is divided into different areas. Each area contains detailed information about the relationships between different objects in the model.


Feedback