Wikipedia

Software metric

Insoftware engineeringanddevelopment,asoftware metricis a standard of measure of a degree to which asoftware systemor process possesses some property.[1][2]Even if a metric is not a measurement (metrics are functions, while measurements are the numbers obtained by the application of metrics), often the two terms are used as synonyms. Sincequantitative measurementsare essential in all sciences, there is a continuous effort bycomputer sciencepractitioners 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, softwaredebugging,softwareperformance optimization,and optimal personnel task assignments.

Common software measurements

edit

Common software measurements include:

Limitations

edit

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.[8][9] The practical utility of software measurements has therefore been limited to the following domains:

A specific measurement may target one or more of the above aspects, or the balance between them, for example as an indicator of team motivation or project performance. [10] Additionally metrics vary between static and dynamic program code, as well as for object oriented software (systems).[11][12]

Acceptance and public opinion

edit

Some software development practitioners point out that simplistic measurements can cause more harm than good.[13]Others have noted that metrics have become an integral part of the software development process.[8] Impact of measurement on programmer 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. 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,[14]while others argue that imperfect quantification is better than none ( “You can’t control what you can't measure.” ).[15]Evidence shows that software metrics are being widely used by government agencies, the US military, NASA,[16]IT consultants, academic institutions,[17]and commercial and academicdevelopment estimation software.

Further reading

edit
  • J. Smith,Introduction to Linear Programming,Acme Press, 2010. An introductory text.
  • Reijo M.Savola,Quality of security metrics and measurements, Computers & Security, Volume 37, September 2013, Pages 78-90.[18]

See also

edit

References

edit
  1. ^Fenton, Norman E. (2014).Software metrics: a rigorous and practical approach.James Bieman (3rd ed.). Boca Raton, FL.ISBN978-1-4398-3823-5.OCLC834978252.{{cite book}}:CS1 maint: location missing publisher (link)
  2. ^Timóteo, Aline Lopes; Álvaro, Re; Almeida, Eduardo Santana De; De, Silvio Romero; Meira, Lemos.Software Metrics: A Survey.CiteSeerX10.1.1.544.2164.
  3. ^"Descriptive Information (DI) Metric Thresholds".Land Software Engineering Centre.Archived fromthe originalon 6 July 2011.Retrieved19 October2010.
  4. ^Gill, G. K.; Kemerer, C. F. (December 1991)."Cyclomatic complexity density and software maintenance productivity".IEEE Transactions on Software Engineering.17(12): 1284–1288.doi:10.1109/32.106988.ISSN1939-3520.
  5. ^"maintainability - Does it make sense to compute cyclomatic complexity/lines of code ratio?".Software Engineering Stack Exchange.Retrieved2021-03-01.
  6. ^"OMG Adopts Automated Function Point Specification".Omg.org. 2013-01-17.Retrieved2013-05-19.
  7. ^Amit, Idan; Feitelson, Dror G. (2020-07-21). "The Corrective Commit Probability Code Quality Metric".arXiv:2007.10912[cs.SE].
  8. ^abBinstock, Andrew (March 2010)."Integration Watch: Using metrics effectively".SD Times.BZ Media.Retrieved19 October2010.
  9. ^Kolawa, Adam (7 August 2008)."When, Why, and How: Code Analysis".The Code Project.Retrieved14 February2021.
  10. ^Mike, John."Essential Metrics for Effective Incident Response Strategies".Retrieved18 July2021.
  11. ^Gosain, Anjana; Sharma, Ganga (2015)."Dynamic Software Metrics for Object Oriented Software: A Review".In Mandal, J. K.; Satapathy, Suresh Chandra; Kumar Sanyal, Manas; Sarkar, Partha Pratim; Mukhopadhyay, Anirban (eds.).Information Systems Design and Intelligent Applications.Advances in Intelligent Systems and Computing. Vol. 340. New Delhi: Springer India. pp. 579–589.doi:10.1007/978-81-322-2247-7_59.ISBN978-81-322-2247-7.
  12. ^S, Parvinder Singh; Singh, Gurdev.Dynamic Metrics for Polymorphism in Object Oriented Systems.CiteSeerX10.1.1.193.4307.
  13. ^Kaner, Dr. Cem (2004),Software Engineer Metrics: What do they measure and how do we know?,CiteSeerX10.1.1.1.2542
  14. ^Lincke, Rüdiger; Lundberg, Jonas; Löwe, Welf (2008),"Comparing software metrics tools"(PDF),International Symposium on Software Testing and Analysis 2008,pp. 131–142
  15. ^DeMarco, Tom(1982).Controlling Software Projects: Management, Measurement and Estimation.Yourdon Press.ISBN0-13-171711-1.
  16. ^"NASA Metrics Planning and Reporting Working Group (MPARWG)".Earthdata.nasa.gov. Archived fromthe originalon 2011-10-22.Retrieved2013-05-19.
  17. ^"USC Center for Systems and Software Engineering".Sunset.usc.edu.Retrieved2013-05-19.
  18. ^Savola, Reijo M. (2013-09-01)."Quality of security metrics and measurements".Computers & Security.37:78–90.doi:10.1016/j.cose.2013.05.002.ISSN0167-4048.
edit
Retrieved from "https://en.wikipedia.org/w/index.php?title=Software_metric&oldid=1233858150"