NDLI: How we refactor, and how we know it

Please wait, while we are loading the content...

ICSE 2009 CONFERENCE ORGANIZATION

lCSE 2009 SPONSORS AND SUPPORTERS

Predicting build failures using social network analysis on developer communication

How tagging helps bridge the gap between social and technical aspects in software development

Tesseract: Interactive visual exploration of socio-technical relationships in software development

HOLMES: Effective statistical debugging via efficient path profiling

Taming coincidental correctness: Coverage refinement with context patterns to improve fault localization

Lightweight fault-localization using multiple coverage types

Succession: Measuring transfer of code and developer productivity

Predicting faults using the complexity of code changes

A case-study on using an Automated In-process Software Engineering Measurement and Analysis system in an industrial environment

Using quantitative analysis to implement autonomic IT systems

Model evolution by run-time parameter adaptation

Taming Dynamically Adaptive Systems using models and aspects

Accurate Interprocedural Null-Dereference Analysis for Java

The road not taken: Estimating path execution frequency statically

Automatic dimension inference and checking for object-oriented programs

In-field healing of integration problems with COTS components

Modular string-sensitive permission analysis with demand-driven precision

License integration patterns: Addressing license mismatches in component-based development

Automatic creation of SQL Injection and cross-site scripting attacks

Invariant-based automatic testing of AJAX user interfaces

FEATUREHOUSE: Language-independent, automated software composition

Automatically capturing source code context of NL-queries for software maintenance and reuse

Semantics-based code search

Reasoning about edits to feature models

Learning operational requirements from goal models

Complete and accurate clone detection in graph-based models

How we refactor, and how we know it

The secret life of bugs: Going past the errors and omissions in software repositories

Discovering and representing systematic code changes

Improving API documentation usability with knowledge pushing

Listening to programmers Taxonomies and characteristics of comments in operating system code

Equality and hashing for (almost) free: Generating implementations from abstraction functions

Locating need-to-translate constant strings for software internationalization

Automatically finding patches using genetic programming

FlexSync: An aspect-oriented approach to Java synchronization

Effective static deadlock detection

Refactoring sequential Java code for concurrency via concurrent libraries

Maintaining and evolving GUI-directed test scripts

MINTS: A general framework and tool for supporting test-suite minimization

Synthesizing intensional behavior models by graph transformation

Analyzing critical process models through behavior model synthesis

Validation of contracts using enabledness preserving finite state abstractions

WISE: Automated test generation for worst-case complexity

Taint-based directed whitebox fuzzing

Do code clones matter?

Mining exception-handling rules as sequence association rules

Safe-commit analysis to facilitate team software development

Does distributed development affect software quality? An empirical case study of Windows Vista

The impact of process choice in high maturity environments: An empirical analysis

How to avoid drastic software process change (using stochastic stability)

UEMan: A tool to manage user evaluation in development environments

TranStrL: An automatic need-to-translate string locator for software internationalization

SmartTutor: Creating IDE-based interactive tutorials via editable replay

A toolset for automated failure analysis

JUnitMX - A change-aware unit testing tool

CocoViz with ambient audio software exploration

ConcernLines: A timeline view of co-occurring concerns

Alitheia Core: An extensible software quality monitoring platform

VIDA: Visual interactive debugging

Feedback-driven requirements engineering: The Heuristic Requirements Assistant

Ævol: A tool for defining and planning architecture evolution

Ldiff: An enhanced line differencing tool

SemDiff: Analysis and recommendation support for API evolution

CloneDetective - A workbench for clone detection research

Save-IDE - A tool for design, analysis and implementation of component-based embedded systems

FeatureIDE: A tool framework for feature-oriented software development

Synthesis of timed behavior from scenarios in the Fujaba Real-Time Tool Suite

ContextServ: A platform for rapid and flexible development of context-aware Web services

ReMan: A pro-active reputation management infrastructure for composite Web services

ITACA: An integrated toolbox for the automatic composition and adaptation of Web services

How we refactor, and how we know it

Content Provider	ACM Digital Library
Author	Murphy-Hill, Emerson Parnin, Chris Black, Andrew P.
Abstract	Much of what we know about how programmers refactor in the wild is based on studies that examine just a few software projects. Researchers have rarely taken the time to replicate these studies in other contexts or to examine the assumptions on which they are based. To help put refactoring research on a sound scientific basis, we draw conclusions using four data sets spanning more than 13 000 developers, 240 000 tool-assisted refactorings, 2500 developer hours, and 3400 version control commits. Using these data, we cast doubt on several previously stated assumptions about how programmers refactor, while validating others. For example, we find that programmers frequently do not indicate refactoring activity in commit logs, which contradicts assumptions made by several previous researchers. In contrast, we were able to confirm the assumption that programmers do frequently intersperse refactoring with other program changes. By confirming assumptions and replicating studies made by other researchers, we can have greater confidence that those researchers' conclusions are generalizable.
Starting Page	287
Ending Page	297
Page Count	11
File Format	PDF
ISBN	9781424434534
DOI	10.1109/ICSE.2009.5070529
Language	English
Publisher	Association for Computing Machinery (ACM)
Publisher Date	2009-05-16
Access Restriction	Subscribed
Content Type	Text
Resource Type	Article

Central Library (ISO-9001:2015 Certified)
Indian Institute of Technology Kharagpur
Kharagpur, West Bengal, India | PIN - 721302

See location in the Map
03222 282435
Mail: support@ndl.gov.in

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in