SOFTWARE METRICS

K.Hari Hara Ganesh Friday, July 26, 2013

SOFTWARE METRICS
What is Metrics Metric is a measure for quantitatively assessing, controlling or selecting a person, process, event, or institution

Metric along with the procedures to carry out measurements for the interpretation of the assessment in the light of previous or comparable assessments

SOFTWARE METRICS
What is Software Metrics A Software Metric is a measure of some property of a piece of Software or its specifications Since Quantitative methods have proved so powerful in the other sciences, Computer Science practitioners and theoreticians have worked hard to bring similar approaches to Software Development

SOFTWARE METRICS
Why Software Metrics As Mr.Tom DeMarco an American Software Engineer stated, You cannot control what you cannot measure

Software Metrics is the requirement CMM Capability Maturity Model

of

SOFTWARE METRICS
Difference between ISO 9001:2000 and CMM ISO 9001:2000 certification is for all types of Industries. It requires only documentation. You will not know till the end of the Project, where you are CMM certification is for Software Industry. It is Quantitative. At any point of time, using Metrics, you will know the status of the Project. If lagging in the schedule, by deploying additional resources, you will be able to complete the Project in Time

SOFTWARE METRICS
OWNER Example of Data Owned

Management

Schedules Budgets Time spent per task Inspection data including defects Root cause of defects
Test cases planned / executed / passed Problem reports from testing Test coverage Lines of code Modules changed Problem reports from operations Operational hours

Engineers

Testers

Configuration Management Specialists Users

SOFTWARE METRICS
CMM-Metrics Sl.No 1 2 21 22 23 3 31 4 41 5 51 52 6 Metric Parameters Size in Function Points( or Effort points) Effort in Mandays (Upto Product Release) Effort in Mandays (Implementation only) Total Effort Sl.No. (2 + 21) Effort Variance (Total Plan - Total Actual) / (Total Plan *100) Productivity (Up to Product Release) Function Productivity (for implementation ) Function Point Rework Effort in Mandays % Rework Effort (On total Project effort ) - Bug Fixing Etc. Project Duration ( upto FIR) in Days Delivery Variance in Days Delivery Variance in % (Delivery Variance / Project Duration) * 100 Defect Density (Total Defects / Function Points) Org. Goal 0 to -x >= >= <= >= <= Plan Actual 0.0 0.0 0 #REF! 0 #REF! 0 #REF! 0.0 #REF! 0.0 0.0 0 #REF! 0 0 Goal Org. Goal Achieved #REF! 0 to -17 #REF! #REF! #REF! #DIV/0! #REF! >= 2.0 >=6 < = 10 >= -20 < = 0,16

7 Defect Severity ( # of Serious Defects / Function <= Point) 8 Residual Defects Density (Impl. defects / <= Function Point) 9 Review effetiveness (Review Defects toTotal > = x% Functionality Defects) in % 10 Average Adjusted Defect Age (Sum of N S / 1 Sum of N) 11 Project Cost- Variance (Customisation Cost entered ) 12 Requirement Stability Index ( # of Changes to Reqs.To Ordered Reqs.)

#REF! <=0.016 #REF! <=0.016 #REF! #REF! #REF! #DIV/0! > = 40% 1 -

 SOFTWARE METRICS
CMM-Metrics Details 1 Phase Wise Defects Requirement Review Design Review Code Review Unit Testing Module Testing Integration Testing QC testing(Module Test included) Process Non Conformance and W/pdt audit During Implementation Post implementation Total Total Defects 2 Total Defects Identified at Review Functional Defects out of Process and W/pdt audit Total Functionality Defects = Review defs+Test Defs+Func.Defs of (Proc + W/Pdt) +Implem Defs 3 Defect Age No of Defects with Age 1 No of Defects with Age 2 Total Average Adjusted Age N = No. of Defects S = Square of Age NS = No. of Defects * Square of Age A B C

0 0

0 0

0 0 0 0 0 0

N S 0 0 0 0 0

NS 0 0 0 #DIV/0!

SOFTWARE METRICS
CMM-Metrics Phase wise Effort Variance in % Var = ((Sch - Act) / Sch) * 100 URS & RD / SRS % of Activity Effort To Total Effort Design Effort in Mandays % of Activity Effort To Total Effort Project Management Effort in Mandays % of Activity Effort To Total Effort Development Effort in Mandays % of Activity Effort To Total Effort Testing Effort in Mandays % of Activity Effort To Total Effort Implementation Effort in Mandays % of Activity Effort To Total Effort Rework Effort in Mandays % of Activity Effort To Total Effort Misc (Includes all documentation works, Usermanual etc.) % of Activity Effort To Total Effort Total Sch Act Var

1 2 3 4 5 6 7 8

SOFTWARE METRICS
Defect(s) Found during Requirement Study
1

Defect Age 20

Design Document
1

Development
1

Integration Testing
1

Implementation

24

Defect Age is the time between the Defect Identified Vs the Defect Injected The increase in Defect Age increases the 4Ms (Man, Money, Material & most importantly Minutes) of a Project

SOFTWARE METRICS
Conclusion A Metrics program that is based on the Goals of an Organization will help communicate, measure progress towards the Goal, and eventually attain those Goals Well-designed Metrics with documented objectives can help an Organization obtain the information it needs to continue to improve its Software Products, Processes, and Services while maintaining a focus on what is important A practical, systematic, start-to-finish method of selecting, designing, and implementing Software Metrics is a valuable aid

SOFTWARE METRICS

INTERACTIVE SESSION
Your experience on Projects
Questions / Queries

SOFTWARE METRICS

THANK YOU