SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "WFRF:(Besker Terese 1970) srt2:(2017)"

Sökning: WFRF:(Besker Terese 1970) > (2017)

  • Resultat 1-5 av 5
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Besker, Terese, 1970, et al. (författare)
  • An investigation of Technical Debt in Automatic Production Systems
  • 2017
  • Ingår i: ACM International Conference Proceeding Series. - New York, NY, USA : ACM. - 9781450352642 ; Part F129907
  • Konferensbidrag (refereegranskat)abstract
    • Technical Debt is a recent concept, borrowed from the financial domain. It has been recently used in software development to describe technical sub-optimal solutions that have short-term benefits but long-term extra-costs. However, no body of literature investigates how Automatic Production Systems companies deal with Technical Debt. We investigated how Technical Debt is known, how much it hurts and how is managed in an automatic production systems company. Results from one in-depth investigation show that the automatic production systems company spend quite a lot of resources because of Technical Debt, both in the extra-costs (interest) and in its management. The company presents moderate awareness of what Technical Debt is and how much is present in its systems. However, the tracking level is quite low. We, therefore, claim that Technical Debt needs more research in this domain, as it is a source of substantial extra-costs and the current practices to manage it are not suitable.
  •  
2.
  • Besker, Terese, 1970, et al. (författare)
  • Impact of Architectural Technical Debt on Daily Software Development Work - A Survey of Software Practitioners
  • 2017
  • Ingår i: Proceedings - 43rd Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2017. - 9781538621400 ; , s. 278-287
  • Konferensbidrag (refereegranskat)abstract
    • — The negative consequences of Technical Debt is an area of increasing interest, and more specifically the Architectural aspects of it have received increased attention in the last few years. Besides the negative effects of Architectural Technical Debt on the overall software product quality in terms of hindering evolution and causing high maintenance costs, Architectural Technical Debt also has a significant negative impact on software practitioners’ daily work. Although a great deal of theoretical work on Architectural Technical Debt has been undertaken, there is a lack of empirical studies that examine the negative effects of Architectural Technical Debt during the software development lifecycle. The aim of this study is to investigate how practitioners perceive and estimate the impact of Architectural Technical Debt during the software development process. This paper reports the results of an online web survey providing quantitative data from 258 participants. The contribution of this paper is threefold: First, it shows that practitioners experience that the Architectural type of Technical Debt has the highest negative impact on daily software development work. Secondly, we provide evidence that does not support the commonly held belief that Architectural Technical Debt increases with the age of the software. Thirdly, we show that despite different responsibilities and working tasks of software professionals, Architectural Technical Debt negatively affects all roles without any significant difference between the roles.
  •  
3.
  • Besker, Terese, 1970, et al. (författare)
  • The Pricey Bill of Technical Debt - When and by whom will it be paid?
  • 2017
  • Ingår i: IEEE International Conference on Software Maintenance and Evolution (ICSME). - 9781538609927 ; , s. 13-23
  • Konferensbidrag (refereegranskat)abstract
    • — Software companies need to support continuous and fast delivery of customer value both in short and a long-term perspective. However, this can be hindered by evolution limitations and high maintenance efforts due to internal software quality issues by what is described as Technical Debt. Although significant theoretical work has been undertaken to describe the negative effects of Technical Debt, these studies tend to have a weak empirical basis and often lack quantitative data. The aim of this study is to estimate wasted time, caused by the Technical Debt interest during the software life-cycle. This study also investigates how practitioners perceive and estimate the impact of the negative consequences due to Technical Debt during the software development process. This paper reports the results of both an online web-survey provided quantitative data from 258 participants and follow-up interviews with 32 industrial software practitioners. The importance and originality of this study contributes and provides novel insights into the research on Technical Debt by quantifying the perceived interest and the negative effects it has on the software development life-cycle. The findings show that on average, 36 % of all development time is estimated to be wasted due to Technical Debt; Complex Architectural Design and Requirement Technical Debt generates most negative effect; and that most time is wasted on understanding and/or measuring the Technical Debt. Moreover, the analysis of the professional roles and the age of the software system in the survey revealed that different roles are affected differently and that the consequences of Technical Debt are also influenced by the age of the software system.
  •  
4.
  • Besker, Terese, 1970, et al. (författare)
  • Time to Pay Up - Technical Debt from a Software Quality Perspective
  • 2017
  • Ingår i: CibSE. - 9789873806988 ; , s. 235-248
  • Konferensbidrag (refereegranskat)abstract
    • Software companies need to produce high-quality software and support continuous and fast delivery of customer value both in the short and long term. However, this can be hindered by compromised software quality attributes that have an important influence on the overall software development lifecycle. The aim of this study is threefold: to understand which quality issues have the most negative impact on the software development lifecycle process, to deter-mine the association of these quality issues in relation to the age of the software, and relate each of these quality issues to the impact of different Technical Debt types. This paper reports the results of six initial group interviews with in total 43 practitioners, an online web-survey provided quantitative data from 258 participants and seven follow-up group interviews with in total 32 industrial software practitioners. First, this study shows that practitioners identified maintenance difficulties, a limited ability to add new features, restricted reusability, and poor reliability, and performance degradation issues as the quality issues having the most negative effect on the software development lifecycle. Secondly, we found no evidence for the generally held view that the Technical Debt increases with age of the software. Thirdly, we show that Technical Debt affects not only productivity but also several other quality attributes of the system.
  •  
5.
  • Ghanbari, Hadi, et al. (författare)
  • Looking for Peace of Mind? Manage your (Technical) Debt - An Exploratory Field Study
  • 2017
  • Ingår i: International Symposium on Empirical Software Engineering and Measurement. - 1949-3789 .- 1949-3770. ; 2017-November
  • Konferensbidrag (refereegranskat)abstract
    • Background: In the last two decades Technical Debt (TD) has received a considerable amount of attention from software engineering research and practice. Recently, a small group of studies suggests that, in addition to its technical and economic consequences, TD can affect developers’ psychological states and morale. However, until now there has been a lack of empirical research clarifying such influences. Aims: In this study, we aim at taking the first step in filling this gap by investigating the potential impacts of TD and its management on developers’ morale. Method: Drawing from previous literature on morale, we decided to explore the influence of TD and its management on three dimensions of morale called affective, future/goal, and interpersonal antecedents. In so doing, we conducted an exploratory field study and collected data from software professionals active in different industrial domains through eight qualitative interviews and an online survey (n=33). Results: Our results indicate that TD mainly has a negative influence on future/goal and affective antecedents of morale. This is mainly because the occurrence of TD hinders developers from performing their tasks and achieving their goals. TD management, on the other hand, has a positive influence on all the three dimensions of morale since it is associated with positive feelings and interpersonal feedback as well as a sense of progress. Conclusions: According to the results of this empirical study, the occurrence of TD reduces developers’ morale, while its management increases developers’ morale.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-5 av 5
Typ av publikation
konferensbidrag (5)
Typ av innehåll
refereegranskat (5)
Författare/redaktör
Martini, Antonio, 19 ... (5)
Bosch, Jan, 1967 (5)
Besker, Terese, 1970 (5)
Tichy, Matthias, 197 ... (1)
Ghanbari, Hadi (1)
Lärosäte
Chalmers tekniska högskola (5)
Språk
Engelska (5)
Forskningsämne (UKÄ/SCB)
Naturvetenskap (5)
År

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy