Travelled to:1 × Austria
1 × Croatia
1 × India
1 × Italy
1 × Japan
1 × Portugal
1 × South Africa
1 × United Kingdom
11 × Canada
2 × France
2 × Germany
21 × USA
3 × China
Collaborated with:∅ M.P.Robillard T.Fritz S.Rastkar R.J.Walker D.Cubranic D.Notkin E.R.Murphy-Hill M.Kersten E.L.A.Baniassad R.Holmes A.W.J.Bradley B.d.Alwis J.Anvik A.Lai R.Jiresal T.Zimmermann M.Kamimura A.Zeller S.Minto M.Palyart X.Blanc N.Sawadsky A.Kuhn C.A.Thompson G.Murray P.Viriyakattiyaporn D.C.Shepherd E.Hill J.Sillito K.D.Volder L.Hiew C.Schwanninger E.S.Lan K.J.Sullivan E.M.Huang A.N.Meyer J.Ou R.A.Bittencourt G.J.d.S.Santos D.D.S.Guerrero M.Kim V.Sazawal J.Singer K.S.Booth A.Chan A.T.T.Ying M.Foucault J.Falleri J.Brunet R.Terra J.C.A.d.Figueiredo D.S.Guerrero B.N.Freeman-Benson D.Wright D.Swanson J.Isaak G.Kiczales J.Lamping C.V.Lopes C.Maeda A.Mendhekar
Talks about:softwar (18) develop (13) code (10) studi (9) sourc (9) use (9) program (8) model (8) recommend (7) concern (6)
♀ Person: Gail C. Murphy
DBLP: Murphy:Gail_C=
Facilitated 9 volumes:
Ed
PrCo
EdPrChPrCo
EdPrChPrCoPrCoContributed to:
2015
2015
2014201420142014
201320132013201220122011
20112011
201120112010
2010200920092008200720072007200720062006
2005200520052004
2004
20032003
200320032002200220012000
19991999
199919981998199719961995
19912018Wrote 61 papers:
- ESEC-FSE-2015-FoucaultPBMF #developer #open source #quality
- Impact of developer turnover on quality in open-source software (MF, MP, XB, GCM, JRF), pp. 829–841.
- MoDELS-2015-Murphy
- Software supply chains (GCM), p. 2.
- CHI-2014-FritzHMZ #case study #persuasion #process #using
- Persuasive technology in the real world: a study of long-term use of activity sensing devices for fitness (TF, EMH, GCM, TZ), pp. 487–496.
- FSE-2014-MeyerFMZ #developer
- Software developers’ perceptions of productivity (ANM, TF, GCM, TZ), pp. 19–29.
- FSE-2014-PalyartMMB
- Speculative reprogramming (MP, GCM, ERMH, XB), pp. 837–840.
- MSR-2014-BrunetMTFG #design #developer #question
- Do developers discuss design? (JB, GCM, RT, JCAdF, DSG), pp. 340–343.
- Onward-2014-Murphy #development
- Getting to Flow in Software Development (GCM), pp. 269–281.
- ICPC-2013-KamimuraM #generative #summary #testing #towards
- Towards generating human-oriented summaries of unit test cases (MK, GCM), pp. 215–218.
- ICSE-2013-RastkarM #question #why
- Why did this code change? (SR, GCM), pp. 1193–1196.
- ICSE-2013-SawadskyMJ #named #recommendation #web
- Reverb: recommending code-related web pages (NS, GCM, RJ), pp. 812–821.
- MSR-2013-Murphy #development #question #what
- What is software development productivity, anyway? (GCM), p. 1.
- FSE-2012-Murphy-HillJM #developer #development #recommendation
- Improving software developers’ fluency by recommending development environment commands (ERMH, RJ, GCM), p. 42.
- MoDELS-2012-KuhnMT #case study #development #modelling #scalability
- An Exploratory Study of Forces and Frictions Affecting Large-Scale Model-Driven Development (AK, GCM, CAT), pp. 352–367.
- CHI-2011-FritzM #developer #how
- Determining relevancy: how software developers determine relevant information in feeds (TF, GCM), pp. 1827–1830.
- CSCW-2011-Murphy-HillM #effectiveness #interactive #tool support
- Peer interaction effectively, yet infrequently, enables programmers to discover new tools (ERMH, GCM), pp. 405–414.
- ICSE-2011-MurphyZ
- ICSE 2011 technical briefings (GCM, AZ), pp. 1072–1073.
- ICSM-2011-RastkarMB #generative #natural language #source code #summary
- Generating natural language summaries for crosscutting source code concerns (SR, GCM, AWJB), pp. 103–112.
- MSR-2011-BradleyM
- Supporting software history exploration (AWJB, GCM), pp. 193–202.
- ICSE-2010-FritzM #developer #using
- Using information fragments to answer the questions developers ask (TF, GCM), pp. 175–184.
- ICSE-2010-FritzOMM #source code
- A degree-of-knowledge model to capture source code familiarity (TF, JO, GCM, ERMH), pp. 385–394.
- ICSE-2010-RastkarMM #case study #debugging
- Summarizing software artifacts: a case study of bug reports (SR, GCM, GM), pp. 505–514.
- WCRE-2010-BittencourtSGM #automation #information retrieval #modelling #using
- Improving Automated Mapping in Reflexion Models Using Information Retrieval Techniques (RAB, GJdSS, DDSG, GCM), pp. 163–172.
- ICPC-2009-MurphyVS #behaviour #process #programming #using
- Using activity traces to characterize programming behaviour beyond the lab (GCM, PV, DCS), pp. 90–94.
- MSR-2009-RastkarM #interactive #on the #question #recommendation #what
- On what basis to recommend: Changesets or interactions? (SR, GCM), pp. 155–158.
- ICSE-2008-AlwisM #concept #query
- Answering conceptual queries with Ferret (BdA, GCM), pp. 21–30.
- ESEC-FSE-2007-FritzMH #process #question
- Does a programmer’s activity indicate knowledge of code? (TF, GCM, EH), pp. 341–350.
- ICPC-2007-AlwisMR #case study #comparative #tool support
- A Comparative Study of Three Program Exploration Tools (BdA, GCM, MPR), pp. 103–112.
- ICSM-2007-Murphy #named
- Houston: We are in Overload (GCM), p. 1.
- MSR-2007-AnvikM #debugging #implementation
- Determining Implementation Expertise from Bug Reports (JA, GCM), p. 2.
- MSR-2007-MintoM #recommendation
- Recommending Emergent Teams (SM, GCM), p. 5.
- FSE-2006-KerstenM #using
- Using task context to improve programmer productivity (MK, GCM), pp. 1–11.
- FSE-2006-SillitoMV #evolution
- Questions programmers ask during software evolution tasks (JS, GCM, KDV), pp. 23–34.
- ICSE-2006-AnvikHM #debugging #question
- Who should fix this bug? (JA, LH, GCM), pp. 361–370.
- ECOOP-2005-MurphyKRC #development
- The Emergent Structure of Development Tasks (GCM, MK, MPR, DC), pp. 33–48.
- ESEC-FSE-2005-HolmesWM #recommendation
- Strathcona example recommendation tool (RH, RJW, GCM), pp. 237–240.
- ESEC-FSE-2005-KimSN #empirical
- An empirical study of code clone genealogies (MK, VS, DN, GCM), pp. 187–196.
- ICSE-2005-HolmesM #recommendation #source code #using
- Using structural context to recommend source code examples (RH, GCM), pp. 117–125.
- CSCW-2004-CubranicMSB #case study #development #learning
- Learning from project history: a case study for software development (DC, GCM, JS, KSB), pp. 82–91.
- SEKE-2004-CubraniM #automation #categorisation #debugging #using
- Automatic bug triage using text categorization (DC, GCM), pp. 92–97.
- ASE-2003-RobillardM #automation #process
- Automatically Inferring Concern Code from Program Investigation Activities (MPR, GCM), pp. 225–235.
- ICSE-2003-BaniassadMS #design pattern #graph
- Design Pattern Rationale Graphs: Linking Design to Source (ELAB, GCM, CS), pp. 352–362.
- ICSE-2003-CubranicM #development #named #recommendation
- Hipikat: Recommending Pertinent Software Development Artifacts (DC, GCM), pp. 408–418.
- ICSE-2003-RobillardM #source code
- FEAT. A Tool for Locating, Describing, and Analyzing Concerns in Source Code (MPR, GCM), pp. 822–823.
- IWPC-2003-ChanHMY #execution #object-oriented #scalability #visualisation
- Scaling an Object-Oriented System Execution Visualizer through Sampling (AC, RH, GCM, ATTY), pp. 237–244.
- WCRE-2003-Murphy #learning
- Learning from the Past (GCM), pp. 2–3.
- ICSE-2002-RobillardM #dependence #graph #using
- Concern graphs: finding and describing concerns using structural program dependencies (MPR, GCM), pp. 406–416.
- ICSM-2002-LaiM #behaviour #modelling
- Behavioural Concern Modelling for Software Change Tasks (AL, GCM), pp. 112–121.
- ICSE-2001-MurphyLWR #case study #source code
- Separating Features in Source Code: An Exploratory Study (GCM, AL, RJW, MPR), pp. 275–284.
- FSE-2000-RobillardM #design #exception #java #robust #source code
- Designing robust Java programs with exceptions (MPR, GCM), pp. 2–10.
- FSE-2000-WalkerM #evolution #reuse
- Implicit context: easing software evolution and reuse (RJW, GCM), pp. 69–78.
- ESEC-FSE-1999-RobillardM #exception #java #source code
- Analyzing Exception Flow in Java Programs (MPR, GCM), pp. 322–327.
- ICSE-1999-WalkerBM #aspect-oriented #assessment #programming
- An Initial Assessment of Aspect-Oriented Programming (RJW, ELAB, GCM), pp. 120–130.
- OOPSLA-1999-KerstenM #aspect-oriented #case study #learning #named #programming #using
- Atlas: A Case Study in Building a Web-Based Learning Environment using Aspect-oriented Programming (MK, GCM), pp. 340–352.
- ICSE-1998-BaniassadM #concept #query #re-engineering
- Conceptual Module Querying for Software Reengineering (ELAB, GCM), pp. 64–73.
- OOPSLA-1998-WalkerMFWSI #modelling #visualisation
- Visualizing Dynamic Software System Information Through High-Level Models (RJW, GCM, BNFB, DW, DS, JI), pp. 271–283.
- ICSE-1997-KiczalesLLMMM #design #guidelines #implementation
- Open Implementation Design Guidelines (GK, JL, CVL, CM, AM, GCM), pp. 481–490.
- ICSE-1996-MurphyNL #empirical #graph
- An Empirical Study of Static Call Graph Extractors (GCM, DN, ESCL), pp. 90–99.
- FSE-1995-MurphyN #lightweight
- Lightweight Source Model Extraction (GCM, DN), pp. 116–127.
- FSE-1995-MurphyNS #modelling
- Software Reflexion Models: Bridging the Gap Between Source and High-Level Models (GCM, DN, KJS), pp. 18–28.
- TOOLS-USA-1991-Murphy #analysis #case study #experience #object-oriented
- Experiences in Applying Object-Oriented Analysis (GCM), pp. 249–264.
- ASE-2018-Murphy #re-engineering
- The need for context in software engineering (IEEE CS Harlan Mills award keynote) (GCM), p. 5.