Paper
Making Software Metrics Useful
Authors
Ewan Tempero, Paul Ralph
Abstract
Most engineers use measurements to make decisions. However, measurements are rarely used for decisions about constructing software products. While many approaches to measuring attributes of software (``metrics'') have been developed, they are rarely used to answer useful questions such as ``Do I need to refactor this class?'' or ``Are these integration tests sufficient?'' Practitioners therefore question the value of software metrics. We argue that this situation arose because software metrics were developed without understanding metrology (the science of measurement) and suggest directions software metrics research should take.
Metadata
Related papers
Fractal universe and quantum gravity made simple
Fabio Briscese, Gianluca Calcagni • 2026-03-25
POLY-SIM: Polyglot Speaker Identification with Missing Modality Grand Challenge 2026 Evaluation Plan
Marta Moscati, Muhammad Saad Saeed, Marina Zanoni, Mubashir Noman, Rohan Kuma... • 2026-03-25
LensWalk: Agentic Video Understanding by Planning How You See in Videos
Keliang Li, Yansong Li, Hongze Shen, Mengdi Liu, Hong Chang, Shiguang Shan • 2026-03-25
Orientation Reconstruction of Proteins using Coulomb Explosions
Tomas André, Alfredo Bellisario, Nicusor Timneanu, Carl Caleman • 2026-03-25
The role of spatial context and multitask learning in the detection of organic and conventional farming systems based on Sentinel-2 time series
Jan Hemmerling, Marcel Schwieder, Philippe Rufin, Leon-Friedrich Thomas, Mire... • 2026-03-25
Raw Data (Debug)
{
"raw_xml": "<entry>\n <id>http://arxiv.org/abs/2603.16012v1</id>\n <title>Making Software Metrics Useful</title>\n <updated>2026-03-16T23:42:44Z</updated>\n <link href='https://arxiv.org/abs/2603.16012v1' rel='alternate' type='text/html'/>\n <link href='https://arxiv.org/pdf/2603.16012v1' rel='related' title='pdf' type='application/pdf'/>\n <summary>Most engineers use measurements to make decisions. However, measurements are rarely used for decisions about constructing software products. While many approaches to measuring attributes of software (``metrics'') have been developed, they are rarely used to answer useful questions such as ``Do I need to refactor this class?'' or ``Are these integration tests sufficient?'' Practitioners therefore question the value of software metrics. We argue that this situation arose because software metrics were developed without understanding metrology (the science of measurement) and suggest directions software metrics research should take.</summary>\n <category scheme='http://arxiv.org/schemas/atom' term='cs.SE'/>\n <published>2026-03-16T23:42:44Z</published>\n <arxiv:comment>IEEE Computer. In Press</arxiv:comment>\n <arxiv:primary_category term='cs.SE'/>\n <author>\n <name>Ewan Tempero</name>\n </author>\n <author>\n <name>Paul Ralph</name>\n </author>\n <arxiv:doi>10.1109/MC.2026.3666634</arxiv:doi>\n <link href='https://doi.org/10.1109/MC.2026.3666634' rel='related' title='doi'/>\n </entry>"
}