Papers
Topics
Authors
Recent
Gemini 2.5 Flash
Gemini 2.5 Flash
119 tokens/sec
GPT-4o
56 tokens/sec
Gemini 2.5 Pro Pro
43 tokens/sec
o3 Pro
6 tokens/sec
GPT-4.1 Pro
47 tokens/sec
DeepSeek R1 via Azure Pro
28 tokens/sec
2000 character limit reached

Quality Requirements for Code: On the Untapped Potential in Maintainability Specifications (2401.10833v1)

Published 19 Jan 2024 in cs.SE

Abstract: Quality requirements are critical for successful software engineering, with maintainability being a key internal quality. Despite significant attention in software metrics research, maintainability has attracted surprisingly little focus in the Requirements Engineering (RE) community. This position paper proposes a synergistic approach, combining code-oriented research with RE expertise, to create meaningful industrial impact. We introduce six illustrative use cases and propose three future research directions. Preliminary findings indicate that the established QUPER model, designed for setting quality targets, does not adequately address the unique aspects of maintainability.

Definition Search Book Streamline Icon: https://streamlinehq.com
References (24)
  1. Amine Abbad-Andaloussi. 2023. On the Relationship Between Source-Code Metrics and Cognitive Load: A Systematic Tertiary Review. Journal of Systems and Software 198 (2023), 111619. https://doi.org/10.1016/j.jss.2023.111619
  2. Software Development and Innovation: Exploring the Software Shift in Innovation in Swedish Firms. Technological Forecasting and Social Change 167 (2021), 120695. https://doi.org/10.1016/j.techfore.2021.120695
  3. A Tool-Based Perspective on Software Code Maintainability Metrics: A Systematic Literature Review. Scientific Programming 2020 (2020), e8840389. https://doi.org/10.1155/2020/8840389
  4. Quality Requirements in Industrial Practice - An Extended Interview Study at Eleven Companies. IEEE Transactions on Software Engineering 38, 4 (2011), 923–935.
  5. An Investigation of How Quality Requirements Are Specified in Industrial Practice. Information and Software Technology 55, 7 (2013), 1224–1236. https://doi.org/10.1016/j.infsof.2013.01.006
  6. Markus Borg. 2023. Requirements on Technical Debt: Dare to Specify Them! IEEE Software 40, 2 (March 2023), 8–12. https://doi.org/10.1109/MS.2022.3226791
  7. Digitalization of Swedish Government Agencies - A Perspective Through the Lens of a Software Development Census. In Proc. of the 40th International Conference on Software Engineering: Software Engineering in Society. 37–46.
  8. Increasing, Not Diminishing: Investigating the Returns of Highly Maintainable Code. In Proc. of the 7rd International Conference on Technical Debt.
  9. J. Dresner and K. H. Borchers. 1964. Maintenance, Maintainability, and System Requirements Engineering. SAE Technical Paper 640591. SAE International, Warrendale, PA. https://www.sae.org/publications/technical-papers/content/640591/
  10. International Organization for Standardization. 2021. Information Technology - Software Measurement - Software Quality Measurement - Automated Source Code Quality Measures. Technical Report ISO/IEC 5055:2021.
  11. Sources of Company Funding. In Intellectual Property and Financing Strategies for Technology Startups, Jr. Halt, Gerald B., Jr. Donch, John C., Amber R. Stiles, and Robert Fesnak (Eds.). Springer International Publishing, Cham, 11–33. https://doi.org/10.1007/978-3-319-49217-9_2
  12. Andrew Hunt and David Thomas. 1999. The Pragmatic Programmer: From Journeyman to Master (1 ed.). Addison-Wesley Professional, Boston, MA, USA.
  13. Software Engineering in Start-up Companies: An Analysis of 88 Experience Reports. Empirical Software Engineering 24, 1 (2019), 68–102. https://doi.org/10.1007/s10664-018-9620-y
  14. Juha-Matti Lehtonen and Kai Virtanen. 2022. Choosing the Most Economically Advantageous Tender Using a Multi-Criteria Decision Analysis Approach. Journal of Public Procurement 22, 2 (2022), 164–179. https://doi.org/10.1108/JOPP-06-2021-0040
  15. Jean-Louis Letouzey. 2012. The SQALE Method for Evaluating Technical Debt. In Proc. of the 3rd International Workshop on Managing Technical Debt. 31–36. https://doi.org/10.1109/MTD.2012.6225997
  16. How to Characterize the Health of an Open Source Software Project? A Snowball Literature Review of an Emerging Practice. In Proc. of the 18th International Symposium on Open Collaboration (OpenSym ’22). 1–12. https://doi.org/10.1145/3555051.3555067
  17. Thomas McCabe. 1976. A Complexity Measure. IEEE Transactions on Software Engineering SE-2, 4 (1976), 308–320. https://doi.org/10.1109/TSE.1976.233837
  18. Source Code Metrics: A Systematic Mapping Study. Journal of Systems and Software 128 (2017), 164–197. https://doi.org/10.1016/j.jss.2017.03.044
  19. A Systematic Literature Review of Empirical Research on Quality Requirements. Requirements Engineering 27, 2 (2022), 249–271. https://doi.org/10.1007/s00766-022-00373-9
  20. Paul Oman and Jack Hagemeister. 1994. Construction and Testing of Polynomials Predicting Software Maintainability. Journal of Systems and Software 24, 3 (1994), 251–266. https://doi.org/10.1016/0164-1212(94)90067-1
  21. Mike Rawlinson and Peter Wells. 1996. Taylorism, Lean Production and the Automotive Industry. Asia Pacific Business Review 2, 4 (1996), 189–204. https://doi.org/10.1080/13602389600000026
  22. Supporting Roadmapping of Quality Requirements. IEEE Software 25, 2 (2008), 42–47. https://doi.org/10.1109/MS.2008.48
  23. Adam Tornhill and Markus Borg. 2022. Code Red: The Business Impact of Code Quality - A Quantitative Study of 39 Proprietary Production Codebases. In Proc. of the 5th International Conference on Technical Debt. 11–20.
  24. Specification of Service Level Agreements: Problems, Principles and Practices. Software Quality Journal 12, 1 (2004), 43–57. https://doi.org/10.1023/B:SQJO.0000013358.61395.96
User Edit Pencil Streamline Icon: https://streamlinehq.com
Authors (1)
  1. Markus Borg (60 papers)
Citations (1)

Summary

We haven't generated a summary for this paper yet.