Abstract
AbstractThe technical debt metaphor is used within software engineering to describe technical concessions that produce a short‐term benefit but result in long‐term consequences. Systems engineering is subject to these concessions, yet there is a limited amount of research associating technical debt with systems engineering. This paper provides the results of an empirical survey investigating the prevalence of technical debt in systems engineering, including the occurrence of technical debt, the use of the metaphor, and the distribution of technical debt within the systems engineering lifecycle. The results of the survey show that while technical debt is common in systems engineering and occurs throughout the lifecycle, the metaphor and terminology of technical debt is not consistently applied. These results emphasize the need to enrich the usage of the technical debt metaphor within systems engineering to enable the management of technical debt and to reduce the risk of technical bankruptcy.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
