How Technology Fails Developers: A Qualitative Investigation of Tool, Architecture, and Legacy System Deficiencies in Software Error Introduction

Authors

  • Rahul Azmeera University of the Cumberlands
  • Dr. James C Hyatt University of the Cumberlands

DOI:

https://doi.org/10.47941/jts.3921

Keywords:

Software Errors, Development Tools, System Architecture, Legacy Systems, AI Code Generation

Abstract

Purpose: This study investigated the technological deficiencies contributing to software errors in software products, examining how inadequacies in development tools, developer expertise gaps, architectural failures, modern technology adoption challenges, and legacy system constraints create conditions for software errors.

Methodology: A qualitative phenomenological design was employed. Semi-structured interviews were conducted with 12 experienced software developers averaging 14.5 years of experience in U.S.-based organizations across retail, healthcare, technology, and financial sectors. Data were analyzed using reflexive thematic analysis in NVivo 14, anchored in the Technological Context construct of the Technology-Organization-Environment (TOE) framework.

Findings: Five themes emerged from this study, theme 1. Inadequacies in development tools and practices- discovering the challenges with existing tools and developer practices; theme 2. Impact of developer expertise and practices on software quality- discusses how the individual work experience shows bias in software development; theme 3. System architecture and oversight failures- discusses the software errors caused due to poor architecture and error monitoring; theme 4. The role of modern technologies and automation- discusses the impact of AI coding assistants; theme 5. Challenges posed by legacy systems and external integrations- elaborates how legacy systems limit developers’ productivity and software innovation. These themes collectively constitute the Technological Error Origin Framework (TEOF).

Unique contribution to theory, practice and policy: This study provides the first developer-experience-grounded, phenomenologically anchored account of software error origins within the TOE framework. Organizations should invest in integrated error-detection toolchains, implement developer upskilling programs spanning both technical and domain knowledge, enforce architecture-first principles with mandatory monitoring, and establish structured legacy modernization roadmaps.

Downloads

Download data is not yet available.

Author Biographies

Rahul Azmeera, University of the Cumberlands

PhD, Independent Researcher

Dr. James C Hyatt, University of the Cumberlands

Adjunct Professor

References

Akbar, M. A., Smidt, H., Shafiq, M., Alwageed, H., Pitafi, A. H., & Humayun, M. (2022). An empirical investigation of software technical debt. Journal of Software: Evolution and Process, 34(6), e2454. https://doi.org/10.1002/smr.2454

Alexandrova, T., & Rapanotti, L. (2019). Legacy system replacement: Understanding the risks. Information Systems Management, 36(1), 54–67. https://doi.org/10.1080/10580530.2018.1537496

Baker, J. (2011). The technology-organization-environment framework. In Y. Dwivedi, M. Wade, & S. Schneberger (Eds.), Information systems theory (Vol. 28, pp. 231–245). Springer. https://doi.org/10.1007/978-1-4419-6108-2_12

Bluemke, I., & Malanowska, A. (2021). On the difficulty of test case selection. Symmetry, 13(11), 2193. https://doi.org/10.3390/sym13112193

Braun, V., & Clarke, V. (2022). Thematic analysis: A practical guide. SAGE Publications.

Byrne, D. (2022). A worked example of Braun and Clarke's approach to reflexive thematic analysis. Quality & Quantity, 56, 1391–1412. https://doi.org/10.1007/s11135-021-01182-y

Castro, L., Galster, M., & Goedicke, M. (2023). Technical debt in software architecture: A systematic mapping study. Journal of Systems and Software, 197, 111601. https://doi.org/10.1016/j.jss.2023.111601

Creswell, J. W., & Creswell, J. D. (2018). Research design: Qualitative, quantitative, and mixed methods approaches (5th ed.). SAGE Publications.

Frechette, J., Bitzas, V., Aubry, M., Kilpatrick, K., & Lavoie-Tremblay, M. (2020). Capturing lived experience: Methodological considerations for interpretive phenomenological inquiry. International Journal of Qualitative Methods, 19. https://doi.org/10.1177/1609406920907254

Govindaras, B., Hussain, A., Tengku Wook, T. S. M., & Ahmad, W. F. W. (2023). Challenges in software testing for complex integrated systems. IEEE Access, 11, 45621–45639. https://doi.org/10.1109/ACCESS.2023.3274189

Hennink, M., & Kaiser, B. N. (2022). Sample sizes for saturation in qualitative research: A systematic review of empirical tests. Social Science & Medicine, 292, 114523. https://doi.org/10.1016/j.socscimed.2021.114523

Horani, O., Suleiman, H., & Tal, I. (2023). A systematic review of TOE framework for enterprise digital adoption. IEEE Access, 11, 31922–31949. https://doi.org/10.1109/ACCESS.2023.3261867

