Software Testing with the Use of Metrics

Measurement is the key to managing the software testing process. Software Metrics can aid in improving your organizations testing process by (1) providing insight and early visibility into the "real" status of the testing effort, and (2) aid in making assessments as to whether progress, productivity and quality goals are being met. This Software Testing With The Use of Metrics training course presents a practical guide on how to start taking advantage of these new tools/techniques to aid in improving the testing process. These metric based tools and techniques have successfully been used by (1) software test teams, (2) software developers and, (3) SQA/IV&V staffs.

This Software Testing With The Use of Metrics is designed for Intermediate/advanced level professionals.

A practical overview of metrics-based testing designed for technical and managerial professionals concerned with improving quality, performance, and productivity of software testing.

By attending Software Testing With The Use of Metrics workshop, Delegates will learn:

  • A set of government/industry "best practices" metrics with numerous examples, variations , and case studies. These metrics can track the "real status", quality, and productivity of the testing effort, as well as provide an indication of future problems.
  • Goal-Question-Metric. An overview of Software Quality Goals, Criteria and Metrics as well as a framework for developing customized testing goals and metrics to measure if these goals are being met.
  • Requirements Testability. Metrics that can be used in the Requirement Phase. .
  • Software Complexity Metrics: A new Structured Testing methodology that uses metrics to aid in (1) developing software that is easier to test and maintain, and (2) selecting an appropriate set of paths for more thorough testing.
  • How to integrate software metrics into the testing process

COURSE AGENDA

  • Software Complexity
  • McCabes Complexity Metric
  • Drawing a Flowgraph
  • Computation of McCabes Metrics
  • Properties of a Complexity Metric
  • Using McCabes metric for identifying program paths for testing
  • Science and Measurement
  • Conceptual Framework
  • Tradeoffs among Factors
  • Examples of Tradeoffs
  • Classifications of a Metric
  • Properties of a Good Metric
  • Goal-Question-Metric Framework
  • Survey of S/W risks and cost drivers
  • Requirements Volatility Metrics
  • Requirements Change Metrics
  • Requirements Progress Metrics
  • Criteria for Good Requirements
  • Analysis of Requirement Errors
  • Requirement Tracing Metrics
  • Testable /Non-Testable Requirements
  • Unit Testing Progress Metrics
  • Integration testing Progress metrics
  • Depth of Testing Metrics
  • Branch/Statement Testing Coverage
  • Code Complexity Metrics
  • System Testing Progress metrics
  • Fault Tracking Metrics
  • Defect Containment Metrics
  • S/W Size
  • Test Team Personnel Metrics
  • Software measurement principles
  • SEI Core Metrics
  • Case Studies
  • The Cost of Inadequate S/W Testing
  • Crises-Driven Development
  • Software Growth
  • Problems due to Growth in Size
  • How S/W Metrics can aid in Testing
  • High cost of testing
  • What is testing?
  • Problems in testing
  • Latent Error Correction Costs
  • Software Error Introduction and Discovery