A group of people working on computers.
BGSU computer science professor Dr. Michael Decker is developing an open-source tool for software developers unlike anything currently available as part of a $750,000 grant from the National Science Foundation.

BGSU computer science professor developing novel open-source differencing tool funded by a $750K grant

Estimated Reading Time:  

Dr. Michael Decker’s software infrastructure, srcDiff, identifies changes to code more accurately and comprehensively than existing methods

By Laren Kowalczyk '07

A Bowling Green State University computer science professor is developing an open-source tool for software developers unlike anything currently available as part of a federally-funded grant designed to support research on how software evolves over time.

Dr. Michael Decker’s proposed new software infrastructure called srcDiff, derived from Source Code Differencer, identifies changes made to code more accurately and comprehensively than existing methods by modeling a programmer’s viewpoint of the software change.

Decker, an associate professor in the BGSU Computer Science Department, is collaborating with Dr. Jonathan Maletic, a computer science professor at Kent State University, in developing the infrastructure and soliciting feedback through community outreach, which is a substantial focus of the project.

The three-year project is being funded by a $750,000 grant from the National Science Foundation.

“The unique part about this grant is its focus on community outreach,” Decker said. “We’re developing open-source software that will enable other researchers and industry practitioners to further their research or apply it to their projects or industry.”

A man in a computer lab.
Dr. Michael Decker is collaborating with Kent State University to develop an open-source differencing tool for software developers. (BGSU photo)

The differencing process

Developers constantly change code to improve functionality, fix bugs, add new features, merge software and detect clones, among many other things.

Software developers need to be able to find and understand what changes have occurred within the code. To do that, they use a process called differencing, which compares two files side-by-side to determine what differentiates them.

“For example, the code was working right, or you knew it worked at some point,” Decker said. “Then changes are made to the system, and now that code no longer works. Something must have changed to break that code.”

The challenge for developers, Decker said, is that current differencing tools rely on the mechanical property of edit distance alone. Edit distance is how dissimilar an item, such as a sequence of characters, is to another.

Decker said srcDiff uses edit distance in combination with differencing rules that contain a developer’s domain knowledge, increasing its efficiency and effectiveness in identifying what changes have occurred.

The focus on producing human-centric differences reduces the burden researchers and practitioners often face in obtaining, analyzing and processing software changes.

“The infrastructure we’re developing helps people more easily understand what changes occurred in the system,” Decker said. “It produces a more accurate and human-understandable difference of changes. The approach is very scalable and can be applied to large software systems.”

Novel feature

One of the infrastructure’s novel features is its ability to identify and report changes to nonexecutable parts of code, including white space and comments developers include to explain changes they’ve made.

Typical differencing tools only capture changes to the executable code, which directs the computer to perform various functions.

“There’s a lot of meaning in the white space of code, and the comments are very important for a developer to understand the code and the work done on that body of code. Other tools discard all the white space and comments. They are only differencing on the executable parts.

“The srcDiff infrastructure preserves all of that.”

In addition to developing and refining the srcDiff infrastructure, Decker is also building a support library and working with Maletic to solicit feedback through community workshops, client meetings and attending conferences.

“We’re building infrastructure that supports research, and getting feedback from the community is essential as we continue developing our tool,” Maletic said. “In addition to creating awareness of our tool, we’re helping researchers understand how they can use srcDiff as part of their research.”

Related Stories

Media Contact | Michael Bratton | mbratto@bgsu.edu | 419-372-6349

Updated: 10/24/2023 02:20PM