DGDaniel Graziotin

Daniel Graziotin

*This is an algorithmically generated author record based on publicly available information.

Current Organizations / Institutes

The organizations/institutes from the scholar's latest article


Daniel Graziotin has a total of 6 co-authors. Here are the top co-authors by number of shared publications:


Latest Publications

  • Open Access

    A Community's Perspective on the Status and Future of Peer Review in Software Engineering

    by Lutz Prechelt, Daniel Graziotin, Daniel Méndez Fernández

    Context: Pre-publication peer review of scientific articles is considered a key element of the research process in software engineering, yet it is often perceived as not to work fully well. Objective: We aim at understanding the perceptions of and attitudes towards peer review of authors and reviewers at one of software engineering's most prestigious venues, the International Conference on Software Engineering (ICSE). Method: We invited 932 ICSE 2014/15/16 authors and reviewers to participate in a survey with 10 closed and 9 open questions. Results: We present a multitude of results, such as: Respondents perceive only one third of all reviews to be good, yet one third as useless or misleading; they propose double-blind or zero-blind reviewing regimes for improvement; they would like to see showable proofs of (good) reviewing work be introduced; attitude change trends are weak. Conclusion: The perception of the current state of software engineering peer review is fairly negative. Also, we found hardly any trend that suggests reviewing will improve by itself over time; the community will have to make explicit efforts. Fortunately, our (mostly senior) respondents appear more open for trying different peer reviewing regimes than we had expected.

  • Open Access

    Factors and actors leading to the adoption of a JavaScript framework

    by Amantia Pano, Daniel Graziotin, Pekka Abrahamsson

    The increasing popularity of JavaScript has led to a variety of JavaScript frameworks that aim to help developers to address programming tasks. However, the JavaScript frameworks' number has risen rapidly to thousands and more. It is challenging for practitioners to identify the frameworks that best fit to their needs and to develop new ones fitting such needs. There is a lack of knowledge regarding what drives developers towards the choice. This paper explores the factors and actors that lead to a choice of a JavaScript framework. We conducted a qualitative interpretive study of semi-structured interviews, analyzed and sampled using the grounded theory methodology. We interviewed 18 participants, chosen with judgmental sampling of decision makers regarding the JavaScript framework selection, up to reaching theoretical saturation. We offer a model of desirable JavaScript framework adoption factors. The factors are grouped into categories that are derived by the Unified Theory of Acceptance and Use of Technology (Venkatesh et al., 2003). The factors are performance expectancy (performance, size), effort expectancy (automatization, learnability, flexibility, complexity, understandability), social influence (competitor analysis, collegial advice, community size, community responsiveness), facilitating conditions (suitability, updates, modularity, isolation, extensibility), and price value. A combination of four decision makers, which are customer, developer, team, and team leader, leads to the choice. Our model contributes to the body of knowledge related to technology adoption of software engineers. As a practical implication, our model is useful for Web and framework developers.

  • Open Access

    Consequences of Unhappiness While Developing Software

    by Daniel Graziotin, Fabian Fagerholm, Xiaofeng Wang, Pekka Abrahamsson

    The growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding the positive side of happiness -- positive emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that also studying the negative side -- unhappiness -- could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, and is mainly expressed in terms of development productivity and software quality. In this paper, we attempt to uncover the experienced consequences of unhappiness among software developers. Using qualitative data analysis of the responses given by 181 questionnaire participants, we identified 49 consequences of unhappiness while doing software development. We found detrimental consequences on developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data, will spawn new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.

  • Open Access

    Unhappy Developers: Bad for Themselves, Bad for Process, and Bad for Software Product

    by Daniel Graziotin, Fabian Fagerholm, Xiaofeng Wang, Pekka Abrahamsson

    Recent research in software engineering supports the "happy-productive" thesis, and the desire of flourishing happiness among programmers is often expressed by industry practitioners. Recent literature has suggested that a cost-effective way to foster happiness and productivity among workers could be to limit unhappiness of developers due to its negative impact. However, possible negative effects of unhappiness are still largely unknown in the software development context. In this paper, we present the first results from a study exploring the consequences of the unhappy developers. Using qualitative data analysis of the survey responses given by 181 participants, we identified 49 potential consequences of unhappiness while developing software. These results have several implications. While raising the awareness of the role of moods, emotions and feelings in software development, we foresee that our classification scheme will spawn new happiness studies linking causes and effects, and it can act as a guideline for developers and managers to foster happiness at work.