Jayakody, J. A. S. K., & Wijayanayake, W. M. J. I. (2021). Developer-perceived challenges in adopting DevOps toolchains: A qualitative study. Journal of Systems and Software, 178, 110982. https://doi.org/10.1016/j.jss.2021.110982

Karcher, S., Kirilova, D., Andreata, A., & Sherif, N. (2024). Reflexivity in qualitative research. International Journal of Qualitative Methods, 23. https://doi.org/10.1177/16094069241238049

Khaliq, A., Shahzad, B., & Saleem, M. A. (2023). Limitations of AI-based test case generation in enterprise software. IEEE Transactions on Software Engineering, 49(4), 2241–2258. https://doi.org/10.1109/TSE.2022.3225442

Khan, M. S., Fernandez-Crehuet, J. M., & Dabbagh, M. (2022). Perceived ease of use and developer tool adoption: An empirical study. Journal of Software: Evolution and Process, 34(9), e2465. https://doi.org/10.1002/smr.2465

Krasner, H. (2021). The cost of poor software quality in the US: A 2020 report. Consortium for Information & Software Quality (CISQ). https://www.it-cisq.org/the-cost-of-poor-quality-software-in-the-us-a-2020-report/

Kurian, J., & Thomas, A. (2023). Testing challenges in microservices-based software architectures. ACM Computing Surveys, 55(14), 1–36. https://doi.org/10.1145/3568024

Li, F., Liang, P., & Avgeriou, P. (2022). A systematic mapping study on technical debt and its management. Journal of Systems and Software, 193, 111477. https://doi.org/10.1016/j.jss.2022.111477

Lincoln, Y. S., & Guba, E. G. (1985). Naturalistic inquiry. SAGE Publications.

Lopez, M., Medina, L., & Morales-Salazar, E. (2021). Developer challenges in tool and framework adoption: An empirical study. IEEE Access, 9, 82167–82184. https://doi.org/10.1109/ACCESS.2021.3086549

Negri-Ribalta, C., Noei, E., & Adams, B. (2024). Security risks in AI-generated code: An empirical study. In Proceedings of the 46th International Conference on Software Engineering (ICSE), pp. 1–12. https://doi.org/10.1145/3597503.3639177

Neubauer, B. E., Witkop, C. T., & Varpio, L. (2019). How phenomenology can help us learn from the experiences of others. Perspectives on Medical Education, 8, 90–97. https://doi.org/10.1007/s40037-019-0509-2

Nugraha, F., & Talita, A. S. (2021). Scalability challenges in modern distributed software systems. Journal of Physics: Conference Series, 1803, 012003. https://doi.org/10.1088/1742-6596/1803/1/012003

Panthi, V., Mohapatra, D. P., & Mall, R. (2022). Software testing: A survey of testing practices and challenges. International Journal of Software Engineering and Knowledge Engineering, 32(3), 391–428. https://doi.org/10.1142/S0218194022500127

Pashchenko, I., Vu, D. L., & Massacci, F. (2020). A qualitative study of dependency management and its security implications. In Proceedings of the 2020 ACM SIGSAC Conference on Computer and Communications Security (pp. 1117–1130). https://doi.org/10.1145/3372297.3417232

Soui, M., & Haddad, R. (2023). Automated GUI test case generation: Challenges and opportunities. ACM Computing Surveys, 55(12), 1–42. https://doi.org/10.1145/3565472

Taylor, R. N. (2019). Software architecture: Foundations, theory, and practice. Wiley.

Tian, Y., Zhang, F., & Hassan, A. E. (2022). Software architecture smells: A systematic mapping study. Journal of Systems and Software, 193, 111481. https://doi.org/10.1016/j.jss.2022.111481

Xu, F. F., Alon, U., Neubig, G., & Hellendoorn, J. (2022). A systematic evaluation of large language models of code. In Proceedings of the 6th ACM SIGPLAN International Symposium on Machine Programming (pp. 1–10). https://doi.org/10.1145/3520312.3534862

Zardari, S., Bhutto, A., & Rehman, M. (2022). Test case selection and prioritization: A systematic review. IEEE Access, 10, 32987–33004. https://doi.org/10.1109/ACCESS.2022.3161234.

Downloads

Published

2026-08-09

How to Cite

Azmeera, R., & Hyatt, J. (2026). How Technology Fails Developers: A Qualitative Investigation of Tool, Architecture, and Legacy System Deficiencies in Software Error Introduction. Journal of Technology and Systems, 8(3), 19–36. https://doi.org/10.47941/jts.3921

Issue

Section

Articles