A field study of the software design process for large systems
Communications of the ACM
People, Organizations, and Process Improvement
IEEE Software
Coordination in software development
Communications of the ACM
Splitting the organization and integrating the code: Conway's law revisited
Proceedings of the 21st international conference on Software engineering
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
Hipikat: recommending pertinent software development artifacts
Proceedings of the 25th International Conference on Software Engineering
Practices of Software Maintenance
ICSM '98 Proceedings of the International Conference on Software Maintenance
Maintaining mental models: a study of developer work habits
Proceedings of the 28th international conference on Software engineering
Textual Allusions to Artifacts in Software-Related Repositories
Proceedings of the 2006 international workshop on Mining software repositories
Questions programmers ask during software evolution tasks
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Information Needs in Collocated Software Development Teams
ICSE '07 Proceedings of the 29th international conference on Software Engineering
ConcernLines: A timeline view of co-occurring concerns
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Codebook: discovering and exploiting relationships in software repositories
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Using information fragments to answer the questions developers ask
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Mashup environments in software engineering
Proceedings of the 1st Workshop on Web 2.0 for Software Engineering
Staying aware of relevant feeds in context
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Hard-to-answer questions about code
Evaluation and Usability of Programming Languages and Tools
Supporting software history exploration
Proceedings of the 8th Working Conference on Mining Software Repositories
History slicing: assisting code-evolution tasks
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Gerrit software code review data from Android
Proceedings of the 10th Working Conference on Mining Software Repositories
Degree-of-knowledge: Modeling a developer's knowledge of code
ACM Transactions on Software Engineering and Methodology (TOSEM)
Hi-index | 0.00 |
Software engineers working in large teams on large, long-lived code-bases have trouble understanding why the source code looks the way does. Often, they answer their questions by looking at past revisions of the source code, bug reports, code checkins, mailing list messages, and other documentation. This process of inquiry can be quite inefficient, especially when the answers they seek are located in isolated repositories accessed by multiple independent investigation tools. Prior mining approaches have focused on linking various data repositories together; in this paper we investigate techniques for displaying information extracted from the repositories in a way that helps developers to build a cohesive mental model of the rationale behind the code. After interviewing several developers and testers about how they investigate source code, we created a Visual Studio plugin called Deep Intellisense that summarizes and displays historical information about source code. We designed Deep Intellisense to address many of the hurdles engineers face with their current techniques, and help them spend less time gathering information and more time getting their work done.