BibSLEIGH — Gerardo

Travelled to:

1 × Australia
1 × Croatia
1 × Cyprus
1 × India
1 × Korea
1 × Latvia
1 × Luxembourg
1 × Romania
1 × South Africa
1 × Sweden
1 × Switzerland
1 × United Kingdom
16 × USA
2 × Germany
2 × Hungary
2 × Ireland
3 × China
3 × Portugal
3 × The Netherlands
5 × France
6 × Canada
6 × Italy

Collaborated with:

M.D.Penta L.Cerulo A.Cimitile A.D.Lucia S.Panichella L.Aversano M.Tortorella C.A.Visaggio G.A.D.Lucca R.Oliveto L.Troiano G.Antoniol M.Ceccarelli A.R.Fasolino M.Munro D.Distante G.Bavota E.Zimeo G.Casazza G.D.Santo A.D.Sorbo H.C.Gall S.R.Tilley S.Stefanucci G.Frattolillo P.Tramontana R.Preziosi ∅ T.Bodhuin E.Merlo F.García M.Piattini A.Marcus E.Guzman A.Borriello F.Melillo G.Rossi D.Bovenzi V.F.Rollo G.Venturi J.Czeranski R.Koschke L.Mancini P.Antonini C.Vassallo G.D.Ruvo M.Cimitile F.Pacilio S.Huang P.Gallucci C.J.Taylor U.d.Carlini L.Sansone D.Falessi G.Cantone S.Giannantonio A.Bacchelli M.L.Bernardi J.Aponte C.D.Grosso R.Esposito N.Tsantalis L.Moreno A.Panichella F.Mercaldo M.D'Angelo A.Furno C.Manganelli Q.Zagarese I.Alshabani L.Pellegrino F.Baude C.V.Alexandru J.Shimagaki

Talks about:

code (18) studi (16) case (13) chang (11) softwar (10) develop (10) web (10) system (9) approach (8) legaci (8)

♂ Person: Gerardo Canfora

DBLP: Canfora:Gerardo

Facilitated 8 volumes:

PrCo

PrCo

PrCo

PrCh

GCh

PrCh

GCh

PrCh

Contributed to:

2015

2014

2013

2015

2012

2011

2010

2009

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1996

1995

1994

1993

2015

2016

2018

Wrote 85 papers:

