‘Technical debt’ and ‘software legacy’ are concepts that both discuss a state of software that is sub-optimal, time constrained, and explain how this state can decrease an organization’s 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 ‘tec...
Sustainable and scalable software systems require careful consideration over the force known as tech...
Delivering increasingly complex software-reliant systems demands better ways to manage the long-term...
In this chapter, we discuss recent progress and opportunities in empirical software engineering by f...
\u27Technical debt\u27 and \u27software legacy\u27 are concepts that both discuss a state of softwar...
Different methods for technical debt accumulation have been discussed, but they have mainly focused ...
Springer Science+Business Media New York 2013 Abstract Software systems accumulate technical debt (T...
Background: Technical debt is currently receiving increasing attention from practitioners and resear...
— Software companies need to support continuous and fast delivery of customer value both in short an...
AbstractTechnical debt (TD) is a metaphor for taking shortcuts or workarounds in technical decisions...
Technical debt is a metaphor for the consequences that software projects face when they make trade-o...
Context: The concept of technical debt (TD) contextualizes problems faced during software evolution ...
Organisations that manage legacy systems at scale, such as those found within large government agenc...
Technical debt (TD) is a metaphor for taking shortcuts or workarounds in technical decisions to gain...
Context Technical debt is a software engineering metaphor, referring to the eventual financial conse...
Context: Technical debt (TD) is a metaphor reflecting technical compromises that can yield short-ter...
Sustainable and scalable software systems require careful consideration over the force known as tech...
Delivering increasingly complex software-reliant systems demands better ways to manage the long-term...
In this chapter, we discuss recent progress and opportunities in empirical software engineering by f...
\u27Technical debt\u27 and \u27software legacy\u27 are concepts that both discuss a state of softwar...
Different methods for technical debt accumulation have been discussed, but they have mainly focused ...
Springer Science+Business Media New York 2013 Abstract Software systems accumulate technical debt (T...
Background: Technical debt is currently receiving increasing attention from practitioners and resear...
— Software companies need to support continuous and fast delivery of customer value both in short an...
AbstractTechnical debt (TD) is a metaphor for taking shortcuts or workarounds in technical decisions...
Technical debt is a metaphor for the consequences that software projects face when they make trade-o...
Context: The concept of technical debt (TD) contextualizes problems faced during software evolution ...
Organisations that manage legacy systems at scale, such as those found within large government agenc...
Technical debt (TD) is a metaphor for taking shortcuts or workarounds in technical decisions to gain...
Context Technical debt is a software engineering metaphor, referring to the eventual financial conse...
Context: Technical debt (TD) is a metaphor reflecting technical compromises that can yield short-ter...
Sustainable and scalable software systems require careful consideration over the force known as tech...
Delivering increasingly complex software-reliant systems demands better ways to manage the long-term...
In this chapter, we discuss recent progress and opportunities in empirical software engineering by f...