Software metrics
Upcoming SlideShare
Loading in...5
×
 

Software metrics

on

  • 640 views

Basic software metrics are discussed

Basic software metrics are discussed

Statistics

Views

Total Views
640
Views on SlideShare
640
Embed Views
0

Actions

Likes
0
Downloads
43
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Software metrics Software metrics Presentation Transcript

  • Software MetricsSivaraam Duraisamy
  •  Measurement – Data Metrics – Analyzed ResultMetrics
  •  Size Function Points Feature Points Story Points Person Days Lines of Code Effort Person Days/Months Complexity Requirements Change Requests Database size Test Cases Defects found at source Defects found at customer endMeasurements in Software
  •  Metrics helps the team to have a control over the projects to take corrective actions to align with the goals better estimations to know where team stands on the expectation improve trust improve confidenceMetrics
  •  Effort Variation Organizations’ main objective is to make profit Profit = Revenue – expenses Most of the proposals are done based on the efforts estimated The gap between the effort estimated and the actual effortsspent decides the profit So the effort variation is one of the important factor that decidesthe success of the projectEffort Variation =(Actual Effort Spent - Estimated Effort)-------------------------------------------------------------------------------------------Estimated EffortMetrics – Organization Requirements
  •  Size Variation Organizations’ main objective is to make profit Profit = Revenue – expenses Proposals are done based on the size of the projects Normally the requirements are changing throughout the lifecycle The gap between the size estimated and the actual size alsoplays a major role in deciding the profit So the size variation is one of the important factor that decidesthe success of the project(Actual Size - Estimated Size)Size Variation = --------------------------------------------------------Estimated SizeMetrics – Organization Requirements
  •  Schedule Variation Delivery on time is one of the primary factor to win the customersatisfaction, which may bring the continued business Delivery on time increase the trust on the producer by the client Delayed delivery may lead to loss to producer as well as theclient So schedule variation is also one of the key factor in deciding thecontinued and enhanced businessSchedule Variation =(Actual Delivery Date – Committed Delivery Date )-------------------------------------------------------------------------------------------Duration of the project in calendar daysMetrics – Organization Requirements(Contd…)
  •  Scope Coverage In the case of the projects following Agile-Scrum, everything is time boxed So no chance of schedule variation The deviation will be on Scope covered only Agile Scrum teams forecast the deliverables in terms of scope Delivery as per the forecast increase the trust on the team by the customer Delivery as per the forecast also make the teams life easier for furtherplanning More and frequent de-scoping will affect the performance of the scrumteam So scope coverage is also one of the key factor in the projects following AgileScrumScope CompletedScope Coverage = ----------------------------------------------------------Scope ForecastedMetrics – Organization Requirements(Contd…)
  •  Customer Reported Defects For a continued business, customer trust is an importantone Delivered Quality Product is one of the factor whichincreases trust If the delivery is made on time without quality is also aproblem Quality of the product is decided by the client based on thenumber of defects found at the customer place That too if the defects are blocking their activity, resultingin business loss will severely affect the businessrelationship So the top priority we can say there shouldnot be any blocker defects at customer endMetrics – Organization Requirements(Contd…)
  •  Customer Reported Defects At the same time it is much difficult to completely avoid thedefects As a goal, fixing the count of the defects is also not good,because the count of defect depends on the size of the project Defect Leakage is the metrics which will help to work towardsminimizing the defects at customer endDefect Leakage =Defects reported by the Client--------------------------------------------------------------------------------------------Defect found during development by the team + Defects reported by the ClientMetrics – Organization Requirements(Contd…)
  •  Organization also require some more metrics fromother departments like Human ResourceDepartment, System Administration, GeneralAdministration…etc. They need not be categorized under softwaremetricsMetrics – Organization Requirements(Contd…)
  •  Projects wants Effort Deviation Schedule Deviation Scope Coverage Defects Leakage Projects also want Requirement StabilityMetrics – Project Requirements
  •  Requirement Stability Because of the changes in the requirements the team may face Wastage of effort because of the change in requirements done on the finishedfeatures More effort because of additional requirements Long hours work or week end work because delivery pressure along with changesin requirements The metrics on the requirements stability will help the team to forecast theirquantum of deliverables The root cause analyzes on the change in requirements along with the correctiveaction will help in minimizing the changes by improving the requirement studymethodRequirements Stability =Total no of features underwent changes + No of new features added------------------------------------------------------------------------------------------------------------------------Total no of features initially givenMetrics – Project Requirements(Contd…)
  •  Few of the metrics which may not be directly needed by theorganization and projects, but needed by the individuals fortheir own development Defects found during Unit Testing Defects found by the testing team Quality of code developedMetrics – Individuals
  •  Defect found during Unit testing Normally the Unit testing is done by the developer on his/her codedeveloped The count of the defect found in a unit of work done, shows thedevelopers competitiveness He/she can take corrective actions to bring it down to improve his/herefficiency The self confidence improves when the defect count goes down Code Quality The code quality may be measured based on the comments receivedthrough manual / automated code reviews The learning and the corrective actions taken will improve the codequality The performance of the system also improve considerablyMetrics – Individuals (Contd…)
  •  Only the basic software metrics are discussed Though the categorization is made as Organization,Project and Individual, all the metrics help all. Thecategorization is made based on the primarybeneficiarySoftware Metrics
  • THANK YOUsivaraam_sai@yahoo.co.in
  •  Steve McConne. “Software Estimation”, 2006,Microsoft Corporation.Further Reading