How many researchers does it take to make impact?: mining software engineering publication data for collaboration insights

Authors:
Subhajit Datta;Santonu Sarkar;A. S. M. Sajeev;Nishant Kumar
Affiliations:
Singapore University of Technology and Design;Infosys Labs, Bangalore, India;University of New England, Australia;Appnomic Systems, India
Venue:
Proceedings of the 6th ACM India Computing Convention
Year:
2013

Citing 8
Cited 0

An Empirical Study of Speed and Communication in Globally Distributed Software Development

IEEE Transactions on Software Engineering
Latent dirichlet allocation

The Journal of Machine Learning Research
Using Multivariate Statistics (5th Edition)

Using Multivariate Statistics (5th Edition)
Stop the numbers game

Communications of the ACM
Seeing inside: Using social network analysis to understand patterns of collaboration and coordination in global software teams

ICGSE '07 Proceedings of the International Conference on Global Software Engineering
Evaluation methods for topic models

ICML '09 Proceedings of the 26th Annual International Conference on Machine Learning
Continuing Prospects for an Engineering Discipline of Software

IEEE Software
The web of topics: discovering the topology of topic evolution in a corpus

Proceedings of the 20th international conference on World wide web

Quantified Score

Hi-index	0.00

Visualization

Abstract

In the three and half decades since the inception of organized research publication in software engineering, the discipline has gained a significant maturity. This journey to maturity has been guided by the synergy of ideas, individuals and interactions. In this journey software engineering has evolved into an increasingly empirical discipline. Empirical sciences involve significant collaboration, leading to large teams working on research problems. In this paper we analyze a corpus of 19,000+ papers, written by 21,000+ authors from 16 publication venues between 1975 to 2010, to understand what is the ideal team size that has produced maximum impact in software engineering research, and whether researchers in software engineering have maintained the same co-authorship relations over long periods of time as a means of achieving research impact.