16 research outputs found

    Mining quality reputation of developers from a revision control system - and what it is good for: Preprint

    No full text
    The internal quality of source code is in uenced by various factors of the development context, e.g. programmers. We extract authorship information about collaboratively written code from a revision control system and combine it with data about le quality in order to train a reputation system. The developers' reputation is then used to predict the quality of other les they contributed to. This paper validates the existence of a relationship between developers and code quality, shows that reputation is a sound concept, compares dierent authorship mining algorithms, and measures predictive capabilities. In the future, the results may serve as benchmarks for authorship mining and help to coste ciently increase the quality of software: by enabling reputation systems that redu ce cowboy coding, o

    First results from an investigation into the validity of developer reputation derived from wiki articles and source code

    No full text
    The internal quality of software is often neglected by developers for various reasons like time pressure or a general dislike for certain activities. Yet internal quality is important to speed up development and to keep software maintainable. We present a way to use reputation systems to improve the internal quality of software by putting artifacts like wiki articles and source code under their control. Specifically, we show that reputation scores derived from such artifacts reflect actual reputation in the developer community using data from a work group wiki and an open source project

    Finest Magic Cloth or a Naked Emperor? The SKQuest Data Set on Software Metrics for Improving Transparency and Quality

    No full text
    Software development has a problem with transparency/visibility. As an intangible product, software and its intermediate development results are hard to see or touch. Customers of custom software have difficulties checking progress, and risk coming out with costly but low-quality software. In the space domain with its often expensive and one-of-a-kind devices, which are developed in complex multitier supply chains, the risk is even greater. This paper presents the SKQuest data set. It contains the completed responses with 190 variables from an empirical study with over 100 software experts. The data set covers distinct aspects of measuring metrics and transparency in software projects. To show what information lies in the data set, the paper investigates, and affirms, from different perspectives, the following questions: Is transparency a problem in software development projects? Is there a desire for more transparency in projects? Can metrics contribute to improving the situation? Moreover, it attempts to replicate the results of an earlier study. The main contribution of this paper is, however, the SKQuest data set that is published with this paper in CSV formatas. It is a tool that enables systematic investigations of software metrics and allows research on how they can improve the efficiency of the software lifecycle, not limited to, but particularly with respect to transparency. Consequently, the paper may serve as a starting point for future research avenues in academia and industry and help to improve existing and future standards in software development

    Hybrid Software and System Development in Practice: Waterfall, Scrum, and Beyond

    Get PDF
    Software and system development faces numerous challenges of rapidly changing markets. To address such challenges, companies and projects design and adopt speciĄc development approaches by combining well-structured methods and Ćexible agile practices. Yet, the number of methods and practices is large and the actual process composition is often carried out in an ad-hoc manner. This paper reports on a survey on hybrid software development approaches. We study which approaches are used in practice, how diferent approaches are combined, and what contextual factors inĆuence the use and combination of hybrid software development approaches. This summary refers to the paper Hybrid Software and System Development in Practice: Waterfall, Scrum, and Beyond [Ku17]. This paper was published as full research paper in the proceedings of the International Conference on Software System Process
    corecore