JASPER: an Eclipse plug-in to facilitate software maintenance tasks

ABSTRACT

Recent research has shown that developers spend significant amounts of time navigating around code. Much of this time is spent on redundant navigations to code that the developer previously found. This is necessary today because existing development environments do not enable users to easily collect relevant information, such as web pages, textual notes, and code fragments. JASPER is a new system that allows users to collect relevant artifacts into a working set for easy reference. These artifacts are visible in a single view that represents the user's current task and allows users to easily make each artifact visible within its context. We predict that JASPER will significantly reduce time spent on redundant navigations. In addition, JASPER will facilitate multitasking, interruption management, and sharing task information with other developers.

REFERENCES

• 1: Coblenz, M. J. JASPER: Facilitating Software Maintenance Activities With Explicit Task Representations. M. S. Thesis. Technical Report CMU-CS-06-150, School of Computer Science, Carnegie Mellon University, Pittsburgh, PA. 2006.
• 2: Victor M. González , Gloria Mark, "Constant, constant, multi-tasking craziness": managing multiple working spheres, Proceedings of the SIGCHI conference on Human factors in computing systems, p.113-120, April 24-29, 2004, Vienna, Austria [doi>10.1145/985692.985707]
• 3: Doug Janzen , Kris De Volder, Navigating and querying code without getting lost, Proceedings of the 2nd international conference on Aspect-oriented software development, p.178-187, March 17-21, 2003, Boston, Massachusetts [doi>10.1145/643603.643622]
• 4: Mik Kersten , Gail C. Murphy, Mylar: a degree-of-interest model for IDEs, Proceedings of the 4th international conference on Aspect-oriented software development, p.159-168, March 14-18, 2005, Chicago, Illinois [doi>10.1145/1052898.1052912]
• 5: Ko, A. J., Myers, B. A., Coblenz, M. J., Aung, H. H. An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks. IEEE Transactions on Software Engineering, 33(12), December, 2006, to appear.
• 6: Perlow, L. The Time Famine: Toward a Sociology of Work Time, Administrative Science Quarterly, 44, 57--81, 1999.
• 7: Steven P. Reiss, The Desert environment, ACM Transactions on Software Engineering and Methodology (TOSEM), v.8 n.4, p.297-342, Oct. 1999 [doi>10.1145/322993.322994]
• 8: Martin P. Robillard , Gail C. Murphy, Representing concerns in source code, 2003
• 9: Martin P. Robillard , Wesley Coelho , Gail C. Murphy, How Effective Developers Investigate Source Code: An Exploratory Study, IEEE Transactions on Software Engineering, v.30 n.12, p.889-903, December 2004 [doi>10.1109/TSE.2004.101]
• 10: Robillard, M. P. and Murphy, G. C. Automatically Inferring Concern Code from Program Investigation Activities. In Proceedings of the 18th International Conference on Automated Software Engineering, 225--234, October 2003.
• 11: Martin P. Robillard , Frédéric Weigand-Warr, ConcernMapper: simple view-based separation of scattered concerns, Proceedings of the 2005 OOPSLA workshop on Eclipse technology eXchange, p.65-69, October 16-17, 2005, San Diego, California [doi>10.1145/1117696.1117710]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.6 Programming Environments

General Terms:
Design, Documentation, Human Factors

Keywords:
Eclipse, concerns, natural programming, programmer efficiency, programming environments