ICSME-2015-PanichellaSGVCG #evolution #how #maintenance: How can i improve my app? Classifying user reviews for software maintenance and evolution (SP, ADS, EG, CAV, GC, HCG), pp. 281–290.
ASE-2014-BavotaPTPOC #recommendation #refactoring: Recommending refactorings based on team co-maintenance patterns (GB, SP, NT, MDP, RO, GC), pp. 337–342.
FSE-2014-MorenoBPOMC #automation #generative: Automatic generation of release notes (LM, GB, MDP, RO, AM, GC), pp. 484–495.
ICPC-2014-PanichellaCPO #empirical #evolution #how: How the evolution of emerging collaborations relates to code changes: an empirical study (SP, GC, MDP, RO), pp. 177–188.
ICPC-2014-VassalloPPC #developer #mining #named #source code: CODES: mining source code descriptions from developers discussions (CV, SP, MDP, GC), pp. 106–109.
ICSME-2014-PanichellaBPCA #developer #how: How Developers’ Collaborations Identified from Different Sources Tell Us about Code Changes (SP, GB, MDP, GC, GA), pp. 251–260.
CSMR-2013-BorrielloMC #android #architecture #migration #towards: Migrating Android Applications towards Service-centric Architectures with Sip2Share (AB, FM, GC), pp. 413–416.
ICSE-2013-AversanoCRT #approach: An approach for restructuring text content (LA, GC, GDR, MT), pp. 1225–1228.
ICSE-2013-CanforaPGOP #developer #named: YODA: young and newcomer developer assistant (GC, MDP, SG, RO, SP), pp. 1331–1334.
ICSM-2013-BavotaCPOP #documentation #empirical #maintenance: An Empirical Investigation on Documentation Usage Patterns in Maintenance Tasks (GB, GC, MDP, RO, SP), pp. 210–219.
ICSM-2013-BavotaCPOP13a #ecosystem #evolution: The Evolution of Project Inter-dependencies in a Software Ecosystem: The Case of Apache (GB, GC, MDP, RO, SP), pp. 280–289.
ICST-2013-CanforaLPOPP #fault #multi #predict: Multi-objective Cross-Project Defect Prediction (GC, ADL, MDP, RO, AP, SP), pp. 252–261.
ICST-2013-CanforaMVDFM #automation #case study #performance #smarttech #testing #user interface: A Case Study of Automating User Experience-Oriented Performance Testing on Smartphones (GC, FM, CAV, MD, AF, CM), pp. 66–69.
SAC-2013-ZagareseCZAPB #data-driven #interactive #performance: Efficient data-intensive event-driven interaction in SOA (QZ, GC, EZ, IA, LP, FB), pp. 1907–1912.
SCAM-2013-CeruloCPC #detection #markov: A Hidden Markov Model to detect coded information islands in free text (LC, MC, MDP, GC), pp. 157–166.
SCAM-J-2013-CeruloPBCC15 #detection #markov #named: Irish: A Hidden Markov Model to detect coded information islands in free text (LC, MDP, AB, MC, GC), pp. 26–43.
CSMR-2012-BernardiCLPD #communication #debugging #developer #eclipse: Do Developers Introduce Bugs When They Do Not Communicate? The Case of Eclipse and Mozilla (MLB, GC, GADL, MDP, DD), pp. 139–148.
FSE-2012-CanforaPOP #open source #question: Who is going to mentor newcomers in open source projects? (GC, MDP, RO, SP), p. 44.
ICPC-2012-PanichellaAPMC #developer #mining #source code: Mining source code descriptions from developer communications (SP, JA, MDP, AM, GC), pp. 63–72.
MSR-2011-CanforaCCP #debugging #interactive #social: Social interactions around cross-system bug fixings: the case of FreeBSD and OpenBSD (GC, LC, MC, MDP), pp. 143–152.
WCRE-2011-CanforaCCP #debugging #empirical #how: How Long Does a Bug Survive? An Empirical Study (GC, MC, LC, MDP), pp. 191–200.
ICPC-2010-CanforaCPP #case study: An Exploratory Study of Factors Influencing Change Entropy (GC, LC, MDP, FP), pp. 134–143.
ICSE-2010-CeccarelliCCP #approach #impact analysis: An eclectic approach for change impact analysis (MC, LC, GC, MDP), pp. 163–166.
ICSM-2010-CanforaCCP #detection #empirical #logic #multi #using: Using multivariate time series and association rules to detect logical change coupling: An empirical study (GC, MC, LC, MDP), pp. 1–10.
ICSE-2009-CanforaCP #difference #named: Ldiff: An enhanced line differencing tool (GC, LC, MDP), pp. 595–598.
ESEC-FSE-2007-AversanoCCGP #design pattern #empirical #evolution: An empirical study on the evolution of design patterns (LA, GC, LC, CDG, MDP), pp. 385–394.
MSR-2007-CanforaCP #identification #repository #source code: Identifying Changed Source Code Lines from Version Repositories (GC, LC, MDP), p. 14.
SAC-2007-DistanteRC #analysis #framework #modelling #process #web: Modeling business processes in web applications: an analysis framework (DD, GR, GC), pp. 1677–1682.
CSMR-2006-CanforaC #eclipse #impact analysis #named #plugin: Jimpa: An Eclipse Plug-in for Impact Analysis (GC, LC), pp. 341–342.
CSMR-2006-CanforaCVGP #design #empirical #evolution: Performances of Pair Designing on Software Evolution: a controlled experiment (GC, AC, CAV, FG, MP), pp. 197–205.
CSMR-2006-CanforaFFT #interactive #legacy #migration #web #web service: Migrating Interactive Legacy Systems To Web Services (GC, ARF, GF, PT), pp. 24–36.
CSMR-2006-CanforaFFT06a #flexibility #interactive #legacy #migration #web #web service: A Flexible Wrapper For The Migration Of Interactive Legacy System To Web Services (GC, ARF, GF, PT), pp. 347–344.
CSMR-2006-DistanteTC #approach #legacy #towards #web: Towards a Holistic Approach to Redesigning Legacy Applications for the Web with UWAT (DD, SRT, GC), pp. 295–299.
ICSE-2006-CanforaSZ #java: Developing and executing java AWT applications on limited devices with TCPTE (GC, GDS, EZ), pp. 787–790.
ICSE-2006-DistanteCTH #case study #legacy #web: Redesigning legacy applications for the web with UWAT+: a case study (DD, GC, SRT, SH), pp. 482–491.
ICSM-2006-CanforaCP #co-evolution #identification #on the #using: On the Use of Line Co-change for Identifying Crosscutting Concern Code (GC, LC, MDP), pp. 213–222.
MSR-2006-CanforaC #fine-grained #impact analysis #repository: Fine grained indexing of software repositories to support impact analysis (GC, LC), pp. 105–111.
MSR-2006-CanforaC06a #debugging #question: Where is bug resolution knowledge stored? (GC, LC), pp. 183–184.
SAC-2006-BodhuinCPT #complexity #physics: Hiding complexity and heterogeneity of the physical world in smart living environments (TB, GC, RP, MT), pp. 1921–1927.
SAC-2006-CanforaC #development #open source: Supporting change request assignment in open source development (GC, LC), pp. 1767–1772.
SEKE-2006-AversanoCV #named #web: WECAP: A Web Environment for Project Planning (LA, GC, CAV), pp. 591–594.
CSMR-2005-Canfora #testing #web #web service: User-Side Testing of Web Services (GC), p. 301.
SAC-2005-CanforaCGPV #education: Confirming the influence of educational background in pair-design knowledge through experiments (GC, AC, FG, MP, CAV), pp. 1478–1484.
WCRE-2005-CanforaP #architecture #testing: Architecting, Analyzing and Testing Service-Oriented Systems (GC, MDP), p. 237.
IWPC-2004-CanforaCV #design #empirical: Working in Pairs as a Means for Design Knowledge Building: An Empirical Study (GC, AC, CAV), pp. 62–69.
SAC-2004-AversanoBCET #approach #evolution #process #towards #using: Evolution of business processes towards eBusiness using a critiquing approach (LA, TB, GC, RE, MT), pp. 1351–1358.
SEKE-2004-CanforaCT #estimation #experience #fuzzy #linear: An Experience of Fuzzy Linear Regression applied to Effort Estimation (GC, LC, LT), pp. 57–61.
WCRE-2004-CanforaSZ #java #migration #towards: Toward Seamless Migration of Java AWT-Based Applications to Personal Wireless Devices (GC, GDS, EZ), pp. 38–47.
CSMR-2003-BovenziCF #legacy #web: Enabling Legacy System Accessibility by Web Heterogeneous Clients (DB, GC, ARF), pp. 73–81.
ICEIS-v1-2003-CanforaRV #impact analysis #integration: Business Change Impacts on System Integration (GC, VFR, GV), pp. 28–38.
ICEIS-v2-2003-CanforaT #assessment #risk management: Dealing with the “Don’t Know” Answer in Risk Assessment (GC, LT), pp. 229–237.
SEKE-2003-CanforaCPT #approach #case study #implementation: A Tool for Decision Support Implementing OFNWA Approach: A Case Study (GC, LC, RP, LT), pp. 714–720.
CSMR-2002-AversanoCLG #case study #documentation #tool support #using #web #workflow #xml: Integrating Document and Workflow Management Tools using XML and Web Technologies: A Case Study (LA, GC, ADL, PG), p. 24–?.
IWPC-2002-AversanoCLS #case study #comprehension #evolution #reuse: Evolving Ispell: A Case Study of Program Understanding for Reuse (LA, GC, ADL, SS), pp. 197–206.
SEKE-2002-AversanoC #modelling #process: Introducing eservices in business process models (LA, GC), pp. 481–488.
SEKE-2002-CanforaC #approach #visual notation #xml: A visual approach to define XML to FO transformations (GC, LC), pp. 563–570.
SEKE-2002-CanforaT #evaluation #nondeterminism #re-engineering #tool support: The importance of dealing with uncertainty in the evaluation of software engineering methods and tools (GC, LT), pp. 691–698.
CSMR-2001-AversanoCCL #case study #experience #legacy #migration #web: Migrating Legacy Systems to the Web: An Experience Report (LA, GC, AC, ADL), pp. 148–157.
IWPC-2001-AversanoCS #case study #comprehension #maintenance #process: Understanding and Improving the Maintenance Process: A Method and Two Case Studies (LA, GC, SS), pp. 199–208.
CSMR-2000-AntoniolCCL #case study #identification #maintenance #set: Identifying the Starting Impact Set of a Maintenance Request: A Case Study (GA, GC, GC, ADL), pp. 227–230.
ICSM-2000-AntoniolCCL #documentation #information retrieval #modelling #traceability: Information Retrieval Models for Recovering Traceability Links between Code and Documentation (GA, GC, GC, ADL), p. 40–?.
IWPC-2000-AntoniolCLCM #functional #object-oriented #requirements: Tracing Object-Oriented Code into Functional Requirements (GA, GC, ADL, GC, EM), pp. 79–86.
WCRE-2000-CanforaCK #approach #component: Revisiting the Delta IC Approach to Component Recovery (GC, JC, RK), pp. 140–149.
ICSM-1999-AntoniolCL #case study #evolution #maintenance #object-oriented #traceability: Maintaining Traceability During Object-Oriented Software Evolution: A Case Study (GA, GC, ADL), pp. 211–219.
IWPC-1999-CanforaCLL #approach #case study #identification: A Case Study of Applying an Eclectic Approach to Identify Objects in Code (GC, AC, ADL, GADL), pp. 136–143.
WCRE-1999-AntoniolCLM #documentation #object-oriented: Recovering Code to Documentation Links in OO Systems (GA, GC, ADL, EM), pp. 136–144.
IWPC-1998-CanforaCLL #legacy #migration #platform #source code #towards: Decomposing Legacy Programs: A First Step Towards Migrating to Client-Server Platforms (GC, AC, ADL, GADL), pp. 136–144.
ICSM-1996-CanforaCL #analysis #specification #tool support: Specifying code analysis tools (GC, AC, ADL), pp. 95–103.
SEKE-1996-CanforaCL #cobol #concept: Recovering a Conceptual Data Model from COBOL Code (GC, AC, GADL), pp. 277–284.
SEKE-1996-CanforaLM #c #ide #re-engineering #reuse: An Integrated Environment for Reuse Reengineering C Code (GC, ADL, MM), pp. 214–221.
WPC-1996-CanforaMT #comprehension #maintenance: A Workbench for Program Comprehension during Software Maintenance (GC, LM, MT), pp. 30–39.
ICSM-1995-CanforaC #algorithm #dependence #graph: Algorithms for program dependence graph production (GC, AC), p. 157–?.
ICSM-1995-CanforaFT #process #re-engineering #reuse #towards: Towards reengineering in reuse reengineering processes (GC, ARF, MT), pp. 147–156.
SEKE-1995-CanforaCT #maintenance #prolog: Prolog for Software Maintenance (GC, AC, MT), pp. 478–486.
ICSM-1994-AntoniniCC #case study #experience #legacy #quality #re-engineering #requirements: Reengineering Legacy Systems to Meet Quality Requirements: An Experience Report (PA, GC, AC), pp. 146–153.
ICSM-1994-CanforaCLL: Software Salvaging Based on Conditions (GC, AC, ADL, GADL), pp. 424–433.
ICSM-1994-CanforaCTM #data type #identification #precise #reuse: A Precise Method for Identifying Reusable Abstract Data Types in Code (GC, AC, MT, MM), pp. 404–413.
SEKE-1994-CanforaLT #inheritance: Recovering object classes and inheritance relationships from existing code (GC, GADL, MT), pp. 233–240.
CSM-1993-CanforaCMT #c #case study #data type #source code: Extracting Abstract Data Types from C Programs: A Case Study (GC, AC, MM, CJT), pp. 200–209.
SEKE-1993-CanforaCCS #ada #animation #interactive #reverse engineering #source code: Reverse Engineering and Interactive Animation of Ada Programs (GC, AC, UdC, LS), pp. 507–516.
WCRE-1993-CanforaCM #data type #identification #reuse #reverse engineering: A Reverse Engineering Method for Identifying Reusable Abstract Data Types (GC, AC, MM), pp. 73–82.
ASE-2015-SorboPVPCG #developer #development #email #mining: Development Emails Content Analyzer: Intention Mining in Developer Discussions (T) (ADS, SP, CAV, MDP, GC, HCG), pp. 12–23.
FSE-2016-PanichellaSGVCG #classification #development #named: ARdoc: app reviews development oriented classifier (SP, ADS, EG, CAV, GC, HCG), pp. 1023–1027.
FSE-2016-SorboPASVCG #recommendation #what: What would users change in my app? summarizing app reviews for recommending software changes (ADS, SP, CVA, JS, CAV, GC, HCG), pp. 499–510.
ASE-2018-FalessiPCC #traceability: Estimating the number of remaining links in traceability recovery (journal-first abstract) (DF, MDP, GC, GC), p. 953.