Ändra sökning
RefereraExporteraLänk till posten
Permanent länk

Direktlänk
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annat format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annat språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf
Ownership vs Contribution: Investigating the Alignment between Ownership and Contribution
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-0003-2300-068x
2022 (Engelska)Ingår i: IEEE 19th International Conference on Software Architecture Companion, ICSA-C 2022, Institute of Electrical and Electronics Engineers (IEEE), 2022, s. 30-34Konferensbidrag, Publicerat paper (Refereegranskat)
Abstract [en]

Software development is a collaborative endeavour. Organisations that develop software assign modules to different teams, i.e., teams own their modules and are responsible for them. These modules are rarely isolated, meaning that there exist dependencies among them. Therefore, other teams might often contribute to developing modules they do not own. The contribution can be, among other types, in the form of code authorship, code review, and issue detection. This research presents a model to investigate the alignment between module ownership and contribution and the preliminary results of an industrial case study to evaluate the model in practice. Our model uses seven metrics to assess teams' contributions. Initial results suggest that the model correctly identifies misalignment between ownership and contribution. The detection of misalignment between ownership and contribution is the first step towards investigating the impact it might have on the faster accumulation of Technical Debt. © 2022 IEEE.

Ort, förlag, år, upplaga, sidor
Institute of Electrical and Electronics Engineers (IEEE), 2022. s. 30-34
Nyckelord [en]
Measurement, Codes, Software architecture, Conferences, Refining, Collaboration, Software
Nationell ämneskategori
Programvaruteknik
Identifikatorer
URN: urn:nbn:se:bth-23320DOI: 10.1109/ICSA-C54293.2022.00013ISI: 000838715700009Scopus ID: 2-s2.0-85132145417ISBN: 9781665494939 (tryckt)OAI: oai:DiVA.org:bth-23320DiVA, id: diva2:1676639
Konferens
2022 IEEE 19th International Conference on Software Architecture Companion, ICSA-C, Honolulu, 12 March 2022 through 15 March 2022
Ingår i projekt
SHADE- A value-oriented strategy for managing the degradation of software assets, KK-stiftelsenSERT- Software Engineering ReThought, KK-stiftelsen
Forskningsfinansiär
KK-stiftelsen, 20170176KK-stiftelsen, 20180010
Anmärkning

open access

Tillgänglig från: 2022-06-27 Skapad: 2022-06-27 Senast uppdaterad: 2023-04-11Bibliografiskt granskad
Ingår i avhandling
1. Understanding Asset Degradation in Software Engineering
Öppna denna publikation i ny flik eller fönster >>Understanding Asset Degradation in Software Engineering
2023 (Engelska)Doktorsavhandling, sammanläggning (Övrigt vetenskapligt)
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).

Ort, förlag, år, upplaga, sidor
Karlskrona: Blekinge Tekniska Högskola, 2023
Serie
Blekinge Institute of Technology Doctoral Dissertation Series, ISSN 1653-2090 ; 5
Nyckelord
Assets in Software Engineering, Asset Management, Asset Degradation, Technical Debt
Nationell ämneskategori
Programvaruteknik
Forskningsämne
Programvaruteknik
Identifikatorer
urn:nbn:se:bth-24429 (URN)978-91-7295-455-7 (ISBN)
Disputation
2023-05-31, J1630 och Zoom, Campus Karlskrona, Karlskrona, 13:00 (Engelska)
Opponent
Handledare
Tillgänglig från: 2023-04-12 Skapad: 2023-04-11 Senast uppdaterad: 2023-06-07Bibliografiskt granskad

Open Access i DiVA

fulltext(1173 kB)285 nedladdningar
Filinformation
Filnamn FULLTEXT01.pdfFilstorlek 1173 kBChecksumma SHA-512
bc8a8b8666f2b4606def812101945218f47ebfa09f575db8e28bd5d80928e207587a24635b54d1e6a93efc96fd90ec5eb92804937798785eeb583620b8160476
Typ fulltextMimetyp application/pdf

Övriga länkar

Förlagets fulltextScopus

Person

Zabardast, EhsanGonzalez-Huerta, JavierTanveer, Binish

Sök vidare i DiVA

Av författaren/redaktören
Zabardast, EhsanGonzalez-Huerta, JavierTanveer, Binish
Av organisationen
Institutionen för programvaruteknik
Programvaruteknik

Sök vidare utanför DiVA

GoogleGoogle Scholar
Totalt: 285 nedladdningar
Antalet nedladdningar är summan av nedladdningar för alla fulltexter. Det kan inkludera t.ex tidigare versioner som nu inte längre är tillgängliga.

doi
isbn
urn-nbn

Altmetricpoäng

doi
isbn
urn-nbn
Totalt: 172 träffar
RefereraExporteraLänk till posten
Permanent länk

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