Endre søk
RefereraExporteraLink to record
Permanent link

Direct link
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf
A taxonomy of assets for the development of software-intensive products and services
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.ORCID-id: 0000-0002-1729-5154
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.ORCID-id: 0000-0003-1350-7030
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.ORCID-id: 0000-0002-3646-235x
Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.ORCID-id: 0000-0003-1744-3118
Vise andre og tillknytning
2023 (engelsk)Inngår i: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 202, artikkel-id 111701Artikkel i tidsskrift (Fagfellevurdert) Published
Abstract [en]

Context:Developing software-intensive products or services usually involves a plethora of software artefacts. Assets are artefacts intended to be used more than once and have value for organisations; examples include test cases, code, requirements, and documentation. During the development process, assets might degrade, affecting the effectiveness and efficiency of the development process. Therefore, assets are an investment that requires continuous management.

Identifying assets is the first step for their effective management. However, there is a lack of awareness of what assets and types of assets are common in software-developing organisations. Most types of assets are understudied, and their state of quality and how they degrade over time have not been well-understood.

Methods:We performed an analysis of secondary literature and a field study at five companies to investigate and identify assets to fill the gap in research. The results were analysed qualitatively and summarised in a taxonomy.

Results:We present the first comprehensive, structured, yet extendable taxonomy of assets, containing 57 types of assets.

Conclusions:The taxonomy serves as a foundation for identifying assets that are relevant for an organisation and enables the study of asset management and asset degradation concepts.

sted, utgiver, år, opplag, sider
Elsevier, 2023. Vol. 202, artikkel-id 111701
Emneord [en]
Assets in software engineering, Asset management in software engineering, Assets for software-intensive products or services, Taxonomy
HSV kategori
Identifikatorer
URN: urn:nbn:se:bth-24426DOI: 10.1016/j.jss.2023.111701ISI: 000984121100001Scopus ID: 2-s2.0-85152899759OAI: oai:DiVA.org:bth-24426DiVA, id: diva2:1749684
Ingår i projekt
SHADE- A value-oriented strategy for managing the degradation of software assets, Knowledge FoundationSERT- Software Engineering ReThought, Knowledge Foundation
Forskningsfinansiär
Knowledge Foundation, 20170176Knowledge Foundation, 20180010Tilgjengelig fra: 2023-04-11 Laget: 2023-04-11 Sist oppdatert: 2023-06-02bibliografisk kontrollert
Inngår i avhandling
1. Understanding Asset Degradation in Software Engineering
Åpne denne publikasjonen i ny fane eller vindu >>Understanding Asset Degradation in Software Engineering
2023 (engelsk)Doktoravhandling, med artikler (Annet vitenskapelig)
Abstract [en]

Background: As software is everywhere, and almost every company has nowadays a dependency on software, designing and developing software-intensive products or services has become significantly challenging and time-consuming. The challenges are due to the continuous growth of the size and complexity of software and the fast pace of change. It is important that software-developing organisations’ engineering practices adapt to the rising challenges by adopting well-engineered development activities. Organisations deal with many software artefacts, some of which are more relevant for the organisation. We define Software Assets as artefacts intended to be used more than once. Given softwared evelopment’s continuous and evolutionary aspect, the assets involved degrade over time. Organisations need to understand what assets are relevant and how they degrade to exercise quality control over software assets. Asset degradation is inevitable, and it may manifest in different ways. 

Objective: The main objective of this thesis is: (i) to contribute to the software engineering body of knowledge by providing an understanding of what assets are and how they degrade; and (ii) to gather empirical evidence regarding asset degradation and different factors that might impact it on industrial settings. 

Method: To achieve the thesis goals, several studies have been conducted. The collected data is from peer-reviewed literature and collaboration with five companies that included extracting archival data from over 20 million LOC and archival data from open-source repositories. 

Results: The first contribution of this thesis is defining the concept of assets and asset degradation in a position paper. We aim to provide an understanding of software assets and asset degradation and its impact on software development.  Additionally, a taxonomy of assets is created using academic and industrial input. The taxonomy includes 57 assets and their categories. To further investigate the concept of asset degradation, we have conducted in-depth analyses of multiple industrial case studies on selected assets. This thesis presents results to provide evidence on the impact of different factors on asset degradation, including: (I) how the accumulation of technical debt is affected by different development activities; (ii) how degradation ‘survives’; and (iii) how working from home or the misalignment between ownership and contribution impacts the faster accumulation of asset degradation. Additionally, we created a model to calculate the degree of the alignment between ownership and contribution to code. 

Conclusion: The results can help organisations identify and understand the relevant software assets and characterize their quality degradation. Understanding how assets degrade and which factors might impact their faster accumulation is the first step to conducting sufficient and practical asset management activities. For example, by engaging (i) proactively in preventing uncontrolled growth of degradation (e.g., aligning ownership and contribution); and (ii) reactively in prioritizing mitigation strategies and activities (focusing on recently introducing TD items).

sted, utgiver, år, opplag, sider
Karlskrona: Blekinge Tekniska Högskola, 2023
Serie
Blekinge Institute of Technology Doctoral Dissertation Series, ISSN 1653-2090 ; 5
Emneord
Assets in Software Engineering, Asset Management, Asset Degradation, Technical Debt
HSV kategori
Forskningsprogram
Programvaruteknik
Identifikatorer
urn:nbn:se:bth-24429 (URN)978-91-7295-455-7 (ISBN)
Disputas
2023-05-31, J1630 och Zoom, Campus Karlskrona, Karlskrona, 13:00 (engelsk)
Opponent
Veileder
Tilgjengelig fra: 2023-04-12 Laget: 2023-04-11 Sist oppdatert: 2023-06-07bibliografisk kontrollert

Open Access i DiVA

fulltext(1988 kB)62 nedlastinger
Filinformasjon
Fil FULLTEXT01.pdfFilstørrelse 1988 kBChecksum SHA-512
90253cced9911a83be7e431f7c6caad84cbebf26430535755f9fedab2b2234ebff46ddd5c80b27048e7e93806b7558494eadba28b1a8f93a73ec24e8363ea625
Type fulltextMimetype application/pdf

Andre lenker

Forlagets fulltekstScopus

Person

Zabardast, EhsanGonzalez-Huerta, JavierGorschek, TonyŠmite, DarjaAlégroth, EmilFagerholm, Fabian

Søk i DiVA

Av forfatter/redaktør
Zabardast, EhsanGonzalez-Huerta, JavierGorschek, TonyŠmite, DarjaAlégroth, EmilFagerholm, Fabian
Av organisasjonen
I samme tidsskrift
Journal of Systems and Software

Søk utenfor DiVA

GoogleGoogle Scholar
Totalt: 62 nedlastinger
Antall nedlastinger er summen av alle nedlastinger av alle fulltekster. Det kan for eksempel være tidligere versjoner som er ikke lenger tilgjengelige

doi
urn-nbn

Altmetric

doi
urn-nbn
Totalt: 179 treff
RefereraExporteraLink to record
Permanent link

Direct link
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf