part two managing software projects

6
PART TWO Managing Software Projects Chapter 4 Metrics Measure 1 Measure 2 …… …… …… Measure n Metrics indicators

Upload: sirius

Post on 15-Jan-2016

22 views

Category:

Documents


0 download

DESCRIPTION

Metrics. PART TWO Managing Software Projects. Chapter 4 Metrics. Measure 1 Measure 2 …… …… …… Measure n. indicators. PART TWO – Managing - Metrics.  Size-Oriented Metrics. The normalization value: lines of code ( LOC ).  Errors per KLOC.  Errors per person-month. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: PART TWO Managing Software Projects

PART TWO Managing Software Projects

Chapter 4 Metrics

Measure 1Measure 2

………………

Measure n

Metricsindicators

Page 2: PART TWO Managing Software Projects

PART TWO – Managing - Metrics

Size-Oriented Metrics

The normalization value: lines of code (LOC)

Errors per KLOC

Defects per KLOC

$ per LOC

Page of documentation per KLOC

Errors per person-month

LOC per person-month

$ per Page of documentation

Programming language dependent

Penalize well-designed but shorter programs

Page 3: PART TWO Managing Software Projects

PART TWO – Managing - Metrics

Function-Oriented Metrics

The normalization value: function point (FP)

number of user inputs number of user outputs number of user inquiries number of files number of ext.interfaces

measurement parameter

3 4 3 7 5

countweighting factor

simple avg. complex

4 5 4 10 7

6 7 6 15 10

= = = = =

count-total

X X X X X

14

1

01.065.0totalcounti

iFFPComplexity adjustment

valuesp.91

LOC/FP Table on

p.94

Page 4: PART TWO Managing Software Projects

PART TWO – Managing - Metrics

Metrics for Software Quality

McCall & Cavano (1978)

ProductOperation

ProductRevision

ProductTransition

UnderstandabilityMaintainabilityFlexibilityTestability

PortabilityReusabilityInteroperability

CorrectnessRobustnessEfficiency

IntegrityUsabilityRisk

Page 5: PART TWO Managing Software Projects

PART TWO – Managing - Metrics

Correctness: defects / KLOC

Maintainability: Mean-Time-To-Change (MTTC)

Integrity: Threat – the probability that an attack of a specific type will occur within a given time;

Security – the probability that the attack of a specific type will be repelled.

attack

)security1()threat1(integrity

Usability: user-friendliness (Ch.15)

Defect Removal Efficiency (DRE) := E / (E+D)

Errors found before deliveryErrors found after delivery

Page 6: PART TWO Managing Software Projects

PART TWO – Managing - Metrics

Statistical Process Control: -- Control Chart [Walter Shewart 1920s]

1. Moving Range Control Chart

2. Individual Control Chart

data

projects

Mean valueStable

Unstable

Unstable