IEEE Std 1061-1992 IEEE Standard for a Software Quality Metrics Methodology -Description

Abstract: A methodology for establishing quality requirements and identifying, implementing, analyzing, and validating the process and product of software quality metrics is defined. The methodology spans the entire software life cycle. Although this standard includes examples of metrics, this standard does not prescribe specific metrics.

Keywords: direct metric, factor, metrics framework, software quality metric, subfactor

Content

• 1. Overview
• • 1.1 Scope
  • 1.2 Audience
• 2. Definitions
• 3. Purpose of software quality metrics
• 4. Software quality metrics framework
• 5. The software quality metrics methodology
• • 5.1 Establish software quality requirements
  • • 5.1.1 Identify a list of possible quality requirements
    • 5.1.2 Determine the actual list of quality requirements
    • 5.1.3 Quantify each factor
  • 5.2 Identify software quality metrics
  • • 5.2.1 Apply the software quality metrics framework
    • 5.2.2 Perform a cost-benefit analysis
    • 5.2.3 Gain commitment to the metrics set
  • 5.3 Implement the software quality metrics
  • • 5.3.1 Define the data collection procedures
    • 5.3.2 Prototype the measurement process
    • 5.3.3 Collect the data and compute the metrics values
  • 5.4 Analyze the software metrics results
  • • 5.4.1 Interpret the results
    • 5.4.2 Identify software quality
    • 5.4.3 Make software quality predictions
    • 5.4.4 Ensure compliance with requirements
  • 5.5 Validate the software quality metrics
  • • 5.5.1 Purpose of metrics validation
    • 5.5.2 Validity criteria
    • 5.5.3 Validation procedure
    • 5.5.4 Additional requirements
  • B.1 Detailed metrics descriptions
  • • B.1.1 Halstead - software science
    • B.1.2 Boehm - constructive cost model (COCOMO)
    • B.1.3 Albrecht - function points
    • B.1.4 McCabe - cyclomatic complexity
  • B.2 Sample metrics results
  • • B.2.1 Halstead effort
    • B.2.2 Halstead difficulty
    • B.2.3 McCabe complexity V(G)
    • B.2.4 Source of software error
    • B.2.5 Number of changes that affect module
    • B.2.6 Defect metrics
    • B.2.7 Traceability
    • B.2.8 Number of program paths (Np)
  • C.1 Mission critical example
  • • C.1.1 Establish software quality requirements
    • C.1.2 Identify software quality metrics
    • C.1.3 Implement the software quality metrics
    • C.1.4 Analyze the software metrics results
    • C.1.5 Validate the software quality metrics
  • C.2 Example from a commercial environment
  • • C.2.1 Establish software quality requirements
    • C.2.2 Identify software quality metrics
    • C.2.3 Implement the software quality metrics
    • C.2.4 Analyze the software metrics results
  • D.1 Annotated bibliography
  • D.2 Bibliography
  • D.3 Standards and related documents

links: [Standard Status] - [Purchase] - [PDF^*] - [Software Engineering Collection - Description]

available for Standards Online Software Engineering Collection subscribers only