Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactored data clumps with the help of LLMs (research project) #2547

Closed
wants to merge 2 commits into from

Conversation

compf
Copy link

@compf compf commented Apr 10, 2024

Hello maintainers,

I am conducting a master thesis project focused on enhancing code quality through automated refactoring of data clumps, assisted by Large Language Models (LLMs).

Data clump definition

A data clump exists if

  1. two methods (in the same or in different classes) have at least 3 common parameters and one of those methods does not override the other, or
  2. At least three fields in a class are common with the parameters of a method (in the same or in a different class), or
  3. Two different classes have at least three common fields

See also the following UML diagram as an example
Example data clump

I believe these refactoring can contribute to the project by reducing complexity and enhancing readability of your source code.

Pursuant to the EU AI Act, I fully disclose the use of LLMs in generating these refactorings, emphasizing that all changes have undergone human review for quality assurance.

Even if you decide not to integrate my changes to your codebase (which is perfectly fine), I ask you to fill out a feedback survey, which will be scientifically evaluated to determine the acceptance of AI-supported refactorings. You can find the feedback survey under https://campus.lamapoll.de/Data-clump-refactoring/en

Thank you for considering my contribution. I look forward to your feedback. If you have any other questions or comments, feel free to write a comment, or email me under [email protected] .

Best regards,
Timo Schoemaker
Department of Computer Science
University of Osnabrück

@ptrthomas
Copy link
Member

@compf thanks for the details. I do not find the changes helpful. the original code is less verbose and more readable and maintainable (in my opinion). Scenario and ScenarioOutline are separate to mirror parts of a file format parsed by ANTLR. they may be "similar" but they have subtle differences in how they are used, I will take a look at the survey if I can fill it

@ptrthomas ptrthomas closed this Apr 11, 2024
@compf
Copy link
Author

compf commented Apr 11, 2024

That's perfectly fine. Thank you nevertheless for the feedback. If would be great if you can fill out the survey :)

@ptrthomas
Copy link
Member

@compf yes I have filled out the survey

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants