128,498 research outputs found
Bug or Feature?
No full textThis article explores the relevance of the ‘bug or feature’ concept found in computer programming to the process of game design. Several examples are presented of successful games with either apparent bugs that proved beneficial on closer analysis, or actual bugs whose solution provided worthwhile emergent benefits. Game design is posed as a bug fixing process
Exploring usability discussions in open source development
No full textThe public nature of discussion in open source projects provides a valuable resource for understanding the mechanisms of open source software development. In this paper we explore how open source projects address issues of usability. We examine bug reports of several projects to characterise how developers address and resolve issues concerning user interfaces and interaction design. We discuss how bug reporting and discussion systems can be improved to better support bug reporters and open source developers
Usability discussions in open source development
No full textThe public nature of discussion in open source projects provides a valuable resource for understanding the mechanisms of open source software development.
In this paper we explore how open source projects address issues of usability. We examine bug reports of several projects to characterise how developers address and resolve issues concerning user interfaces and interaction design. We discuss how bug reporting and discussion systems can be improved to better support bug reporters and open source developers
moreBugs: A New Dataset for Benchmarking Algorithms for Information Retrieval from Software Repositories
No full textThis report presents moreBugs, a new publicly available dataset derived from the AspectJ and JodaTime repositories for the benchmarking of algorithms for retrieval from software repositories. As a case in point, moreBugs contains all the information required to evaluate a search-based bug localization framework — it includes a set of closed/resolved bugs mined from the bug-tracking system, and, for each bug, its patch-file list and the corresponding snapshot of the repository extracted from version history. moreBugs tracks commit-level changes made to a software repository along with its release information. In addition to the benchmarking of bug localization algorithms, the other algorithms whose benchmarking moreBugs should prove useful for include: change detection, impact analysis, software evolution, vocabulary evolution, incremental learning, and so on
Are developers fixing their own bugs?: Tracing bug-fixing and bug-seeding committers
No full textThis is the post-print version of the Article. The official published version can be accessed from the link below - Copyright @ 2011 IGI GlobalThe process of fixing software bugs plays a key role in the maintenance activities of a software project. Ideally, code ownership and responsibility should be enforced among developers working on the same artifacts, so that those introducing buggy code could also contribute to its fix. However, especially in FLOSS projects, this mechanism is not clearly understood: in particular, it is not known whether those contributors fixing a bug are the same introducing and seeding it in the first place. This paper analyzes the comm-central FLOSS project, which hosts part of the Thunderbird, SeaMonkey, Lightning extensions and Sunbird projects from the Mozilla community. The analysis is focused at the level of lines of code and it uses the information stored in the source code management system. The results of this study show that in 80% of the cases, the bug-fixing activity involves source code modified by at most two developers. It also emerges that the developers fixing the bug are only responsible for 3.5% of the previous modifications to the lines affected; this implies that the other developers making changes to those lines could have made that fix. In most of the cases the bug fixing process in comm-central is not carried out by the same developers than those who seeded the buggy code.This work has been partially funded by the European Commission, under the ALERT project (ICT-258098)
DEVELOPING FLEXIBLE ECONOMIC THRESHOLDS FOR PEST MANAGEMENT USING DYNAMIC PROGRAMMING
No full textThe rice stink bug is a major pest of rice in Texas, causing quality related damage. The previous threshold used for assisting in rice stink bug spray decisions lacked flexibility in economic and production decision variables and neglected the dynamics of the pest population. Using stochastic dynamic programming, flexible economic thresholds for the rice stink bug were generated. The new thresholds offer several advantages over the old, static thresholds, including increased net returns, incorporation of pest dynamics, user flexibility, ease of implementation, and a systematic process for updating.Economic thresholds, Dynamic programming, Pest management, Rice, Crop Production/Industries,
The repeatability of mating failure in a polyandrous bug
No full textFunding: NERC DTG ABE1-NERC13Mating failure, characterised by the lack of production of offspring following copulation, is relatively common across taxa yet is little understood. It is unclear if mating failures are stochastic occurrences between incompatible mating partners or represent a persistent, meaningful phenotype on the part of one or other sex. Here we test this in the seed bug Lygaeus simulans, by sequentially mating families of males with randomly-allocated unrelated females and calculating the repeatability of mating outcome for each individual male and family. Mating outcome is significantly repeatable within individual males but not across full-sib brothers. We conclude that mating failure represents a consistent male-associated phenotype with low heritability in this species, affected by as yet undetermined environmental influences on males.Peer reviewe
Experimental reduction of intromittent organ length reduces male reproductive success in a bug
No full textThis work was funded by the Natural Environment Research Council DTG PHD studentships to L.R.D., E.R.B.-S. and E.V.G., and an 1851 Royal Commission Research Fellowship to I.A.R.It is now clear in many species that male and female genital evolution has been shaped by sexual selection. However, it has historically been difficult to confirm correlations between morphology and fitness, as genital traits are complex and manipulation tends to impair function significantly. In this study,we investigate the functional morphology of the elongate male intromittent organ (or processus) of the seed bug Lygaeus simulans, in two ways. We first use micro-computed tomography (micro-CT) and flash-freezing to reconstruct in high resolution the interaction between the male intromittent organ and the female internal reproductive anatomy during mating.We successfully trace the path of the male processus inside the female reproductive tract. We then confirm that male processus length influences sperm transfer by experimental ablation and show that males with shortened processi have significantly reduced post-copulatory reproductive success. Importantly, male insemination function is not affected by this manipulation per se. We thus present rare, direct experimental evidence that an internal genital trait functions to increase reproductive success and show that, with appropriate staining, micro- CT is an excellent tool for investigating the functional morphology of insect genitalia during copulation.Peer reviewe
Going Beyond Counting First Authors in Author Co-citation Analysis
No full textThe present study examines one of the fundamental aspects of author co-citation analysis (ACA) - the way co-citation
counts are defined. Co-citation counting provides the data on which all subsequent statistical analyses and mappings
are based, and we compare ACA results based on two different types of co-citation counting - the traditional type that
only counts the first one among a cited work's authors on the one hand and a non-traditional type that takes into
account the first 5 authors of a cited work on the other hand. Results indicate that the picture produced through this non-traditional author co-citation counting contains more coherent author groups and is therefore considerably clearer. However, this picture represents fewer specialties in the research field being studied than that produced through the traditional first-author co-citation counting when the same number of top-ranked authors is selected and analyzed. Reasons for these effects are discussed
Bug reproduction: A collaborative practice within software maintenance activities
No full textSoftware development settings provide a great opportunity for CSCW researchers to study collaborative work. In this paper, we explore a specific work practice called bug reproduction that is a part of the software bug-fixing process. Bug reproduction is a highly collaborative process by which software developers attempt to locally replicate the ‘environment’ within which a bug was originally encountered. Customers, who encounter bugs in their everyday use of systems, play an important role in bug reproduction as they provide useful information to developers, in the form of steps for reproduction, software screenshots, trace logs, and other ways to describe a problem. Bug reproduction, however, poses major hurdles in software maintenance as it is often challenging to replicate the contextual aspects that are at play at the customers’ end. To study the bug reproduction process from a human-centered perspective, we carried out an ethnographic study at a multinational engineering company. Using semi-structured interviews, a questionnaire and half-a-day observation of sixteen software developers working on different software maintenance projects, we studied bug reproduction. In this paper, we present a holistic view of bug reproduction practices from a real-world setting and discuss implications for designing tools to address the challenges developers face during bug reproduction
- …
