We Don't Need Another Hero? The Impact of "Heroes" on Software Development

A software project has "Hero Developers" when 80% of contributions are delivered by 20% of the developers. Are such heroes a good idea? Are too many heroes bad for software quality? Is it better to have more/less heroes for different kinds of projects? To answer these questions, we studied 661 open source projects from Public open source software (OSS) Github and 171 projects from an Enterprise Github. We find that hero projects are very common. In fact, as projects grow in size, nearly all project become hero projects. These findings motivated us to look more closely at the effects of heroes on software development. Analysis shows that the frequency to close issues and bugs are not significantly affected by the presence of project type (Public or Enterprise). Similarly, the time needed to resolve an issue/bug/enhancement is not affected by heroes or project type. This is a surprising result since, before looking at the data, we expected that increasing heroes on a project will slow down howfast that project reacts to change. However, we do find a statistically significant association between heroes, project types, and enhancement resolution rates. Heroes do not affect enhancement resolution rates in Public projects. However, in Enterprise projects, the more heroes increase the rate at which project complete enhancements. In summary, our empirical results call for a revision of a long-held truism in software engineering. Software heroes are far more common and valuable than suggested by the literature, particularly for medium to large Enterprise developments. Organizations should reflect on better ways to find and retain more of these heroesComment: 8 pages + 1 references, Accepted to International conference on Software Engineering - Software Engineering in Practice, 201

EFFECT OF ROLE DYNAMICS ON TRANSACTIVE MEMORY SYSTEM AND TEAM PERFORMANCE IN OPEN-SOURCE SOFTWARE TEAMS: THE MODERATING ROLE OF COMMUNICATION

Open-source software (OSS) development is leading trends in the software market. OSS teams occupied with knowledge-intensive tasks are confronted with role-related issues. Team-level role dynamics (i.e., role ambiguity and role conflict) which manifest whether information about roles (e.g., expected responsibilities, behaviours, and outcomes) perceived by members are clarified and coherent, affect team performance. Information about roles can be considered clues for expertise recognition and location, which strengthens members’ reliable understandings about others’ knowledge and work cooperation. Namely, it may influence transactive memory system (TMS), a group work pattern based on cognitive labour division. Although prior studies have proposed that role-related constructs (e.g., role identification, and role conflict) influence team cognitions (e.g., TMS) and team performance, the relationships between role dynamics, TMS and team performance are still unclear. This study intends to explore the affective and cognitive mechanism through which role dynamics influence TMS under various boundary conditions (i.e., instrumental and expressive communication), and provides a further understanding about how to enhance team performance within the mechanism. An empirical study sampling from OSS communities like SourceForge and GitHub will be conducted to verify our hypotheses. Our research intends to offer theoretical and managerial implications about role concerns in OSS teams

Nyílt fejlesztői közösségek hatása az informatikai biztonságra = The Impact of Open Source Development on IT Security

Napjainkban a nyílt forrású fejlesztési modell termékeinek felhasználása széles körben elfogadottá, sokak szerint egyenesen megkerülhetetlenné vált. A közösség, amely ezeket a szoftvereket és komponenseket létrehozza, azonban más normákat és struktúrát követ, mint a hagyományos fejlesztőcsapatok. Fontos kérdés, hogy ezeknek az eltéréseknek milyen biztonsági vonzatai lehetnek rendszerelemet felhasználó információs rendszer biztonságát illetően, illetve hogyan védekezhetünk ezek ellen. A cikkben a terület tudományos eredményének átfogó és szisztematikus elemzése alapján bemutatom a lehetséges kockázati tényezőket és a javasolt védelmi lehetőségeket

A Dataset and Analysis of Open-Source Machine Learning Products

Machine learning (ML) components are increasingly incorporated into software products, yet developers face challenges in transitioning from ML prototypes to products. Academic researchers struggle to propose solutions to these challenges and evaluate interventions because they often do not have access to close-sourced ML products from industry. In this study, we define and identify open-source ML products, curating a dataset of 262 repositories from GitHub, to facilitate further research and education. As a start, we explore six broad research questions related to different development activities and report 21 findings from a sample of 30 ML products from the dataset. Our findings reveal a variety of development practices and architectural decisions surrounding different types and uses of ML models that offer ample opportunities for future research innovations. We also find very little evidence of industry best practices such as model testing and pipeline automation within the open-source ML products, which leaves room for further investigation to understand its potential impact on the development and eventual end-user experience for the products

Online division of labour: emergent structures in Open Source Software

