O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Domain-level Technical Debt

168 visualizações

Publicada em

Evaluation and Assessment in Software Engineering (EASE) 2019, Copenhagen: Talk by Harald Störrle (@stoerrle, Principal IT Consultant at QAware) & Marcus Ciolkowski (@M_Ciolkowski, Pricipal IT Consultant at QAware)

=== Please download slides if blurred! ===

Abstract:
Technical debt is a metaphor for trading software quality for business goals, reminding actors of the deferred cost associated with such trade-offs. The bulk of the research covers source code only, but we often abserve that a different kind of debt is more important in eceonomic terms. In order to set it apart from technical debt and since this is about domain level design decisions, we call it domain debt.

Taking advantage of the new "experience report" format, we would like to present a numer of cases from those many instances that we have observed. We hope that the shepherding process will support us in selecting the most representative exampels, and present them in a way so they will be accessible to a broad audience.

Publicada em: Software
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

×