Bridging the software quality gap
There is a gap in the understanding of software quality between developers and non-technical stakeholders, the software quality gap, which leads to disagreements about the amount of time that should be used for quality improvements. The technical debt metaphor reduces this gap some by describing sof...
Main Author: | |
---|---|
Format: | Others |
Language: | English |
Published: |
Umeå universitet, Institutionen för datavetenskap
2012
|
Subjects: | |
Online Access: | http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-61507 |
id |
ndltd-UPSALLA1-oai-DiVA.org-umu-61507 |
---|---|
record_format |
oai_dc |
spelling |
ndltd-UPSALLA1-oai-DiVA.org-umu-615072013-01-08T13:45:26ZBridging the software quality gapengLindgren, MarkusUmeå universitet, Institutionen för datavetenskap2012Computer scienceDatavetenskapThere is a gap in the understanding of software quality between developers and non-technical stakeholders, the software quality gap, which leads to disagreements about the amount of time that should be used for quality improvements. The technical debt metaphor reduces this gap some by describing software quality in economic terms, enabling developers and non-technical stakeholders to communicate about the quality. However, the metaphor is vague and not very concrete in explaining the gap. The purpose of this thesis is to concretize the technical debt metaphor using Domain-Driven Design, an approach in which communicating software characteristics is central, in order to reduce the software quality gap further. Using the terminology of Domain-Driven Design, a new concept is defined: model debt, which measures and communicates the software quality of the domain model. An application is built, the ModelDebtOMeter, which extracts the domain model of a software system and visualizes it along with its corresponding model debt. The model debt of a legacy system is amortized and the results of the amortizations are presented to the non-technical stakeholders of the system using the ModelDebtOMeter, allowing the non-technical stakeholders to evaluate the model debt concept. The results show that the non-technical stakeholders think that model debt is an understandable concept which reduces, but not eliminates, the software quality gap. Student thesisinfo:eu-repo/semantics/bachelorThesistexthttp://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-61507UMNAD ; 928application/pdfinfo:eu-repo/semantics/openAccess |
collection |
NDLTD |
language |
English |
format |
Others
|
sources |
NDLTD |
topic |
Computer science Datavetenskap |
spellingShingle |
Computer science Datavetenskap Lindgren, Markus Bridging the software quality gap |
description |
There is a gap in the understanding of software quality between developers and non-technical stakeholders, the software quality gap, which leads to disagreements about the amount of time that should be used for quality improvements. The technical debt metaphor reduces this gap some by describing software quality in economic terms, enabling developers and non-technical stakeholders to communicate about the quality. However, the metaphor is vague and not very concrete in explaining the gap. The purpose of this thesis is to concretize the technical debt metaphor using Domain-Driven Design, an approach in which communicating software characteristics is central, in order to reduce the software quality gap further. Using the terminology of Domain-Driven Design, a new concept is defined: model debt, which measures and communicates the software quality of the domain model. An application is built, the ModelDebtOMeter, which extracts the domain model of a software system and visualizes it along with its corresponding model debt. The model debt of a legacy system is amortized and the results of the amortizations are presented to the non-technical stakeholders of the system using the ModelDebtOMeter, allowing the non-technical stakeholders to evaluate the model debt concept. The results show that the non-technical stakeholders think that model debt is an understandable concept which reduces, but not eliminates, the software quality gap. |
author |
Lindgren, Markus |
author_facet |
Lindgren, Markus |
author_sort |
Lindgren, Markus |
title |
Bridging the software quality gap |
title_short |
Bridging the software quality gap |
title_full |
Bridging the software quality gap |
title_fullStr |
Bridging the software quality gap |
title_full_unstemmed |
Bridging the software quality gap |
title_sort |
bridging the software quality gap |
publisher |
Umeå universitet, Institutionen för datavetenskap |
publishDate |
2012 |
url |
http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-61507 |
work_keys_str_mv |
AT lindgrenmarkus bridgingthesoftwarequalitygap |
_version_ |
1716528402817613824 |