Abstract
AbstractIn software engineering, technical debt is often used to measure and describe the cost of accumulated work tasks resulting from design decisions deviating from the intended architecture of systems. This paper investigates how to apply the technical debt metaphor to support the selection of integration strategy for complex subsea systems.The investigation presented in the paper is based on a case study that compares several aspects of technical debt in two alternative integration strategies used in an ongoing subsea development project at Aker Solutions (AKSO). Especially, aspects related to using technical debt to describe consequences of unexpected systems emergence during integration, and performing integration activities earlier in the development lifecycle, or in parallel with other engineering activities, have been investigated. The paper furthermore compare and support the case study results with literature.Results from the case study indicate that there is a higher level of inadvertent technical debt related to integration strategies that conduct Integration and Qualification activities late in the development lifecycle, or incorporate a temporal gap between activities for design, and integration.
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.
