Measurement objectives are refined into precise, quantifiable measures.
Measures may be either “base” or “derived.” Data for base measures are obtained by direct measurement. Data for derived measures come from other data, typically by combining two or more base measures.
Examples of commonly used base measures include the following: Estimates and actual measures of work product size (e.g., number of pages, number of line of code, number of test case); Estimates and actual measures of effort and cost (e.g., number of person hours); Quality measures (e.g., number of defects by severity, number of defects by development phase, number of bugs by testing phase).
Examples of commonly used derived measures include the following: Earned Value (hour); Schedule Performance Index (numerical); Defect density (%); Peer review coverage (%); Test or verification coverage (%); Reliability measures (numerical); Quality measures (numerical).
Derived measures typically are expressed as ratios, composite indices, or other aggregate summary measures. They are often more quantitatively reliable and meaningfully interpretable than the base measures used to generate them.
Typical Work Product in this specific practices is Specifications of base and derived measures.
To implement this specific practices, simply follow practices below:
1. Identify candidate measures (name and unit) based on documented measurement objectives.
2. Identify existing measures that already address the measurement objectives.
3. Specify operational definitions for the measures.
Measures may be either “base” or “derived.” Data for base measures are obtained by direct measurement. Data for derived measures come from other data, typically by combining two or more base measures.
Examples of commonly used base measures include the following: Estimates and actual measures of work product size (e.g., number of pages, number of line of code, number of test case); Estimates and actual measures of effort and cost (e.g., number of person hours); Quality measures (e.g., number of defects by severity, number of defects by development phase, number of bugs by testing phase).
Examples of commonly used derived measures include the following: Earned Value (hour); Schedule Performance Index (numerical); Defect density (%); Peer review coverage (%); Test or verification coverage (%); Reliability measures (numerical); Quality measures (numerical).
Derived measures typically are expressed as ratios, composite indices, or other aggregate summary measures. They are often more quantitatively reliable and meaningfully interpretable than the base measures used to generate them.
Typical Work Product in this specific practices is Specifications of base and derived measures.
To implement this specific practices, simply follow practices below:
1. Identify candidate measures (name and unit) based on documented measurement objectives.
2. Identify existing measures that already address the measurement objectives.
3. Specify operational definitions for the measures.
- Communication: What has been measured, how was it measured, what are the units of measure, and what has been included or excluded?
- Repeatability: Can the measurement be repeated, given the same definition, to get the same results?
- Proposed specifications of the measures are reviewed for their appropriateness with potential end users and other relevant stakeholders. Priorities are set or changed, and specifications of the measures are updated as necessary.
No comments:
Post a Comment