2009 | ||
---|---|---|
83 | EE | Gail C. Murphy: Everyday aspects. AOSD 2009: 229-230 |
2008 | ||
82 | Mary Jean Harrold, Gail C. Murphy: Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering, 2008, Atlanta, Georgia, USA, November 9-14, 2008 ACM 2008 | |
81 | EE | Brian de Alwis, Gail C. Murphy, Shawn Minto: Creating a cognitive metric of programming task difficulty. CHASE 2008: 29-32 |
80 | EE | David Shepherd, Gail C. Murphy: A sketch of the programmer's coach: making programmers more effective. CHASE 2008: 97-100 |
79 | EE | Brian de Alwis, Gail C. Murphy: Answering conceptual queries with Ferret. ICSE 2008: 21-30 |
78 | EE | Seonah Lee, Gail C. Murphy, Thomas Fritz, Meghan Allen: How can diagramming tools help support programming activities? VL/HCC 2008: 246-249 |
77 | EE | Jonathan Sillito, Gail C. Murphy, Kris De Volder: Asking and Answering Questions during a Programming Change Task. IEEE Trans. Software Eng. 34(4): 434-451 (2008) |
76 | EE | Marc Eaddy, Thomas Zimmermann, Kaitin D. Sherwood, Vibhav Garg, Gail C. Murphy, Nachiappan Nagappan, Alfred V. Aho: Do Crosscutting Concerns Cause Defects? IEEE Trans. Software Eng. 34(4): 497-515 (2008) |
2007 | ||
75 | EE | Izzet Safer, Gail C. Murphy: Comparing episodic and semantic interfaces for task boundary identification. CASCON 2007: 229-243 |
74 | EE | Thomas Fritz, Gail C. Murphy, Emily Hill: Does a programmer's activity indicate knowledge of code? ESEC/SIGSOFT FSE 2007: 341-350 |
73 | EE | Brian de Alwis, Gail C. Murphy, Martin P. Robillard: A Comparative Study of Three Program Exploration Tools. ICPC 2007: 103-112 |
72 | EE | Gail C. Murphy: Houston: We are in Overload. ICSM 2007: 1 |
71 | EE | John Anvik, Gail C. Murphy: Determining Implementation Expertise from Bug Reports. MSR 2007: 2 |
70 | EE | Shawn Minto, Gail C. Murphy: Recommending Emergent Teams. MSR 2007: 5 |
69 | EE | Wesley Coelho, Gail C. Murphy: ClassCompass: A software design mentoring system. ACM Journal of Educational Resources in Computing 7(1): (2007) |
68 | EE | Martin P. Robillard, Gail C. Murphy: Representing concerns in source code. ACM Trans. Softw. Eng. Methodol. 16(1): (2007) |
2006 | ||
67 | EE | Wesley Coelho, Gail C. Murphy: Presenting crosscutting structure with active models. AOSD 2006: 158-168 |
66 | EE | Izzet Safer, Gail C. Murphy, Julie Waterhouse, Jin Li: A focused learning environment for Eclipse. ETX 2006: 75-79 |
65 | EE | John Anvik, Lyndon Hiew, Gail C. Murphy: Who should fix this bug? ICSE 2006: 361-370 |
64 | EE | Mik Kersten, Gail C. Murphy: Using task context to improve programmer productivity. SIGSOFT FSE 2006: 1-11 |
63 | EE | Jonathan Sillito, Gail C. Murphy, Kris De Volder: Questions programmers ask during software evolution tasks. SIGSOFT FSE 2006: 23-34 |
62 | EE | Brian de Alwis, Gail C. Murphy: Using Visual Momentum to Explain Disorientation in the Eclipse IDE. VL/HCC 2006: 51-54 |
61 | EE | Gail C. Murphy, Christa Schwanninger: Guest Editors' Introduction: Aspect-Oriented Programming. IEEE Software 23(1): 20-23 (2006) |
60 | EE | Gail C. Murphy, Mik Kersten, Leah Findlater: How Are Java Software Developers Using the Eclipse IDE? IEEE Software 23(4): 76-83 (2006) |
59 | EE | Reid Holmes, Robert J. Walker, Gail C. Murphy: Approximate Structural Context Matching: An Approach to Recommend Relevant Examples. IEEE Trans. Software Eng. 32(12): 952-970 (2006) |
2005 | ||
58 | EE | Jan Hannemann, Gail C. Murphy, Gregor Kiczales: Role-based refactoring of crosscutting concerns. AOSD 2005: 135-146 |
57 | EE | Mik Kersten, Gail C. Murphy: Mylar: a degree-of-interest model for IDEs. AOSD 2005: 159-168 |
56 | EE | Gail C. Murphy, Mik Kersten, Martin P. Robillard, Davor Cubranic: The Emergent Structure of Development Tasks. ECOOP 2005: 33-48 |
55 | EE | Miryung Kim, Vibha Sazawal, David Notkin, Gail C. Murphy: An empirical study of code clone genealogies. ESEC/SIGSOFT FSE 2005: 187-196 |
54 | EE | Reid Holmes, Robert J. Walker, Gail C. Murphy: Strathcona example recommendation tool. ESEC/SIGSOFT FSE 2005: 237-240 |
53 | EE | John Anvik, Lyndon Hiew, Gail C. Murphy: Coping with an open bug repository. ETX 2005: 35-39 |
52 | EE | Reid Holmes, Gail C. Murphy: Using structural context to recommend source code examples. ICSE 2005: 117-125 |
51 | EE | Jonathan Sillito, Kris De Volder, Brian Fisher, Gail C. Murphy: Managing software change tasks: an exploratory study. ISESE 2005: 23-32 |
50 | EE | Martin P. Robillard, Gail C. Murphy: Just-in-time concern modeling. ACM SIGSOFT Software Engineering Notes 30(4): 1-3 (2005) |
49 | EE | Wesley Coelho, Gail C. Murphy: ActiveAspect: presenting crosscutting structure. ACM SIGSOFT Software Engineering Notes 30(4): 1-4 (2005) |
48 | EE | Davor Cubranic, Gail C. Murphy, Janice Singer, Kellogg S. Booth: Hipikat: A Project Memory for Software Development. IEEE Trans. Software Eng. 31(6): 446-465 (2005) |
2004 | ||
47 | Gail C. Murphy, Karl J. Lieberherr: Proceedings of the 3rd International Conference on Aspect-Oriented Software Development, AOSD 2004, Lancaster, UK, March 22-24, 2004 ACM 2004 | |
46 | EE | Davor Cubranic, Gail C. Murphy, Janice Singer, Kellogg S. Booth: Learning from project history: a case study for software development. CSCW 2004: 82-91 |
45 | Davor Cubranic, Gail C. Murphy: Automatic bug triage using text categorization. SEKE 2004: 92-97 | |
44 | EE | Martin P. Robillard, Wesley Coelho, Gail C. Murphy: How Effective Developers Investigate Source Code: An Exploratory Study. IEEE Trans. Software Eng. 30(12): 889-903 (2004) |
43 | EE | Annie T. T. Ying, Gail C. Murphy, Raymond T. Ng, Mark Chu-Carroll: Predicting Source Code Changes by Mining Change History. IEEE Trans. Software Eng. 30(9): 574-586 (2004) |
2003 | ||
42 | EE | Martin P. Robillard, Gail C. Murphy: Automatically Inferring Concern Code from Program Investigation Activities. ASE 2003: 225-235 |
41 | EE | Elisa L. A. Baniassad, Gail C. Murphy, Christa Schwanninger: Design Pattern Rationale Graphs: Linking Design to Source. ICSE 2003: 352-362 |
40 | EE | Davor Cubranic, Gail C. Murphy: Hipikat: Recommending Pertinent Software Development Artifacts. ICSE 2003: 408-418 |
39 | EE | Martin P. Robillard, Gail C. Murphy: FEAT. A Tool for Locating, Describing, and Analyzing Concerns in Source Code. ICSE 2003: 822-823 |
38 | EE | Andrew Chan, Reid Holmes, Gail C. Murphy, Annie T. T. Ying: Scaling an Object-Oriented System Execution Visualizer through Sampling. IWPC 2003: 237-244 |
37 | EE | Jan Hannemann, Thomas Fritz, Gail C. Murphy: Refactoring to aspects: an interactive approach. OOPSLA Workshop on Eclipse Technology eXchange 2003: 74-78 |
36 | EE | Gail C. Murphy: Learning from the Past. WCRE 2003: 2-3 |
35 | EE | Martin P. Robillard, Gail C. Murphy: Static analysis to support the evolution of exception structure in object-oriented systems. ACM Trans. Softw. Eng. Methodol. 12(2): 191-221 (2003) |
2002 | ||
34 | EE | Avi Bryant, Andrew Catton, Kris De Volder, Gail C. Murphy: Explicit programming. AOSD 2002: 10-18 |
33 | EE | Elisa L. A. Baniassad, Gail C. Murphy, Christa Schwanninger, Michael Kircher: Managing crosscutting concerns during software evolution tasks: an inquisitive study. AOSD 2002: 120-126 |
32 | EE | Martin P. Robillard, Gail C. Murphy: Concern graphs: finding and describing concerns using structural program dependencies. ICSE 2002: 406-416 |
31 | EE | Albert Lai, Gail C. Murphy: Behavioural Concern Modelling for Software Change Tasks. ICSM 2002: 112-121 |
2001 | ||
30 | Gail C. Murphy, Albert Lai, Robert J. Walker, Martin P. Robillard: Separating Features in Source Code: An Exploratory Study. ICSE 2001: 275-284 | |
29 | Gail C. Murphy, Robert J. Walker, Elisa L. A. Baniassad, Martin P. Robillard, Albert Lai, Mik Kersten: Does aspect-oriented programming work? Commun. ACM 44(10): 75-77 (2001) | |
28 | EE | Gail C. Murphy, David Notkin, Kevin J. Sullivan: Software Reflexion Models: Bridging the Gap between Design and Implementation. IEEE Trans. Software Eng. 27(4): 364-380 (2001) |
2000 | ||
27 | EE | Robert J. Walker, Gail C. Murphy, Jeffrey Steinbok, Martin P. Robillard: Efficient mapping of software system traces to architectural views. CASCON 2000: 12 |
26 | EE | Antonia Bertolino, Gail C. Murphy: An overview of the ICSE 2000 workshop program. ICSE 2000: 793 |
25 | EE | Martin P. Robillard, Gail C. Murphy: Designing robust Java programs with exceptions. SIGSOFT FSE 2000: 2-10 |
24 | EE | Robert J. Walker, Gail C. Murphy: Implicit context: easing software evolution and reuse. SIGSOFT FSE 2000: 69-78 |
1999 | ||
23 | EE | Martin P. Robillard, Gail C. Murphy: Analyzing Exception Flow in Java Programs. ESEC / SIGSOFT FSE 1999: 322-327 |
22 | EE | Robert J. Walker, Elisa L. A. Baniassad, Gail C. Murphy: An Initial Assessment of Aspect-Oriented Programming. ICSE 1999: 120-130 |
21 | EE | Mik Kersten, Gail C. Murphy: Atlas: A Case Study in Building a Web-Based Learning Environment using Aspect-oriented Programming. OOPSLA 1999: 340-352 |
20 | EE | Gail C. Murphy, Robert J. Walker, Elisa L. A. Baniassad: Evaluating Emerging Software Development Technologies: Lessons Learned from Assessing Aspect-Oriented Programming. IEEE Trans. Software Eng. 25(4): 438-455 (1999) |
1998 | ||
19 | EE | Robert J. Walker, Elisa L. A. Baniassad, Gail C. Murphy: Assessing Aspect-Oriented Programming: Preliminary Results. ECOOP Workshops 1998: 433-434 |
18 | Elisa L. A. Baniassad, Gail C. Murphy: Conceptual Module Querying for Software Reengineering. ICSE 1998: 64-73 | |
17 | EE | Robert J. Walker, Gail C. Murphy, Bjørn N. Freeman-Benson, Darin Wright, Darin Swanson, Jeremy Isaak: Visualizing Dynamic Software System Information Through High-Level Models. OOPSLA 1998: 271-283 |
16 | EE | Gail C. Murphy, Ekaterina Saenko: Predicting memory use from a class diagram using dynamic information. WOSP 1998: 145-151 |
15 | EE | Gail C. Murphy, David Notkin, William G. Griswold, Erica S.-C. Lan: An Empirical Study of Static Call Graph Extractors. ACM Trans. Softw. Eng. Methodol. 7(2): 158-191 (1998) |
1997 | ||
14 | EE | Gregor Kiczales, John Lamping, Cristina Videira Lopes, Chris Maeda, Anurag Mendhekar, Gail C. Murphy: Open Implementation Design Guidelines. ICSE 1997: 481-490 |
13 | EE | Chris Maeda, Arthur Lee, Gail C. Murphy, Gregor Kiczales: Open Implementation Analysis and Design. SSR 1997: 44-52 |
12 | Gail C. Murphy, David Notkin: Reengineering with Reflection Models: A Case Study. IEEE Computer 30(8): 29-36 (1997) | |
1996 | ||
11 | EE | Gail C. Murphy, David Notkin, Erica S.-C. Lan: An Empirical Study of Static Call Graph Extractors. ICSE 1996: 90-99 |
10 | EE | Gail C. Murphy, David Notkin: Lightweight Lexical Source Model Extraction. ACM Trans. Softw. Eng. Methodol. 5(3): 262-292 (1996) |
9 | EE | Gail C. Murphy, David Notkin: On the use of static typing to support operations on frameworks. Object Oriented Systems 3: 197-213 (1996) |
1995 | ||
8 | EE | Gail C. Murphy, David Notkin: Lightweight Source Model Extraction. SIGSOFT FSE 1995: 116-127 |
7 | EE | Gail C. Murphy, David Notkin, Kevin J. Sullivan: Software Reflexion Models: Bridging the Gap Between Source and High-Level Models. SIGSOFT FSE 1995: 18-28 |
1994 | ||
6 | Gail C. Murphy, Paul Townsend, Pok Sze Wong: Experiences with Cluster and Class Testing. Commun. ACM 37(9): 39-47 (1994) | |
1993 | ||
5 | Gail C. Murphy, David Notkin: Difficulties with Object-Oriented Frameworks. ICSE Workshop on Studies of Software Design 1993: 77-87 | |
4 | Michel Fortier, Gail C. Murphy: An object-oriented hypermedia framework for command and control information system. OOPS Messenger 4(2): 135-137 (1993) | |
3 | Gail C. Murphy, Pok Sze Wong: Towards a testing methodology for object-oriented systems. OOPS Messenger 4(2): 139-140 (1993) | |
2 | Paul Townsend, Gail C. Murphy: Objects in the life-cycle. OOPS Messenger 4(2): 25-28 (1993) | |
1991 | ||
1 | Gail C. Murphy: Experiences in Applying Object-Oriented Analysis. TOOLS (5) 1991: 249-264 |