[Me] :- So what is software measurement and what’s the big deal?
[Guruji]:- Bill Hetzel once told – “It’s easy to get numbers, what is hard is to know they are right and understand what they mean”
There are many definitions, but for me - It’s “quantified observation” about any aspect of software (product, process or project).
There are lots and lots of measures. Primitive methods included - Number of staff assigned to project A, Pages of requirements specifications, Hours worked to accomplish change request X, Number of operational failures in system Y this year, Lines of code in program Z. Some computed measures include - Defects per 1000 lines of code in program A, Productivity in function points delivered by person B, Quality Score for project C, Average cigarette consumption per line of code, Accuracy of hours worked per week is ±20%. But what makes a good measure is that it should be – Simple, Objective, Easily collected, Robust and Valid