1,721,061 research outputs found
Going Beyond Counting First Authors in Author Co-citation Analysis
Full text linkThe 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
Variations on the Author
Full text link“Variations on the Author” discusses two of Eduardo Coutinho’s recent films (Um Dia na Vida, from 2010, and Últimas Conversas, posthumously released in 2015) and their contribution to the general question of documentary authorship. The director’s filmography is characterized by a consistent yet self-effacing form of authorial self-inscription: Coutinho often features as an interviewer that rather than express opinions propels discourses; an interviewer that is good at listening. This mode of self-inscription characterizes him as an author who is not expressive but who is nonetheless markedly present on the screen. In Um Dia na Vida, however, Coutinho is completely absent form the image, while Últimas Conversas, on the contrary, includes a confessional prologue that moves the director from the margins to the center of his films. This article examines the ways in which these works stand out in the filmography of a director who offers new insights into the notion of cinematic authorship
Decision support for investment of developer effort in code review
No full textModern software development is a highly collaborative endeavour. Developers work in teams with tens, if not hundreds, of people who are globally distributed. At the heart of developer collaboration lies the process of code review, where fellow developers critique code changes to provide feedback to the author. Unlike the rigid formal code inspection process, which includes in-person meetings, the modern variant of code review provides developers with a lightweight, tool supported, online collaboration environment, where code changes are discussed. However, the existence of Modern Code Review (MCR) tools does not guarantee a smooth collaborative process that generates more value than cost. Indeed, the investment of developer effort in code reviewing is a key software development cost that needs to be spent efficiently and effectively.Intelligent MCR investment decisions need to be made at the level of organizations and individuals. Thus, in this thesis, we set out to support team and individual code reviewing investment decisions. First, to support decisions about the content of code reviewing feedback, we train and analyze topic models of 248,695 reviewer comments from one open source community and one proprietary organization. We observe that more context-specific, technical feedback is being raised as the studied organizations have aged and as the reviewers within those organizations accrue project-specific experience. These topic models can be used to track organizational and individual feedback trends, and whether those trends align with respect to organization and individual reviewing goals. Next, we set out to support individual decisions about which review requests require additional effort. Since patches that impact mission-critical project deliverables or deliverables that cover a broad set of products should involve more reviewing investment than others, we propose BLIMP Tracer---an impact analysis tool that pinpoints which deliverables are affected by given code changes. To evaluate BLIMP Tracer, we deploy a prototype implementation of it at a large multinational software organization, and conduct a qualitative empirical study with the developers from that organization. We observe that BLIMP Tracer not only improves the speed and accuracy of identifying the set of deliverables that are impacted by a patch, but also helps the new members of the organization to better understand the project architecture.Le développement moderne de logiciels est un effort hautement collaboratif. Les développeurs travaillent en équipe avec des dizaines, voire des centaines, de personnes réparties dans le monde entier. Au coeur de la collaboration avec les développeurs se trouve le procédé de revue de code, où d'autres développeurs critiquent les changements apportés au code pour fournir des commentaires à l'auteur. Contrairement au processus rigide d'inspection de code formelle, qui inclut des réunions en personne, la variante moderne de l'examen de code fournit aux développeurs un environnement de collaboration en ligne, où les modifications de code sont discutées. Cependant, l'existence d'outils de Revue de Code Moderne (RCM) ne garantit pas un processus collaboratif fluide qui génère plus de bénéfices que de coûts. En effet, l'investissement de l'effort de développement dans la révision de code est un coût clé de développement de logiciel qui doit être dépensé efficacement. Les décisions d'investissement intelligentes du RCM doivent être prises au niveau des organisations et des individus. Ainsi, dans cette thèse, nous avons décidé de soutenir des décisions individuelles et organisationnelles d'investissement de la revue de code. Tout d'abord, pour soutenir les décisions concernant le contenu des commentaires dans la revue de code, nous formons et analysons des modèles de sujets de 248 695 commentaires de réviseurs provenant d'une communauté open source et d'une organisation propriétaire. Nous observons que des commentaires techniques plus spécifiques au contexte sont soulevés au fur et à mesure que les organisations étudiées ont vieilli et que les évaluateurs au sein de ces organisations accumulent une expérience spécifique au projet. Ces modèles de sujets peuvent être utilisés pour suivre les tendances de la rétroaction organisationnelle et individuelle, et si ces tendances s'harmonisent avec les objectifs de la revue de code des l'organisation et l'individuels. Ensuite, nous avons décidé de prendre en charge des décisions individuelles concernant les requêtes de revue de code requièrent des efforts supplémentaires. Puisque les correctifs qui impactent les livrables de projet critiques ou les livrables qui couvrent un large éventail de produits devraient impliquer plus d'investissements de révision que d'autres, nous proposons BLIMP Tracer—un outil d'analyse d'impact qui identifie les livrables affectés par des changements de code donnés. Pour évaluer BLIMP Tracer, nous déployons un prototype dans une grande entreprise de logiciels multinationale, et menons une étude empirique qualitative avec les développeurs de cette organisation. Nous observons que BLIMP Tracer améliore non seulement la rapidité et la précision de l'identification de l'ensemble des livrables impactés par un correctif, mais aide également les nouveaux membres de l'organisation à mieux comprendre l'architecture du projet
Appropriate Similarity Measures for Author Cocitation Analysis
Full text linkWe provide a number of new insights into the methodological discussion about author cocitation analysis. We first argue that the use of the Pearson correlation for measuring the similarity between authors’ cocitation profiles is not very satisfactory. We then discuss what kind of similarity measures may be used as an alternative to the Pearson correlation. We consider three similarity measures in particular. One is the well-known cosine. The other two similarity measures have not been used before in the bibliometric literature. Finally, we show by means of an example that our findings have a high practical relevance.information science;Pearson correlation;cosine;similarity measure;author cocitation analysis
Dispelling the Myths Behind First-author Citation Counts
Full text linkWe conducted a full-scale evaluative citation analysis study of scholars in the XML research field to explore just how different from each other author rankings resulting from different citation counting methods actually are, and to demonstrate the capability of emerging data and tools on the Web in supporting more realistic citation counting methods. Our results contest some common arguments for the continued
use of first-author citation counts in the evaluation of scholars, such as high correlations between author rankings by first-author citation counts and other citation
counting methods, and high costs of using more realistic citation counting methods that are not well-supported by the ISI databases. It is argued that increasingly available digital full text research papers make it possible for citation analysis studies to go beyond what the ISI databases have directly supported and to employ more
sophisticated methods
Empirical analysis of Type-Related Defects in Python projects
No full textThis is the replication material related to the following paper submitted for TSE.
Faizan Khan, Boqi Chen, Daniel Varro, and Shane McIntosh. An Empirical Study ofType-Related Defects in Python Projects.IEEE Transactions on Software Engineering,2021(under review
Empirical analysis of Type-Related Defects in Python projects
No full textThis is the replication material related to the following paper submitted for TSE.
Faizan Khan, Boqi Chen, Daniel Varro, and Shane McIntosh. An Empirical Study ofType-Related Defects in Python Projects.IEEE Transactions on Software Engineering,2021(under review
koamabayili/VECTRON-author-checklist: VECTRON author checklist
No full textWe have done our best to complete the author checklist relating to the use of animals in the hut study. Note that the objective for the hut study was to evaluate the IRS treatment applications for residual efficacy against Anopheles mosquitoes, including the local An. coluzzii mosquito population. Cows were only used to attract mosquitoes into the huts and no tests were carried out directly on the cows. The author checklist is intended for use with studies where experiments are carried out on animals, which is why we have had such difficulty in completing this for the hut study, as many of the questions do not relate to how the cows were used
- …
