Problems and Solutions in Distributed Software Development: A Systematic Review

Jiménez, Miguel; Piattini, Mario

doi:10.1007/978-3-642-01856-5_8

Cited by 20 publications

(14 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…80% of practitioners explicitly mention that avoiding community problems, is the reason why code smells are *not* addressed, meaning that it is more convenient to keep a technical smell than dealing with a community smell. We also confirm in open-source communities the presence and impact of 2 previously reported community smells in industry [5]. At the same time, we observe 4 new community smells that afflict open-source communities and strongly relate to code smells.…”

Section: Surveying Developerssupporting

confidence: 79%

How do community smells influence code smells?

Palomba

Tamburri

Serebrenik

et al. 2018

Proceedings of the 40th International Conference on Software Engineering: Companion Proceeedings

View full text Add to dashboard Cite

Code smells reflect sub-optimal patterns of code that often lead to critical software flaws or failure. In the same way, community smells reflect sub-optimal organisational and socio-technical patterns in the organisational structure of the software community. To understand the relation between the community smells and code smells we start by surveying 162 developers of nine opensource systems. Then we look deeper into this connection by conducting an empirical study of 117 releases from these systems. Our results indicate that community-related factors are intuitively perceived by most developers as causes of the persistence of code smells. Inspired by this observation we design a communityaware prediction model for code smells and show that it outperforms a model that does not consider community factors. CCS CONCEPTS • Software and its engineering → Software organization and properties;

show abstract

Section: Surveying Developerssupporting

confidence: 79%

How do community smells influence code smells?

Palomba

Tamburri

Serebrenik

et al. 2018

Proceedings of the 40th International Conference on Software Engineering: Companion Proceeedings

View full text Add to dashboard Cite

show abstract

“…In addition, some researches and systematic reviews have been conducted regarding these topics [11][12][13][14][15][16][17][18][19]. Moreover, previous works have addressed software systems development and, in some cases, software automatic generation.…”

Section: Methodsmentioning

confidence: 99%

An analysis of tools for automatic software development and automatic code generation

Rosales-Morales

Alor-Hernández

García-Alcaráz

et al. 2015

Rev. Fac. Ing. Antioquia

View full text Add to dashboard Cite

“…For example, an extraordinary number of recurrent issues reported for overly formal organisational structures such as Formal Networks and Formal Groups (Fredrickson 1986), these issues vary from lack of motivation or trust across employees at all levels (Miles et al 2015) to institutional isomorphism (Lai et al 2006;DiMaggio and Powell 1983), to name a few. As a matter of fact, these factors are still reported as causes for several major software failures, e.g., in the context of global software development (Jiménez and Piattini 2008). Similarly, the lack of centralised management or leadership in Informal Networks leads to organisational stagnation (Jeppesen et al 2011;Kim 2007)-this is suspected by many to be a cause behind open-source developer turnover (Homscheid and Schaarschmidt 2016;Li et al 2012).…”

Section: Motivationsmentioning

confidence: 99%

Discovering community patterns in open-source: a systematic approach and its evaluation

et al. 2018

View full text Add to dashboard Cite

The open-source phenomenon has reached the point in which it is virtually impossible to find large applications that do not rely on it. Such grand adoption may turn into a risk if the community regulatory aspects behind open-source work (e.g., contribution guidelines or release schemas) are left implicit and their effect untracked. We advocate the explicit study and automated support of such aspects and propose YOSHI (Yielding Open-Source Health Information), a tool able to map open-source communities onto community patterns, sets of known organisational and social structure types and characteristics with measurable core attributes. This mapping is beneficial since it allows, for example, (a) further investigation of community health measuring established characteristics from organisations research, (b) reuse of pattern-specific best-practices from the same literature, and (c) diagnosis of organisational anti-patterns specific to open-source, if any. We evaluate the tool in a quantitative empirical study involving 25 open-source communities from GitHub, finding that the tool offers a valuable basis to monitor key community traits behind open-source development and may form an effective combination with web-portals such as OpenHub or Bitergia. We made the proposed tool open source and publicly available.

show abstract

Problems and Solutions in Distributed Software Development: A Systematic Review

Cited by 20 publications

References 7 publications

How do community smells influence code smells?

How do community smells influence code smells?

An analysis of tools for automatic software development and automatic code generation

Discovering community patterns in open-source: a systematic approach and its evaluation

Contact Info

Product

Resources

About