• Corpus ID: 3126272

136 16162 – Managing Technical Debt in Software Engineering 5 . 7 Social Debt in Software Engineering : Towards a Crisper Definition

@inproceedings{Tamburri20161361,
  title={136 16162 – Managing Technical Debt in Software Engineering 5 . 7 Social Debt in Software Engineering : Towards a Crisper Definition},
  author={Damian Andrew Tamburri and Steve Fraser},
  year={2016}
}
This report documents the program and outcomes of Dagstuhl Seminar 16162, “Managing Technical Debt in Software Engineering.” We summarize the goals and format of the seminar, results from the breakout groups, a definition for technical debt, a draft conceptual model, and a research road map that culminated from the discussions during the seminar. The report also includes the abstracts of the talks presented at the seminar and summaries of open discussions.s of the talks presented at the seminar… 

Figures from this paper

References

SHOWING 1-6 OF 6 REFERENCES
Managing Technical Debt in Software Engineering (Dagstuhl Seminar 16162)
This report documents the program and outcomes of Dagstuhl Seminar 16162, “Managing Technical Debt in Software Engineering.” We summarize the goals and format of the seminar, results from the
Social debt in software engineering: insights from industry
TLDR
The objective was to study the causality around social debt in practice in a large software company, and found many forces together causing social debt, represented them in a framework, and captured anti-patterns that led to the debt in the first place.
Preemptive management of model driven technical debt for improving software quality
TLDR
Several questions that need to be addressed in order to improve the quality of software architecture by exploring the management of technical debt during modeling are discussed, and various lines of research that are worthwhile subjects for further investigation are suggested.
Tool supported detection and judgment of nonconformance in process execution
TLDR
This paper developed a tool-supported approach that uses process nonconformance detection to identify potential risks in achieving the required process characteristics and demonstrates its use on a large-scale software development project in the aerospace domain.
Building empirical support for automated code smell detection
TLDR
The study investigates the way professional software developers detect god class code smells, then compares these results to automatic classification, and leads to the conclusion that an automated metric-based pre-selection decreases the effort spent on manual code inspections.
JDeodorant: Identification and Removal of Type-Checking Bad Smells
TLDR
An Eclipse plug-in is presented that automatically identifies type-checking bad smells in Java source code, and resolves them by applying the "replace conditional with polymorphism" or "replace type code with state/strategy " refactorings.