Proceedings Article10.1109/CSMR.2007.27
How Developers Develop Features
Orla Greevy,Tudor Gîrba,Stéphane Ducasse +2 more
- 21 Mar 2007
- pp 265-274
TL;DR: This paper correlates developer responsibilities both with a structural view of the system and with a feature view, and identifies which developers are responsible for which features, and whether the responsibilities correspond with structural source code artifacts or with features.
read more
Abstract: Software systems are typically developed by teams of developers, with responsibilities for different parts of the code. Knowledge of how the developers collaborate, and how their responsibilities are distributed over the software artifacts is a valuable source of information when reverse engineering a system. Determining which developers are responsible for which software artifacts (e.g., packages or classes) is just one perspective. In this paper we complement the static perspective with the dynamic perspective of a system in terms of its features. We want to extract information about which developers are responsible for which features. To achieve these two perspectives, we correlate developer responsibilities both with a structural view of the system and with a feature view. We identify which developers are responsible for which features, and whether the responsibilities correspond with structural source code artifacts or with features. We apply our technique to two software projects developed by two teams of students as part of their course work, and to one large open source project
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
I know what you did last summer: an investigation of how developers spend their time
Roberto Minelli,Andrea Mocci,Michele Lanza +2 more
- 16 May 2015
TL;DR: An inference model of development activities is proposed to precisely measure the time spent in editing, navigating and searching for artifacts, interacting with the UI of the IDE, and performing corollary activities, such as inspection and debugging.
7 th European Conference on Software Maintenance and Reengineering
Andrea De Lucia,Mark Harman,Robert M. Hierons,Jens Krinke +3 more
- 01 Jan 2003
TL;DR: The European Conference on Software Maintenance and Reengineering (CSMR) as mentioned in this paper is the world's premier conference on software maintenance and reengineering, which aims to promote both discussion and interaction about evolution, maintenance, and re-engineering.
77
•Dissertation
Enriching Reverse Engineering with Feature Analysis
Orla Greevy
- 01 May 2007
TL;DR: The main contribution of the work is to enrich reverse engineering analysis of object-oriented systems with semantic knowledge of features, and to introduce new techniques that treat features as the primary entities of analysis.
46
An Evolutionary Perspective on Socio-Technical Congruence: The Rubber Band Effect
Stefanie Betz,Darja mite,Samuel A. Fricker,Andrew Moss,Wasif Afzal,Mikael Svahnberg,Claes Wohlin,Jürgen Börstler,Tony Gorschek +8 more
- 09 Oct 2013
TL;DR: This paper examines empirical research related to Conway's law and its application for cross-site coordination and conjecture that changes in the communication structure alone sooner or later trigger changes inThe design structure of the software products to return the socio-technical system into the state of congruence.
Quantifying Program Comprehension with Interaction Data
Roberto Minelli,Andrea Mocci,Michele Lanza,Takashi Kobayashi +3 more
- 02 Oct 2014
TL;DR: Evidence that code navigation and editing occupies only a small fraction of the time of developers, while the vast majority of thetime is spent on reading & understanding source code is found, indicating that the importance of program comprehension was significantly underestimated by previous research.
20
References
Who should fix this bug
John Anvik,Lyndon Hiew,Gail C. Murphy +2 more
- 28 May 2006
TL;DR: This paper applies a machine learning algorithm to the open bug repository to learn the kinds of reports each developer resolves and reaches precision levels of 57% and 64% on the Eclipse and Firefox development projects respectively.
Mining version histories to guide software changes
TL;DR: Data mining is applied to version histories in order to guide programmers along related changes: "Programmers who changed these functions also changed".
1K
How do committees invent
Melvin E. Conway
- 01 Jan 1967
TL;DR: Most design activity requires continually making choices, and many of these choices may be more than design decisions; they may also be personal decisions the designer makes about his own future.
Mining version histories to guide software changes
Thomas Zimmermann,P. Weibgerber,Stephan Diehl,Andreas Zeller +3 more
- 23 May 2004
TL;DR: The ROSE prototype can correctly predict further locations to be changed and show up item coupling that is undetectable by program analysis, and can prevent errors due to incomplete changes.
Studying Software Engineers: Data Collection Techniques for Software Field Studies
TL;DR: A taxonomy of techniques is provided, focusing on those for data collection, organized according to the degree of human intervention each requires, and a discussion of how to use it effectively is provided.
588
Related Papers (5)
Tudor Gîrba,Adrian Kuhn,M. Seeberger,Stéphane Ducasse +3 more
- 05 Sep 2005
David Röthlisberger,Orla Greevy,Oscar Nierstrasz +2 more
- 25 Aug 2007
E.J. Chikofsky,James H. Cross +1 more