12
LOGO “ Add your company slogan ” Software Measurement & Analysis Team Assignment 2 TEAM 21 P&G TEAM Team Assignment 3

Software Measurement & Analysis

  • Upload
    bunme

  • View
    50

  • Download
    0

Embed Size (px)

DESCRIPTION

Team Assignment 2. Team 21 P&G Team. Team Assignment 3. Software Measurement & Analysis. Contents. Goal. 1. Questions. 2. Metrics. 3. Data Elements Supporting. 4. GQM Chart . 3. Goal. Reduce defects found by system test by 10 %. Goal. Questions. Metrics. Metrics. Metrics. - PowerPoint PPT Presentation

Citation preview

Page 1: Software Measurement & Analysis

LOGO

“ Add your company slogan ”

Software Measurement & Analysis

Team Assignment 2

TEAM 21P&G TEAM

Team Assignment 3

Page 2: Software Measurement & Analysis

Contents

Goal1

Questions2

Metrics3

Data Elements Supporting4

GQM Chart 3

Page 3: Software Measurement & Analysis

Goal

Reduce defects found by system test by 10%

Page 4: Software Measurement & Analysis

GoalAnalyze

(The object under measure)

Number of defect found by system test

For the purpose of

(Understanding, controlling, or improving the object)

Controlling and improving

With respect to

(The quality focus of the object that the measurement focuses on)

The detection of defects

(Including: Product Features, Product Quality, Value, Timeliness, Teamwork, Front line Service Behaviors, Commitment to the Customer, Innovation…)

From the viewpoint of

(The people that measure the object)

Project team

In the context of

(The environment in which the measurement takes place)

Viking Project

Page 5: Software Measurement & Analysis

QuestionsID Question

Q1 What is the defect rate in Matador Project in system test phase?

Q2 What is the defect rate in Viking Project in system test phase?Q3 How to know the number of defect found by system test reduce 10%?

Q4 How many defect found in period time (weeks/months) Viking Project in system test phase? And How does it change over time?

Q5 The defect still exist in previous test phase is counted for system test phase of not?

Q6 How many defects still exist in previous test phase?

Q7 How many defects found by system test in previous work package but didn’t fix?

Q8 How long to fix a defect?

Q9 How to know the ability to find defect by tester in system test?

Q10 How to know the probability of implicit defect in product?

Page 6: Software Measurement & Analysis

MetricsID Metric Metric Formula Describes Mapping

with

M1 Defect Destiny

(1 - )*100%OrDefects/ Function point

 

Project team can compare defect ratio between two projects that maybe increase or reduce

Q1, Q2, Q3

M2 Number of Unresolved Defects

Total of found defects in the last phase – Number of fixed current defects

Project team can count number of defects that unresolved at the moment, to plus them for number of defects in the next phase.

Q4, Q5, Q6

M3 Mean Age of Unresolved Defects

 

 ((Current date & time of unresolved defect #1 - registration date & time unresolved defect #1) + ... +  (Current date & time of unresolved defect #N - registration date & time of unresolved defect #N)) / total number of unresolved defects

Project team can know mean age of unresolved defects to assign priority for that defects, help project team find solution to improve it.

Q7, Q8

Page 7: Software Measurement & Analysis

MetricsID Metric Metric Formula Describes Mapping

withM4 Defect

Removal Efficiency

 

DRE = Number of defects resolved during a work package / total number of defects found at the moment work package

Project team can know ability to remove defects of the current team.

Q7, Q8

M5 Defect trend

(Number of current defect -number of old defect)/(Number of old defect)*100%

Project team can know number of defect at system test phase of two consequential work package that increase or reduce

Q4, Q5, Q6

Page 8: Software Measurement & Analysis

MetricsID Metric Metric Formula Describes Mapping

withM6 Defect

SeedingFound defect / seeded defect

 

Project team can know ability of testing team in two projects (Viking and Matador), to compare generally and precisely.

Q9, Q10

M7 Defect Pooling

DefectsTotal = ( DefectsA * DefectsB ) / DefectsA&B

Project team can know ability of testing team in two projects (Viking and Matador), to compare generally and precisely.

Q9, Q10

Page 9: Software Measurement & Analysis

Data Elements SupportingData elements Describes

Number of defects for Viking

Number of defect that detect in the Viking project

Number of defect for Matador

Number of defect that detect in the Matador project

Function point Function point is a measure of the amount of business functionality in a software product.

Current date & time of unresolved defect #1

Current date and time of a defect

Registration date & time unresolved defect #1

Date and time that found the defect in defect tracking system

Number of defects resolved

Number of defect that not fix at the moment

Page 10: Software Measurement & Analysis

Data Elements SupportingData elements Describes

Total number of defects found at the moment

Total number of defects found at the moment

Number of current defect

Number of the current defect in a work package

Number of old defect Number of the defect in the last work package with the above work package

DefectsA Number of defects that found by testing team of Viking project

DefectsB Number of defects that found by testing team of Matador project

Page 11: Software Measurement & Analysis

GQM Chart

Page 12: Software Measurement & Analysis

LOGO

“ Add your company slogan ”