The development Open Source Software fundamentally depends on the participation and commitment of volunteer developers to progress on a particular task. Several works have presented strategies to increase the on-boarding and engagement of new contributors, but little is known on how these diverse groups of developers self-organise to work together. To understand this, one must consider that, on one hand, platforms like GitHub provide a virtually unlimited development framework: any number of actors can potentially join to contribute in a decentralised, distributed, remote, and asynchronous manner. On the other, however, it seems reasonable that some sort of hierarchy and division of labour must be in place to meet human biological and cognitive limits, and also to achieve some level of efficiency. These latter features (hierarchy and division of labour) should translate into detectable structural arrangements when projects are represented as developer-file bipartite networks. Thus, in this paper we analyse a set of popular open source projects from GitHub, placing the accent on three key properties: nestedness, modularity and in-block nestedness -which typify the emergence of heterogeneities among contributors, the emergence of subgroups of developers working on specific subgroups of files, and a mixture of the two previous, respectively. These analyses show that indeed projects evolve into internally organised blocks. Furthermore, the distribution of sizes of such blocks is bounded, connecting our results to the celebrated Dunbar number both in off- and on-line environments. Our conclusions create a link between bio-cognitive constraints, group formation and online working environments, opening up a rich scenario for future research on (online) work team assembly (e.g. size, composition, and formation). From a complex network perspective, our results pave the way for the study of time-resolved datasets, and the design of suitable models that can mimic the growth and evolution of OSS projects

An exploratory study on statistical process control in the UK food industry

Statistical Process Control (SPC) is an effective technique improving process performance in manufacturing companies; however, the literature shows its implementation in the food industry is still less evident. This research aims to assess the SPC implementation in the UK food industry and subsequently develops an SPC implementation roadmap (SPCIR) and SPC Readiness Self-assessment Tool for food companies to assess their readiness level to adopt SPC. Survey and multiple-case studies were conducted to identify the widespread of SPC, challenges of implementing SPC, Critical Success Factors and the reasons for not implementing SPC in this industry. A five-phase SPCIR was refined through the action research, while five SPC readiness factors were identified through the Delphi study. This study adds value to the current knowledge by extending organisational readiness theories through the identification of SPC readiness factors and expands the organisational learning theory by uncovering type of learning created within SPC implementation. This study is relevant, practical, and useful to both practitioners and academics by providing a holistic implementation roadmap to guide the managers to implement SPC not only at the organisational level but also at the project level. This study offers an itinerary of organisational readiness that enables the managers to confirm the organisational preparedness for the adoption of SPC. The small sample size may limit the generalisability of the findings. But this exploratory study provides critical information to the managers in this sector to develop a strategic plan for a successful SPC implementation

A Method to Define Requirements for System of Systems

The purpose of this research was to develop and apply a systems-based method for defining System of Systems (SoS) requirements using an inductive research design. Just as traditional Systems Engineering (TSE) includes a requirements definition phase, so too does System of Systems Engineering (SoSE); only with a wider, more over- arching, systemic perspective. TSE addresses the design and development of a single system with generally a very specific functional purpose enabled by any number of subcomponents. SoSE however, addresses the design and development of a large, complex system to meet a wide range of functional purposes enabled by any number of constituent systems, each of which may have its own individually-managed and funded TSE effort in execution. To date, the body of prescriptive guidance on how to define SoS requirements is extremely limited and nothing exists today that offers a methodological approach capable of being leveraged against real-world SoS problems. As a result, SoSE practitioners are left attempting to apply TSE techniques, methods, and tools to address requirements for the more complex problems of the SoS domain. This research addressed this gap in the systems body of knowledge by developing a method, grounded in systems principles and theory, that offers practitioners a systemic, flexible method for defining unifying and measurable SoS requirements. This provides element system managers and engineers a SoS focus to their efforts while still maximizing their autonomy to achieve system-level requirements. A rigorous mixed-method research methodology, employing inductive methods with a case application was used to develop and validate the SoS Requirements Definition Method. Two research questions provided the research focus: • How does the current body of knowledge inform the definition of a system theoretic construct to define SoS requirements? • What results from the demonstration of the candidate construct for SoS requirements definition? Using Discoverers \u27 Induction (Whewell, 1858), coupled with coding techniques from the grounded theory method (Glaser & Strauss, 1967), a systems-based method for defining SoS requirements was constructed and applied to a real-world SoS requirements definition case. The structured systemic method advances the SoSE field and shows significant promise for further development to support SoSE practitioners in the area of SoS requirements engineering