Marco Ortu

Marco Ortu

Auto-generated profile, based on publicly available information

Marco Ortu

DIEE, University of Cagliari, Cagliari, Italy

Research Focus & Metrics

Academic Career Length

12Years (2015-Present)

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

Representative Publications

View All Publications
9 June 2017 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
AMAlessandro Murgia
Alessandro Murgia
MOMarco Ortu
Marco Ortu
PTParastou Tourani
Parastou Tourani
BABram Adams
Bram Adams
SDSerge Demeyer
Serge Demeyer

16 May 2015
Verified
Book Chapter
Closed access
PDF file
MOMarco Ortu
Marco Ortu
GDGiuseppe Destefanis
Giuseppe Destefanis
MKMohamad Kassab
Mohamad Kassab
SCSteve Counsell
Steve Counsell
Michele MarchesiMichele Marchesi
Michele Marchesi
RTRoberto Tonelli
Roberto Tonelli

13 July 2016 in PeerJ Preprints
Verified
Preprint
Open access
MOMarco Ortu
Marco Ortu
GDGiuseppe Destefanis
Giuseppe Destefanis
SCSteve Counsell
Steve Counsell
SSStephen Swift
Stephen Swift
Michele MarchesiMichele Marchesi
Michele Marchesi
RTRoberto Tonelli
Roberto Tonelli
Building an effective team of developers is a complex task faced by both software companies and open source communities. The problem of forming a “dream” team involves many variables, including consideration of human factors, and it is not a dilemma solvable in a mathematical way. Empirical studies might provide interesting insights to explain which factors need to be taken into account in building a team of developers and which levers act to optimise collaboration and productivity among developers. In this paper, we present the results of an empirical study aimed at investigating the link between team diver- sity (i.e., gender, nationality) and productivity (issue fixing time). We consider issues solved from the GHTorrent dataset inferring gender and nationality of each team’s members. We also evaluate the politeness of all comments involved in issue resolution. Results show that higher gender diversity is linked with a lower team average issue fixing time and that nationality diversity is linked with lower team politeness.

13 July 2016 in PeerJ Preprints
Verified
Preprint
Open access
PDF file
MOMarco Ortu
Marco Ortu
GDGiuseppe Destefanis
Giuseppe Destefanis
SCSteve Counsell
Steve Counsell
SSStephen Swift
Stephen Swift
Michele MarchesiMichele Marchesi
Michele Marchesi
RTRoberto Tonelli
Roberto Tonelli
Building an effective team of developers is a complex task faced by both software companies and open source communities. The problem of forming a “dream” team involves many variables, including consideration of human factors, and it is not a dilemma solvable in a mathematical way. Empirical studies might provide interesting insights to explain which factors need to be taken into account in building a team of developers and which levers act to optimise collaboration and productivity among developers. In this paper, we present the results of an empirical study aimed at investigating the link between team diver- sity (i.e., gender, nationality) and productivity (issue fixing time). We consider issues solved from the GHTorrent dataset inferring gender and nationality of each team’s members. We also evaluate the politeness of all comments involved in issue resolution. Results show that higher gender diversity is linked with a lower team average issue fixing time and that nationality diversity is linked with lower team politeness.

14 March 2016 in arXiv
Verified
Preprint
Open access
PDF file
MMMika Mäntylä
Mika Mäntylä
BABram Adams
Bram Adams
GDGiuseppe Destefanis
Giuseppe Destefanis
DGDaniel Graziotin
Daniel Graziotin
MOMarco Ortu
Marco Ortu
Similar to other industries, the software engineering domain is plagued by psychological diseases such as burnout, which lead developers to lose interest, exhibit lower activity and/or feel powerless. Prevention is essential for such diseases, which in turn requires early identification of symptoms. The emotional dimensions of Valence, Arousal and Dominance (VAD) are able to derive a person's interest (attraction), level of activation and perceived level of control for a particular situation from textual communication, such as emails. As an initial step towards identifying symptoms of productivity loss in software engineering, this paper explores the VAD metrics and their properties on 700,000 Jira issue reports containing over 2,000,000 comments, since issue reports keep track of a developer's progress on addressing bugs or new features. Using a general-purpose lexicon of 14,000 English words with known VAD scores, our results show that issue reports of different type (e.g., Feature Request vs. Bug) have a fair variation of Valence, while increase in issue priority (e.g., from Minor to Critical) typically increases Arousal. Furthermore, we show that as an issue's resolution time increases, so does the arousal of the individual the issue is assigned to. Finally, the resolution of an issue increases valence, especially for the issue Reporter and for quickly addressed issues. The existence of such relations between VAD and issue report activities shows promise that text mining in the future could offer an alternative way for work health assessment surveys.

7 February 2018 in arXiv
Verified
Preprint
Open access
PDF file
RTRoberto Tonelli
Roberto Tonelli
GDGiuseppe Destefanis
Giuseppe Destefanis
Michele MarchesiMichele Marchesi
Michele Marchesi
MOMarco Ortu
Marco Ortu
Smart contracts (SC) are software codes which reside and run over a blockchain. The code can be written in different languages with the common purpose of implementing various kinds of transactions onto the hosting blockchain, They are ruled by the blockchain infrastructure and work in order to satisfy conditions typical of traditional contracts. The software code must satisfy constrains strongly context dependent which are quite different from traditional software code. In particular, since the bytecode is uploaded in the hosting blockchain, size, computational resources, interaction between different parts of software are all limited and even if the specific software languages implement more or less the same constructs of traditional languages there is not the same freedom as in normal software development. SC software is expected to reflect these constrains on SC software metrics which should display metric values characteristic of the domain and different from more traditional software metrics. We tested this hypothesis on the code of more than twelve thousands SC written in Solidity and uploaded on the Ethereum blockchain. We downloaded the SC from a public repository and computed the statistics of a set of software metrics related to SC and compared them to the metrics extracted from more traditional software projects. Our results show that generally Smart Contracts metrics have ranges more restricted than the corresponding metrics in traditional software systems. Some of the stylized facts, like power law in the tail of the distribution of some metrics, are only approximate but the lines of code follow a log normal distribution which reminds of the same behavior already found in traditional software systems.