Measurement Information Specification

Version 1.0

 

[Note: The following template is provided for use with the Rational Unified Process (RUP), and is designed for use in conjunction with the detailed guidance provided within RUP. As with most of the templates provided with RUP, this template should be customized to suit the context of the specific project it will be used on.] 

 [Note: Text such as this you are currently reading ̵; enclosed in square brackets and displayed in blue italics (style=InfoBlue) ̵; is included to provide guidance to the document author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]

Guidelines for Using the Measurement Information Specification Template

As you start working with this template, consider first the reasons for doing measurement.  Identify the information need or issue for which you want measure-supported information.  Use the template in the following order:


Measurement Information Specification Template

 

Information Need Description

Information Need

Identify what the measurement user (e.g., manager or project team member) needs to know in order to make informed decisions.

 

Information  Category

Identify the PSM standard information category name (such as Schedule and Progress), or indicate that this is a new category.

 

Measurable Concept

Measurable Concept

Name or describe the concept (an idea for satisfying the information need by using relevant entities and their attributes). See the PSM I-C-M table for examples, such as Milestone Completion.

 

Entities and Attributes

Relevant Entities

Identify the entity (object) that is to be measured.  Entities include process or product elements of a project.

1.     
2.     
3.     

Attributes

For each entity, identify one or more attributes (properties or characteristics) that will be quantified. [Note: for automated measurement, this must be the precise database element or other direct source of data.]

1.     
2.     
3.     

 

Base Measure Specification

Base Measures

Identify base measures to support the information need. A base measure is a measure of a single attribute defined by a specified measurement method (e.g., planned number of lines of code, cumulative cost to date).  As data is collected, a value is assigned to a base measure.

1.     
2.     

3.     

Measurement Methods

Identify the logical sequence of operations that define the counting rule to calculate each base measure (such as counting semicolons for code size).

1.     
2.     
3.     

Type of Method

Identify the type of method used, either subjective (relying on human judgment) or objective (quantification).

1.     
2.     
3.     

Scale

Identify the set of values, or set of categories, for the attribute measured (e.g. integer values greater than 0).

1.     
2.     
3.     

Type of Scale

Identify the type of scale - ratio (numeric data, 0 to infinity), interval (numeric data, 1 to infinity), ordinal (rankings), or nominal (categories).

1.     
2.     
3.     

Unit of Measurement

Identify the standardized quantitative amount that will be counted to derive the value of each base measure, such as an hour or a page of text.

1.     
2.     
3.     

Derived Measure Specification

Derived Measure

Describe any derived measures used.  A derived measure is developed as a function of two or more values of base measures.

1.     
2.     

Measurement Function

Identify the formula used to calculate each derived measure.

1.     
2.     

Indicator Specification

Indicator Description and Sample

Provide a description and a display of one or more measures (base and derived) to support the user in deriving information for analysis and decision-making.  An indicator is often displayed as a graph or chart.

 

Analysis Model

Describe algorithms to be used with the measures.  As needed, describe the underlying model of expected behavior of the measures over time.

 

Decision Criteria

Identify thresholds, limits, and targets used to trigger action or further investigation.

 

Indicator Interpretation (sample chart)

For sample measures only, describe how the indicator in question was interpreted, and what decisions were made as a result.

 

Data Collection Procedure (For Each Base Measure)

Frequency of Data Collection

Identify how often a measure will be collected (e.g. monthly, weekly).

1.     
2.     
3.     

Responsible Individual

Identify who is responsible for data collection and validation.

1.     
2.     
3.     

Phase or Activity in which Collected

Identify lifecycle phases or activities when this data is collected.

1.     
2.     
3.     

Tools Used in Data Collection

Identify tools used for data collection.

1.     
2.     
3.     

Verification and Validation

Identify methods used to verify and validate the data.

1.     
2.     
3.     

Repository for Collected Data

Identify where the identified data will be stored.

1.     
2.     
3.     


Data Analysis Procedure (For Each Indicator)

Frequency of Data Reporting

Identify how often an indicator will be generated (e.g. monthly, weekly).

1.     
2.     
3.     

Responsible Individual

Identify who is responsible for data analysis.

1.     
2.     
3.     

Phase or Activity in which Analyzed

Identify the lifecycle phase or activity during which analysis will be performed.

1.     
2.     
3.     

Source of Data for Analysis

Identify the source of the data to be analyzed.

1.     
2.     
3.     

Tools Used in Analysis

Identify any tools to be used in the analysis.

1.     
2.     
3.     

Review, Report, or User

Identify where the analysis will be reported and used (e.g. design review, monthly program review).

1.     
2.     
3.     

Additional Information

Additional Analysis Guidance

Provide any additional guidance that the measurement analyst should consider during the analysis.  Indicate related indicators or measures.  Indicate any additional decision criteria that may be considered at a later date.

 

Implementation Considerations

Provide any implementation considerations that the measurement analyst should keep in mind.  Identify any lessons learned or guidance.