Defect management practices are considered an important part of traditional software development. While embracing agile methods, software development organizations have realized that defects still do exist and they mu...
详细信息
ISBN:
(纸本)9783642018527
Defect management practices are considered an important part of traditional software development. While embracing agile methods, software development organizations have realized that defects still do exist and they must be managed. Therefore defect management practices should be migrated as well, but current instructions for such a change are fragmented or incomplete. We studied three software development organizations to find out what are the main problems to consider in defect management when migrating from waterfall to agile. We identified five issues related to process, tools and metrics in a multi-site organization. This paper proposes action items to deal with these issues during the agile migration planning activities.
Geographically distributed development has consistently had to deal with the challenge of intense awareness extensively more than locally concentrated development. Awareness marks the state of being informed incorpora...
详细信息
ISBN:
(纸本)9789896740252
Geographically distributed development has consistently had to deal with the challenge of intense awareness extensively more than locally concentrated development. Awareness marks the state of being informed incorporated with an understanding of project-related activities, states or relationships of each individual employee within a given group or as a whole. In multifarious offices, where social interaction is necessary in order to distribute and locate information together with experts (as well as their availability etc.), awareness becomes a concurrent process which amplifies the exigency of easy routes for staff to be able to access this information, deferred or decentralized, in a formalized and problem-oriented way. The appropriate visualization and navigation of this information is a requirement for ensuring that staff and project managers can orientate themselves most efficiently. This paper develops a model for visualizing the collaboration in development projects using semantic networks and Web3D.
DevOps is a culture-oriented software development and operations methodology, and software organizations increasingly adopting it due to its flexibility and good business gains. Especially, in Covid situations DevOps ...
详细信息
In this talk I will provide a broad overview on developer productivity and dive deep into specific analysis related to how product, process and the people impact productivity. I will use examples from industry on effo...
详细信息
ISBN:
(纸本)9781450385626
In this talk I will provide a broad overview on developer productivity and dive deep into specific analysis related to how product, process and the people impact productivity. I will use examples from industry on effort estimation and defect prediction in product, distributed development in process and the ramp up of new employees in the people category. The talk will also cover interventions via tools and process changes and their impact and discuss future challenges. This talk will be based on previously published work.
Collaborative development is a paradigm shift in software development. Loosely coupled developers coordinate their work via distributed versioning systems (SVN, Git, and others), code reviews and priority-led bug trac...
详细信息
Collaborative development is a paradigm shift in software development. Loosely coupled developers coordinate their work via distributed versioning systems (SVN, Git, and others), code reviews and priority-led bug tracking systems. This development approach allows many different developers to input additional source code to the same source artifact. This article focuses on the lexical content of the source code produced in a collaborative environment. The lexical content is described as the 'dictionary' of the key terms contained within a source artifact. We posit that the lexical content of a Java class will increase as long as more developers add more content to the same class. We analyse the 100 top-ranked GitHub applications (at the time of the sampling) written in Java. Each of their classes is reduced to its lexical content, its size (in LOCs) recorded, as well as the number of different developers who contributed to its source code. Our results show that (i) the lexical content of Java classes is bounded in size, (ii) more developers make the size of the lexical content larger, and (iii) the lexical content of a system's classes might increase with more developers, but depending on its application domain. The implications for practitioners are two-fold: (i) classes with a large set of lexical content should be split in multiple classes, to minimize the need for further maintenance;and (ii) classes developed by many developers should adhere to specific guidelines so that its lexical content does not increase boundlessly. We tested our results in a tailored case study and we confirmed our findings: larger-than-threshold class corpora tend to deteriorate the class cohesion. (C) 2020 Elsevier Inc. All rights reserved.
To support development teams with their individual challenges of distributed collaboration in product development, the EDiT method is being developed. This paper contributes to the continuous validation of the EDiT me...
详细信息
To support development teams with their individual challenges of distributed collaboration in product development, the EDiT method is being developed. This paper contributes to the continuous validation of the EDiT method by a field study at the process team of Porsche Engineering Services GmbH to support the successful transfer into practice. The validation is based on validation by application, validation by evaluation of the contribution to success, and validation by comparison of the requirements. The contribution of the EDiT method could be proven by different measurement criteria, e.g. reducing the average number of days to finish a task by a remarkable amount.
To counteract individual losses in distributed product development, the EDiT method (Enabling distributed Teams) enables product development teams to continuously improve their distributed collaboration based on the c...
详细信息
To counteract individual losses in distributed product development, the EDiT method (Enabling distributed Teams) enables product development teams to continuously improve their distributed collaboration based on the characteristics of distributed product development. The EDiT method is the result of research into supporting distributed product development teams and is continuously being developed. For the successful transfer of the method into practice, a guideline for the situation-adequate adaptation and user-centered application of the EDiT method is designed. Therefore, a comprehensive understanding of the requirements for the EDiT method is compiled. An online guideline provides access and situation-adequate selection, adaptation, and application of the suitable method variant. A reference process model serves as orientation support for the situation-adequate application.
Software companies aim to develop high-quality software projects with the best global resources at the best cost. To achieve this global software development (GSD), an approach should be used which adopts work on proj...
详细信息
Software companies aim to develop high-quality software projects with the best global resources at the best cost. To achieve this global software development (GSD), an approach should be used which adopts work on projects across multiple distributed locations, and this is also known as distributed development. When companies attempt to implement GSD, they face numerous challenges owing to the nature of GSD and its differences from traditional methods. The objectives of this study were to identify the top software development factors that affect the overall success or failure of a software project using exploratory data analysis to find relationships between these factors, and to develop and compare risk prediction models that use machine learning classification techniques such as logistic regression, decision tree, random forest, support vector machine, K-nearest neighbors, and Naive Bayes. The findings of this study are as follows: in GSD, the top 18 factors influencing the software project are listed;and experiments show that the logistic regression and random forest models provide the best results, with an accuracy of 89% and 85%, respectively, and an area under the curve of 73% and 71%, respectively.
暂无评论