An enterprise perspective on technical debt

Klinger, Tim; Tarr, Peri; Wagstrom, Patrick; Williams, Clay

doi:10.1145/1985362.1985371

Cited by 68 publications

(51 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Allman argues that understanding, communicating, and managing technical debt is essential for the long-term success of a system. Whereas technical debt was initially conceptualized as producing immature code in order to deliver solutions to market needs [Cunningham 1992], a broader view includes the notion of tradeoffs between short-term decisions made during development and their potentially long-term costs [Klinger et al 2011]. Thus, whereas both conventional and agile development approaches may accumulate technical debt, the issue is more pronounced and observed relatively more quickly in agile development due to its focus on time-to-market considerations.…”

Section: Adapted Boundary Spanningmentioning

confidence: 99%

Situated Boundary Spanning

Jain

Cao

Mohan

et al. 2014

ACM Trans. Manage. Inf. Syst.

View full text Add to dashboard Cite

Requirements Engineering (RE) faces considerable challenges that are often related to boundaries between various stakeholders involved in the software development process. These challenges may be addressed by boundary spanning practices. We examine how boundary spanning can be adapted to address RE challenges in Product Family Development (PFD), a context that involves complex RE. We study two different development approaches, namely, conventional and agile PFD, because these present considerably different challenges. Our findings from a multisite case study present boundary spanning as a solution to improve the quality of RE processes and highlight interesting differences in how boundary spanner roles and boundary objects are adapted in conventional and agile PFD.

show abstract

Section: Adapted Boundary Spanningmentioning

confidence: 99%

Situated Boundary Spanning

Jain

Cao

Mohan

et al. 2014

ACM Trans. Manage. Inf. Syst.

View full text Add to dashboard Cite

show abstract

“…It is vital that people and organizations recognize and learn from near-miss events. Another example is captured in the phrase 'technical debt' (Brown et al 2010, Guo et al 2011, Klinger et al 2011, which refers to short cuts and other expedient actions taken by IT system designers prior to a release. These may not 'cost' them anything in the very short-run, but sooner or later the 'debt' must be paid off eventually, either through patching or through the cost of security breaches.…”

Section: Why Breach Impact Estimation Is Hardmentioning

confidence: 99%

How Bad is it? – A Branching Activity Model to Estimate the Impact of Information Security Breaches

Thomas¹,

Antkiewicz²,

Florer³

et al. 2013

SSRN Journal

View full text Add to dashboard Cite

“…Large software systems often suffer from an inability to evolve to meet new demands [1], largely due to increasing amounts of technical debt [2], and the inability of code maintainers to automatically update large portions code in a semantically safe way. Even automatic changes which may appear safe in isolation may introduce semantic conflicts that cause faults which are difficult to detect [3].…”

Section: Introductionmentioning

confidence: 99%

Large-Scale Automated Refactoring Using ClangMR

Wright

Jasper

Klimek

et al. 2013

2013 IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

Maintaining large codebases can be a challenging endeavour. As new libraries, APIs and standards are introduced, old code is migrated to use them. To provide as clean and succinct an interface as possible for developers, old APIs are ideally removed as new ones are introduced. In practice, this becomes difficult as automatically finding and transforming code in a semantically correct way can be challenging, particularly as the size of a codebase increases.In this paper, we present a real-world implementation of a system to refactor large C++ codebases efficiently. A combination of the Clang compiler framework and the MapReduce parallel processor, ClangMR enables code maintainers to easily and correctly transform large collections of code. We describe the motivation behind such a tool, its implementation and then present our experiences using it in a recent API update with Google's C++ codebase.

show abstract

An enterprise perspective on technical debt

Cited by 68 publications

References 4 publications

Situated Boundary Spanning

Situated Boundary Spanning

How Bad is it? – A Branching Activity Model to Estimate the Impact of Information Security Breaches

Large-Scale Automated Refactoring Using ClangMR

Contact Info

Product

Resources

About