Scopus İndeksli Yayınlar Koleksiyonu
Permanent URI for this collectionhttps://hdl.handle.net/20.500.12416/8651
Browse
5 results
Search Results
Conference Object Citation - WoS: 49Citation - Scopus: 66Software Engineering Education and Games: a Systematic Literature Review(Graz Univ Technolgoy, inst information Systems Computer Media-iicm, 2016) Kosa, Mehmet; Yılmaz, Murat; Yilmaz, Murat; O'Connor, Rory V.; Clarke, Paul M.; O’Connor, Rory V.; Yazılım MühendisliğiThe trend in using games in elementary level education also spreads through higher education levels and specific domains such as engineering. Recently, researchers have shown an increased interest in the usage of games in software engineering. In this paper, we are presenting a systematic review and analysis of 350 papers regarding games in software engineering education that was published in the last fifteen years. After applying our inclusion criteria and manual inspection of these studies, we have ended up with 53 primary papers. Based on a systematic process, we reported and discussed our findings with possible future research directions. The main results of this study indicate that the studies are accumulated around 5 categories: Games that learners/students play, games that learners/students develop as projects, curriculum proposals, developing/coming up with new approaches, tools, frameworks or suggestions and others.Article Citation - WoS: 6Citation - Scopus: 6Auction-Based Serious Game for Bug Tracking(Wiley, 2019) Usfekes, Cagdas; Tuzun, Eray; Yilmaz, Murat; Macit, Yagup; Clarke, PaulToday, 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.Conference Object Citation - WoS: 8Citation - Scopus: 11Exploring Software Process Variation Arising From Differences in Situational Context(Springer-verlag Berlin, 2017) Clarke, Paul M.; O'Connor, Rory V.; Solan, David; Elger, Peter; Yilmaz, Murat; Ennis, Adam; Treanor, Ryan; O’Connor, Rory V.The software development process is continuously changing, there is huge pressure to condense release cycles into shorter and shorter timeframes, tools are changing dramatically and companies must continually examine the efficacy of their development process. Attempting to hit a moving target is difficult and it is a decision which can have a major effect in terms of both the end-product and the business. In this paper, we discuss the role of situational context in deciding upon the software development process through the analysis of two case studies. The case studies take a detailed look at the organisational profile and context of each company in turn before we compare and contrast each situational context for factors that may influence the development process. We then compare the processes each company has chosen before our discussion of the role context plays in choosing a 'correct' software development process. While both companies have enjoyed sustained business growth and while both are agile in mindset, we find that they are in fact quite distinct in their processes, this distinction being driven by their different situational contexts.Conference Object Citation - WoS: 11Citation - Scopus: 13Refactoring Software Development Process Terminology Through the Use of Ontology(Springer-verlag Berlin, 2016) Clarke, Paul M.; Mesquida Calafat, Antoni Lluis; Ekert, Damjan; Ekstrom, J. J.; Gornostaja, Tatjana; Jovanovic, Milos; Yilmaz, Murat; Calafat, Antoni Lluís MesquidaIn work that is ongoing, the authors are examining the extent of software development process terminology drift. Initial findings suggest there is a degree of term confusion, with the mapping of concepts to terms lacking precision in some instances. Ontologies are concerned with identifying the concepts of relevance to a field of endeavour and mapping those concepts to terms such that term confusion is reduced. In this paper, we discuss how ontologies are developed. We also identify various sources of software process terminology. Our work to date indicates that the systematic development of a software development process ontology would be of benefit to the entire software development community. The development of such an ontology would in effect represent a systematic refactoring of the terminology and concepts produced over four decades of software process innovation.Conference Object Citation - WoS: 28Citation - Scopus: 37An Investigation of Software Development Process Terminology(Springer-verlag Berlin, 2016) Clarke, Paul; Mesquida, Antoni-Lluis; Ekert, Damjan; Ekstrom, J. J.; Gornostaja, Tatjana; Jovanovic, Milos; Yilmaz, MuratThe practice of software development has evolved considerably in recent decades, with new programming technologies, the affordability of hardware, pervasive internet access and mobile computing all contributing to the emergence of new software development processes. The newer process initiatives, which include those which are sometimes referred to as agile or lean methods, have brought with them new terms, which sometimes reflect the introduction of novel concepts. Other times, new terms correspond to long established concepts that have been repackaged. The net position is that we have a proliferation of language and term usage in the software development process domain, a problem which has implications for assessors and assessment frameworks, and for the broader community. In this paper, we explore this problem, finding that it is worthy of further research. Plus, we identify a technique suited to addressing this concern: the establishment of a canonical software process ontological model.