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: 6Citation - Scopus: 10The Impact of Situational Context on Software Process: a Case Study of a Very Small-Sized Company in the Online Advertising Domain(Springer international Publishing Ag, 2018) Yilmaz, Murat; O'Connor, Rory V.; Clarke, Paul M.; Giray, Gorkem; O’Connor, Rory V.A primary concern of software development is selecting a suitable methodology to implement a software project. However, this selection is affected by many factors, with evidence suggesting that a specific set of factors defines a specific situational context for a project. This situational context leads to a project-specific software process. In this paper, we report on our analysis of a very small-sized company's current software process based on a reference framework that identifies the factors of a situational context. The outcome of our case study confirms the earlier findings that a software process is highly dependent on situational factors. The company has a suitable situational context (such as very small-sized, experienced, skilled, cohesive team with low turnover) to apply agile practices and its software process is more close to an agile rather than plan-driven approach. Moreover, the company is continuously adopting its software process to the situational factors changing from project to project and over time.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: 8Citation - Scopus: 6Software Developer's Journey a Story-Driven Approach To Support Software Practitioners(Springer-verlag Berlin, 2016) Atasoy, Berke; O'Connor, Rory V.; Martens, Jean-Bernard; Clarke, Paul; Yilmaz, Murat; O’Connor, Rory V.Agile development requires a highly iterative and collaborative design process, which relies on the successful interpretation of software development activities amongst team members throughout the overall process. However, contemporary methods and tools that support agile efforts provide little help in addressing context-specific tacit knowledge, which is difficult to externalize without a shared method of interpretation. Without a continuously updated interpretation of the project vision, it is difficult to claim a shared mental model, while this is actually vital for the success of an agile process. In this paper, we address this issue and seek guidance in an approach that is commonly used in film storycraft. Film production has ample experience with externalizing experiences with the help of visual planning tools and related techniques to orchestrate the creative efforts of vast interdisciplinary production teams. We therefore propose that methods and tools from visual storycrafting can be adapted to assist software developers, not only with externalizing and discussing context-specific tacit knowledge but also to keep them creatively engaged in the development process.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.