Designing documentation to compensate for delocalized plans
Communications of the ACM
Concern graphs: finding and describing concerns using structural program dependencies
Proceedings of the 24th International Conference on Software Engineering
Navigating and querying code without getting lost
Proceedings of the 2nd international conference on Aspect-oriented software development
How Do Program Understanding Tools Affect How Programmers Understand Programs
WCRE '97 Proceedings of the Fourth Working Conference on Reverse Engineering (WCRE '97)
WPC '97 Proceedings of the 5th International Workshop on Program Comprehension (WPC '97)
Manipulating and documenting software structures using SHriMP views
ICSM '95 Proceedings of the International Conference on Software Maintenance
The perfect search engine is not enough: a study of orienteering behavior in directed search
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Proceedings of the 27th international conference on Software engineering
Software psychology: Human factors in computer and information systems (Winthrop computer systems series)
Building an Ecologically valid, Large-scale Diagram to Help Developers Stay Oriented in Their Code
VLHCC '07 Proceedings of the IEEE Symposium on Visual Languages and Human-Centric Computing
Hi-index | 0.00 |
As software systems grow in size and use more third-party libraries and frameworks, the need for developers to understand unfamiliar large codebases is rapidly increasing. In this paper, we present a tool, Relo, that supports developers' understanding by allowing interactive exploration of code. As the developer explores relationships found in the code, Relo builds and automatically manages the context in a visualization, thereby helping build the developer's mental representation of the code. Developers can group viewed artifacts or use the viewed items to ask Relo for further exploration suggestions. Relo is built as an Eclipse plug-in integrated into the Java Tooling (JDT), and uses a standard, RDF, based backend allowing for maintaining code relationships and performing inferences about the relationships.