Software metric

From Wikipedia, the free encyclopedia

A software metric is a measure of some property of a piece of software or its specifications. Since quantitative measurements are essential in all sciences, there is a continuous effort by computer science practitioners and theoreticians to bring similar approaches to software development. The goal is obtaining objective, reproducible and quantifiable measurements, which may have numerous valuable applications in schedule and budget planning, cost estimation, quality assurance testing, software debugging, software performance optimization, and optimal personnel task assignments.

Common software measurements

Common software measurements include:

Limitations

As software development is a complex process, with high variance on both methodologies and objectives, it is difficult to define or measure software qualities and quantities and to determine a valid and concurrent measurement metric, especially when making such a prediction prior to the detail design. Another source of difficulty and debate is in determining which metrics matter, and what they mean.[3][4] The practical utility of software measurements has thus been limited to narrow domains where they include:

Common goal of measurement may target one or more of the above aspects, or the balance between them as indicator of team’s motivation or project performance.

Acceptance and public opinion

Some software development practitioners point out that simplistic measurements can cause more harm than good.[5] Others have noted that metrics have become an integral part of the software development process.[3] Impact of measurement on programmers psychology have raised concerns for harmful effects to performance due to stress, performance anxiety, and attempts to cheat the metrics, while others find it to have positive impact on developers value towards their own work, and prevent them being undervalued.[6] Some argue that the definition of many measurement methodologies are imprecise, and consequently it is often unclear how tools for computing them arrive at a particular result,[7] while others argue that imperfect quantification is better than none (“You can’t control what you can't measure.”).[8] Evidence shows that software metrics are being widely used by government agencies, the US military, NASA,[9] IT consultants, academic institutions,[10] and commercial and academic development estimation software.

See also

References

  1. ↑ "Descriptive Information (DI) Metric Thresholds". Land Software Engineering Centre. Retrieved 19 October 2010. 
  2. ↑ "OMG Adopts Automated Function Point Specification". Omg.org. 2013-01-17. Retrieved 2013-05-19. 
  3. ↑ 3.0 3.1 Binstock, Andrew. "Integration Watch: Using metrics effectively". SD Times. BZ Media. Retrieved 19 October 2010. 
  4. ↑ Kolawa, Adam. "When, Why, and How: Code Analysis". The Code Project. Retrieved 19 October 2010. 
  5. ↑ Kaner, Dr. Cem, Software Engineer Metrics: What do they measure and how do we know?, CiteSeerX: 10.1.1.1.2542 
  6. ↑ "ProjectCodeMeter (2010) "ProjectCodeMeter Users Manual" page 65" (PDF). Retrieved 2013-05-19. 
  7. ↑ Lincke, Rüdiger; Lundberg, Jonas; Löwe, Welf (2008), "Comparing software metrics tools", International Symposium on Software Testing and Analysis 2008: 131–142 
  8. ↑ DeMarco, Tom. Controlling Software Projects: Management, Measurement and Estimation. ISBN 0-13-171711-1. 
  9. ↑ "NASA Metrics Planning and Reporting Working Group (MPARWG)". Earthdata.nasa.gov. Retrieved 2013-05-19. 
  10. ↑ "USC Center for Systems and Software Engineering". Sunset.usc.edu. Retrieved 2013-05-19. 

External links

Covers a minimal set of essential metrics for a successful product delivery.

This article is issued from Wikipedia. The text is available under the Creative Commons Attribution/Share Alike; additional terms may apply for the media files.