Showing posts with label analysis. Show all posts
Showing posts with label analysis. Show all posts

Monday, June 15, 2009

How analysis and reporting after data collection?

There are a few steps for analysis and reporting.
  • Periodically review the actual results
  • Apply quantitative and statistical techniques
  • Determine and document actions needed to address the deficiencies
  • The results of data analysis are reviewed with affected groups & individuals

  • Project Summary
  • Analysis Reports

Sunday, June 14, 2009

What are the activities that are suggesting measurement principles?

Activities are

  • Formulation
  • Collection
  • Analysis
  • Interpretation
  • Feedback



Principles for Formulation

  • The objectives of measurement should be established before data collection begins.
  • Each technical metric should be defined in an unambiguous manner.
  • Metrics should be derived based on a theory that is valid for the domain of application.
  • Metrics should be tailored to best accommodate specific products and processes.
Principles for Collection and Analysis

  • Whenever possible, data collection and analysis should be automated.
  • Valid statistical techniques should be applied to establish relationships between internal product attributes and external quality characteristics.
  • Interpretative guidelines and recommendations should be established for each metric.

What are the main steps of metric and measurement?

Here are the main steps.

  • Derive the software measures and metrics that are appropriate for the representation of software.
  • Data required to derive the formulated metrics are collected.
  • Once computed, appropriate metrics are analyzed on pre-established guidelines and past data.
  • The results of the analysis are interpreted to gain insight into the quality of the software, and the results of the interpretation lead to modification of work products arising out of analysis, design, code, or test.