Let’s Talk <i>With</i> Developers, Not <i>About</i> Developers: A Review of Automatic Program Repair Research

نویسندگان

چکیده

Automatic program repair (APR) offers significant potential for automating some coding tasks. Using APR could reduce the high costs historically associated with fixing code faults and deliver benefits to software engineering. Adopting also have profound implications developers’ daily activities, transforming their work practices. To realise of it is vital that we consider how developers feel about impact may on work. Developing tools without consideration developer likely undermine success deployment. In this paper, critically review are considered in research by analysing human factors treated 260 studies from Monperrus’s Living Review APR. Over half our were motivated a problem faced (e.g., difficulty faults). Despite these human-oriented motivations, fewer than 7% included study. We looked detail at found quality mixed (for example, one study was based input only developer). Our results suggest often talked about studies, but rarely xmlns:xlink="http://www.w3.org/1999/xlink">with . A more comprehensive reliable understanding relation needed. Without understanding, will be difficult develop techniques which integrate effectively into workflows. recommend future agenda advance

برای دانلود باید عضویت طلایی داشته باشید

برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

منابع مشابه

How Developers Diagnose and Repair Software Bugs

How do practitioners debug computer programs? In a retrospective study with 180 respondents and an observational study with 12 practitioners, we collect and discuss data on how developers spend their time on diagnosis and fixing bugs, with key findings on tools and strategies used, as well as highlighting the need for automated assistance. To facilitate and guide future research, we provide a h...

متن کامل

Not Surveying Developers and Code About Languages

We present cross-sectional analyses of programming language use and reflect upon our experience in doing so. In particular, we directly survey 1500-13000 developers and indirectly do so by mining 200000 repositories. Our analysis reveals programming language adoption phenomena surrounding developer age, birth year, work place, opinions, gender, and choice of software repository. We find that su...

متن کامل

How Do Open Source Developers Talk about Users?

When open source software developers are making design decisions, how do they talk about users? To begin to answer this question, 100 contentious Firefox bug reports were analyzed for distinct uses of the word “user.” The results show that developers use authoritative words (such as allow, educate, and require) to describe what software does for users. Most statements involved confident specula...

متن کامل

Drainage developers

Drainage developers O ur bodies' tissues need continuous irrigation and drainage. Blood vessels feeding the tissues bring in the fl uids, and drainage occurs via the lymphatic system. Whereas much is known about how blood vessels are built, the same was not true for lymph vessels. Now though, Norrmén et al. have identifi ed two of the lead engineers that direct drainage construc-tion—the transc...

متن کامل

Automatic detection of system-specific conventions unknown to developers

In Apache Ant, a convention to improve maintenance was introduced in 2004 stating a new way to close files instead of the Java generic InputStream.close(). Yet, six years after its introduction, this convention was still not generally known to the developers. Two existing solutions could help in these cases. First, one can deprecate entities, but, in our example, one can hardly deprecate Java’s...

متن کامل

ذخیره در منابع من


  با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید

ژورنال

عنوان ژورنال: IEEE Transactions on Software Engineering

سال: 2023

ISSN: ['0098-5589', '1939-3520', '2326-3881']

DOI: https://doi.org/10.1109/tse.2022.3152089