Prabhat Ram, Pilar Rodríguez, Markku Oivo, Silverio Martínez-Fernández, Alessandra Bagnato, Michał Choraś, Rafał Kozik, Sanja Aaramaa, and Milla Ahola. 2020. Actionable Software Metrics: An Industrial Perspective. In Proceedings of the Evaluation and Assessment in Software Engineering (EASE ’20). Association for Computing Machinery, New York, NY, USA, 240–249. DOI:https://doi.org/10.1145/3383219.3383244
Actionable software metrics : an industrial perspective
|Author:||Ram, Prabhat1; Rodríguez, Pilar1; Oivo, Markku1;|
1M3S, Faculty of ITEE, University of Oulu, Oulu, Finland
2Dept. ESSI, GESSI Research Group, UPC-BarcelonaTech, Barcelona, Spain
3Softeam, Paris, France
4ITTI Sp. z o.o, Poznań and UTP, Bydgoszcz, Poland
5Nokia, Oulu, Finland
6Bittium, Oulu, Finland
|Online Access:||PDF Full Text (PDF, 1 MB)|
|Persistent link:|| http://urn.fi/urn:nbn:fi-fe2020060841026
Association for Computing Machinery,
|Publish Date:|| 2020-06-08
Background: Practitioners would like to take action based on software metrics, as long as they find them reliable. Existing literature explores how metrics can be made reliable, but remains unclear if there are other conditions necessary for a metric to be actionable.
Context & Method: In the context of a European H2020 Project, we conducted a multiple case study to study metrics’ use in four companies, and identified instances where these metrics influenced actions. We used an online questionnaire to enquire about the project participants’ views on actionable metrics. Next, we invited one participant from each company to elaborate on the identified metrics’ use for taking actions and the questionnaire responses (N=17).
Result: We learned that a metric that is practical, contextual, and exhibits high data quality characteristics is actionable. Even a non-actionable metric can be useful, but an actionable metric mostly requires interpretation. However, the more these metrics are simple and reflect the software development context accurately, the less interpretation required to infer actionable information from the metric. Company size and project characteristics can also influence the type of metric that can be actionable.
Conclusion: This exploration of industry’s views on actionable metrics help characterize actionable metrics in practical terms. This awareness of what characteristics constitute an actionable metric can facilitate their definition and development right from the start of a software metrics program.
|Pages:||240 - 249|
Proceedings of EASE 2020 : Evaluation and Assessment in Software Engineering. April 15–17, 2020, Trondheim, Norway
Evaluation and Assessment in Software Engineering
|Type of Publication:||
A4 Article in conference proceedings
|Field of Science:||
113 Computer and information sciences
This work is a result of the Q-Rapids Project, funded by the European Union’s Horizon 2020 research and innovation program, under grant agreement No. 732253.
|EU Grant Number:||
(732253) Q-RAPIDS - Quality-Aware Rapid Software Development
© 2020 Association for Computing Machinery. This is the author's version of the work. It is posted here for your personal use. Not for redistribution. The definitive Version of Record was published in Proceedings of EASE 2020 : Evaluation and Assessment in Software Engineering. April 15–17, 2020, Trondheim, Norway, https://doi.org/10.1145/3383219.3383244.