Showing posts with label metrics and measurement. Show all posts
Showing posts with label metrics and measurement. Show all posts

Wednesday, June 30, 2010

What-is-Testing-Process-Performance-Model-(TPPM)-activity?

Testing PPM activity

Testing PPM activity can be logically divided into following Sub-Activities.

  • Estimations-here estimations are done
  • Actual Measurement Entry - here we come with actual measures
  • Statistical Analysis - we are doing analysis for the estimations and measure in this activity

Monday, June 15, 2009

What-is-Testing-Process-Performance-Model-(TPPM)-activity?

Testing PPM activity

Testing PPM activity can be logically divided into following Sub-Activities.

  • Estimations-here estimations are done
  • Actual Measurement Entry - here we come with actual measures
  • Statistical Analysis - we are doing analysis for the estimations and measure in this activity

Sunday, June 14, 2009

What are the business objective of metrics and measurements?

These are business objectives

  • Project must be signed-off on time with maximum 15% schedule variance.
  • Estimation Accuracy (EA) of Effort, & Cost must be within 0.85 to 1.15.
  • 100 % of signed off requirements should be implemented in final delivery.
  • After system sign-off re-work effort on bugs must not exceed 5% of total effort on development per year.
  • At least 80% of resource and time utilization must be ensured for each resource.
  • Achieve at least 20% profit on average for each project.
  • Employee turnover should not be more than 8% during a year.
  • Exploration of two technologies during a year, and one of them must be used.
  • At least 90% of Critical/Major bug requests should be serviced as per agreement during a year (as per PM’s discretion that change request is Critical/Major).
  • At least 10% of the total leads should be materialized by Business Development during the year.
  • Employees satisfaction index (ESI)
  • Conduct at least one market survey per year

What is the relationship of Metrics and Measurement and Quality?

Here are the points to be noted

  • Software requirements are the foundation from which quality is measured. Lack of conformance to requirements is lack of quality.
  • Specified standards define a set of development criteria that guide the manner in which software is engineered. If the criteria are not followed, lack of quality will almost surely result.
  • There is a set of implicit requirements that often goes unmentioned (e.g., the desire for ease of use). If software conforms to its explicit requirements but fails to meet implicit requirements, software quality is suspect.

So there is relationship. As we have measurement correct we will have solid requirements and on that at the quality will be fine

How do ensure that Metrics and mesasurements are correct?

There are two things to do for ensuring that these are correct.

  • Establish the objectives of measurement before data collection begins, defining each technical metric in an unambiguous manner.
  • Define a few metrics and then use them to gain insight into the quality of a software engineering work product.

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.

What is software metric?

Software Metric
Software metric is measure of some property of a piece of software or its specifications.

It provides with quantitative information to make the process better by analyzing that information.

Tuesday, March 24, 2009

How software quality can be achieved?

Achievement of quality would be easy if we are doing the things
  • Apply software engineering methods in effective manner
  • Perform formal technical reviews as per required
  • Software metrics and measurements
  • By testing the software on the right time
  • SCM(Software Configuration Management) and SQA(Software Quality Assurance)
  • and by following standards and procedures.
After doing the above steps you would be able to get a quality product