Davide Fucci

Davide Fucci

Auto-generated profile, based on publicly available information

Davide Fucci

Blekinge Institute of Technology, Karlskrona, Sweden

Research Focus & Metrics

Academic Career Length

14Years (2013-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
18 October 2016 in IEEE Transactions on Software Engineering
Verified
Journal Article
Open access
DFDavide Fucci
Davide Fucci
HEHakan Erdogmus
Hakan Erdogmus
BTBurak Turhan
Burak Turhan
MOMarkku Oivo
Markku Oivo
NJNatalia Juristo
Natalia Juristo
Background: Test-driven development (TDD) is a technique that repeats short coding cycles interleaved with testing. The developer first writes a unit test for the desired functionality, followed by the necessary production code, and refactors the code. Many empirical studies neglect unique process characteristics related to TDD iterative nature. Aim: We formulate four process characteristic: sequencing, granularity, uniformity, and refactoring effort. We investigate how these characteristics impact quality and productivity in TDD and related variations. Method: We analyzed 82 data points collected from 39 professionals, each capturing the process used while performing a specific development task. We built regression models to assess the impact of process characteristics on quality and productivity. Quality was measured by functional correctness. Result: Quality and productivity improvements were primarily positively associated with the granularity and uniformity. Sequencing, the order in which test and production code are written, had no important influence. Refactoring effort was negatively associated with both outcomes. We explain the unexpected negative correlation with quality by possible prevalence of mixed refactoring. Conclusion: The claimed benefits of TDD may not be due to its distinctive test-first dynamic, but rather due to the fact that TDD-like processes encourage fine-grained, steady steps that improve focus and flow.

15 February 2022 in Requirements Engineering
Verified
Journal Article
Open access
PDF file
LMLloyd Montgomery
Lloyd Montgomery
DFDavide Fucci
Davide Fucci
ABAbir Bouraffa
Abir Bouraffa
LSLisa Scholz
Lisa Scholz
WMWalid Maalej
Walid Maalej
Research has repeatedly shown that high-quality requirements are essential for the success of development projects. While the term “quality” is pervasive in the field of requirements engineering and while the body of research on requirements quality is large, there is no meta-study of the field that overviews and compares the concrete quality attributes addressed by the community. To fill this knowledge gap, we conducted a systematic mapping study of the scientific literature. We retrieved 6905 articles from six academic databases, which we filtered down to 105 relevant primary studies. The primary studies use empirical research to explicitly define, improve, or evaluate requirements quality. We found that empirical research on requirements quality focuses on improvement techniques, with very few primary studies addressing evidence-based definitions and evaluations of quality attributes. Among the 12 quality attributes identified, the most prominent in the field are ambiguity, completeness, consistency, and correctness. We identified 111 sub-types of quality attributes such as “template conformance” for consistency or “passive voice” for ambiguity. Ambiguity has the largest share of these sub-types. The artefacts being studied are mostly referred to in the broadest sense as “requirements”, while little research targets quality attributes in specific types of requirements such as use cases or user stories. Our findings highlight the need to conduct more empirically grounded research defining requirements quality, using more varied research methods, and addressing a more diverse set of requirements types.

4 February 2017 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
ODOscar Dieste
Oscar Dieste
AAAlejandrina M. Aranda
Alejandrina M. Aranda
FUFernando Uyaguari
Fernando Uyaguari
BTBurak Turhan
Burak Turhan
ATAyse Tosun
Ayse Tosun
NJNatalia Juristo
Natalia Juristo
Context There is a widespread belief in both SE and other branches of science that experience helps professionals to improve their performance. However, cases have been reported where experience not only does not have a positive influence but sometimes even degrades the performance of professionals. Aim Determine whether years of experience influence programmer performance. Method We have analysed 10 quasi-experiments executed both in academia with graduate and postgraduate students and in industry with professionals. The experimental task was to apply ITLD on two experimental problems and then measure external code quality and programmer productivity. Results Programming experience gained in industry does not appear to have any effect whatsoever on quality and productivity. Overall programming experience gained in academia does tend to have a positive influence on programmer performance. These two findings may be related to the fact that, as opposed to deliberate practice, routine practice does not appear to lead to improved performance. Experience in the use of productivity tools, such as testing frameworks and IDE also has positive effects. Conclusion Years of experience are a poor predictor of programmer performance. Academic background and specialized knowledge of task-related aspects appear to be rather good predictors.

28 December 2016 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
ATAyse Tosun
Ayse Tosun
ODOscar Dieste
Oscar Dieste
DFDavide Fucci
Davide Fucci
SVSira Vegas
Sira Vegas
BTBurak Turhan
Burak Turhan
NJNatalia Juristo
Natalia Juristo
Existing empirical studies on test-driven development (TDD) report different conclusions about its effects on quality and productivity. Very few of those studies are experiments conducted with software professionals in industry. We aim to analyse the effects of TDD on the external quality of the work done and the productivity of developers in an industrial setting. We conducted an experiment with 24 professionals from three different sites of a software organization. We chose a repeated-measures design, and asked subjects to implement TDD and incremental test last development (ITLD) in two simple tasks and a realistic application close to real-life complexity. To analyse our findings, we applied a repeated-measures general linear model procedure and a linear mixed effects procedure. We did not observe a statistical difference between the quality of the work done by subjects in both treatments. We observed that the subjects are more productive when they implement TDD on a simple task compared to ITLD, but the productivity drops significantly when applying TDD to a complex brownfield task. So, the task complexity significantly obscured the effect of TDD. Further evidence is necessary to conclude whether TDD is better or worse than ITLD in terms of external quality and productivity in an industrial setting. We found that experimental factors such as selection of tasks could dominate the findings in TDD studies.

23 March 2021 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
ASAdrian Santos
Adrian Santos
SVSira Vegas
Sira Vegas
ODOscar Dieste
Oscar Dieste
FUFernando Uyaguari
Fernando Uyaguari
ATAyşe Tosun
Ayşe Tosun
NJNatalia Juristo
Natalia Juristo

10 November 2024 in Information and Software Technology
Verified
Journal Article
Open access
OKOleksandr Kosenkov
Oleksandr Kosenkov
PEParisa Elahidoost
Parisa Elahidoost
TGTony Gorschek
Tony Gorschek
JFJannik Fischbach
Jannik Fischbach
DMDaniel Mendez
Daniel Mendez
RMRahul Mohanani
Rahul Mohanani