Co-existence of the \u27technical debt\u27 and \u27software legacy\u27 concepts

\u27Technical debt\u27 and \u27software legacy\u27 are concepts that both discuss a state of software that is sub-optimal, time constrained, and explain how this state can decrease an organization\u27s development efficiency. However, there is significant confusion in the way the software engineering community perceive these concepts. In this paper we perform an initial examination of technical debt and software legacy concepts, and examine their somewhat challenging co-existence. In motivating our work, we discuss previous survey results which show that practitioners believe that technical debt largely emerges from software legacy. We then identify sources of confusion in comparing popular definitions of both concepts. Finally, we map the use of the \u27technical debt\u27 and \u27software legacy\u27 concepts in existing research. We conclude that structured co-existence of these terms can be pursued with mutually beneficial gains