Browsing by Author "Clarke, P."

Now showing 1 - 5 of 5

Open Access
Adopting augmented reality for the purpose of software development process training and improvement: an exploration
(Springer, Cham, 2018) Ohri, İ.; Öge, İ.; Orkun, B.; Yilmaz, M.; Tüzün, Eray; Clarke, P.; O’Connor, R. V.
Augmented reality (AR) is a technological field of study that bridges the physical and digital world together with a view to improving user experience. AR holds great potential to change the delivery of software services or software process improvement by utilizing a specific set of components. The purpose of this exploratory study is to propose an integration framework to support AR for improving the onboarding process, notably in introducing new hires to the development process while performing their daily tasks. In addition, it also aims to enhance the software development workflow process using AR. Similar to a GPS device that can guide you from point A to point B, our goal is to create software artifacts like navigation components where software teams may benefit from digitally enhanced working conditions provided using AR. After conducting a review in the literature, we confirmed that there is lack of studies about the combination of augmented reality with software engineering disciplines for onboarding. In this paper, we formalized our approach based on the benefits of AR. Ultimately; we propose an AR-based preliminary model for improving the software development process.
Open Access
Auction-based serious game for bug tracking
(The Institution of Engineering and Technology(IET ), 2019-10) Üsfekes, Ç.; Tüzün, Eray; Yılmaz, M.; Macit, Y.; Clarke, P.
Today, one of the challenges in software engineering is utilising application lifecycle management (ALM) tools effectively in software development. In particular, it is hard for software developers to engage with the work items that are appointed to themselves in these ALM tools. In this study, the authors have focused on bug tracking in ALM where one of the most important metrics is mean time to resolution that is the average time to fix a reported bug. To improve this metric, they developed a serious game application based on an auction-based reward mechanism. The ultimate aim of this approach is to create an incentive structure for software practitioners to find and resolved bugs that are auctioned where participants are encouraged to solve and test more bugs in less time and improve quality of software development in a competitive environment. They conduct hypothesis tests by performing a Monte Carlo simulation. The preliminary results of this research support the idea that using a gamification approach for an issue tracking system enhances the productivity and decreases mean time to resolution.
Open Access
Editorial: Best papers of the 14th international conference on software and system processes (ICSSP 2020) and 15th international conference on global software engineering (ICGSE 2020)
(John Wiley and Sons Ltd, 2023-01-30) Steinmacher, I.; Clarke, P.; Tüzün, Eray; Britto, R.
Today's software industry is global, virtual, and depending more than ever on strong and reliable processes. Stakeholders and infrastructure are distributed across the globe, posing challenges that go beyond those with co-located teams and servers. Software Engineering continues to be a complex undertaking, with projects challenged to meet expectations, especially regarding costs. We know that Software Engineering is an ever-changing discipline, with the result that firms and their employees must regularly embrace new methods, tools, technologies, and processes. In 2020, the International Conference on Global Software Engineering (ICGSE) and the International Conference on Systems and Software Processes (ICSSP) joined forces aiming to create a holistic understanding of the software landscape both from the perspective of human and infrastructure distribution and also the processes to support software development. Unfortunately, these challenges have become even more personal to many more in 2020 due to the disruption introduced by the COVID-19 pandemic, which forced both conferences to be held virtually. As an outcome of the joint event, we selected a set of the best papers from the two conferences, which were invited to submit extended versions to this Special Issue in the Journal of Software: Maintenance and Evolution. Dedicated committees were established to identify the best papers. Eight papers were invited and ultimately, seven of these invited papers have made it into this Special Issue. © 2023 John Wiley & Sons, Ltd.
Open Access
Editorial: Machine learning, software process, and global software engineering
(John Wiley and Sons Ltd, 2023-01-30) Steinmacher, I.; Clarke, P.; Tüzün, Eray; Britto, R.
On June 26–28, 2020, the International Conference on Software and Systems Processes (ICSSP 2020) and the International Conference on Global Software Engineering (ICGSE 2020) were held in virtual settings during the first year of the COVID pandemic. Several submissions to the joint event have been selected for inclusion in this special issue, focusing on impactful and timely contributions to machine learning (ML). At present, many in our field are enthusiastic about the potential of ML, yet some risks should not be casually overlooked or summarily dismissed. Each ML implementation is subtly different from any other implementation, and the risk profile varies greatly based on the approach adopted and the implementation context. The ICSSP/ICGSE 2020 Program Committees have encouraged submissions that explore the risks and benefits associated with ML so that the important discussion regarding ML efficacy and advocacy can be further elaborated. Four contributions have been included in this special issue. © 2023 John Wiley & Sons, Ltd.
Open Access
What makes agile software development agile
(IEEE, 2021-07-26) Kuhrmann, M.; Tell, P.; Hebig, R.; Klunder, J. A-C; Munch, J.; Linssen, O.; Pfahl, D.; Felderer, M.; Prause, C.; Macdonell, S.; Nakatumba-Nabende, J.; Raffo, D.; Beecham, S.; Tüzün, Eray; Lopez, G.; Paez, N.; Fontdevila, D.; Licorish, S.; Kupper, S.; Ruhe, G.; Knauss, E.; Özcan-Top, O.; Clarke, P.; Mc Caffery, F. H.; Genero, M.; Vizcaino, A.; Piattini, M.; Kalinowski, M.; Conte, T.; Prikladnicki, R.; Krusche, S.; Coşkunçay, A.; Scott, E.; Calefato, F.; Pimonova, S.; Pfeiffer, R-H; Schultz, U. P.; Heldal, R.; Fazal-Baqaie, M.; Anslow, C.; Nayebi, M.; Schneider, K.; Sauer, S.; Winkler, D.; Biffl, S.; Bastarrica, C.; Richardson, I.
Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile In this article, we investigate the question: what makes a software development method agile We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.