[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-564038-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-564038-en":126},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","visualizing-software-refactoring-using-radar-charts","Visualizing software refactoring using radar charts","","Visualizing software refactoring using radar charts presents a Radar Chart Refactoring Visualization (RcRV) approach for analyzing how refactoring changes evolve across multiple software releases. The method generates radar charts using inputs from developers or tools such as Ref-Finder, highlighting trends over time for multiple refactorings, methods, and classes. An evaluation study indicates the tool is useful, appealing, and easy to use, helping developers and maintainers detect design violations and potential bugs while reducing development and maintenance effort.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/general/","General",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/visualizing-software-refactoring-using-radar-charts/564038/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/visualizing-software-refactoring-using-radar-charts/564038.png","ImageObject",442,249,{"name":42,"@type":43},"kopisore","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-22","2026-10-12",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",5,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What problem does RcRV address in software refactoring analysis?","Question",{"text":63,"@type":64},"It addresses the difficulty of analyzing the impact when multiple refactorings are performed simultaneously, by visualizing refactoring changes across releases.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How does RcRV generate its visualizations?",{"text":68,"@type":64},"RcRV produces radar charts from developer inputs or refactoring identification tools such as Ref-Finder, showing changes across multiple dimensions.",{"name":70,"@type":61,"acceptedAnswer":71},"What benefits does the paper claim for developers and maintainers?",{"text":72,"@type":64},"The approach helps detect design violations and potential bugs and improves code comprehensibility, saving time and effort during development and maintenance.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},564038,1792019203,{"code":4,"msg":82,"data":83},"success",[84,89,94,99,104,109,114,119,123],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":86,"show_sort_weight":87,"slug":88},11,"Presentations",90,"presentations",{"id":90,"doc_module":22,"doc_module_name":25,"category_name":91,"show_sort_weight":92,"slug":93},12,"Resumes",80,"resumes",{"id":95,"doc_module":22,"doc_module_name":25,"category_name":96,"show_sort_weight":97,"slug":98},14,"Invoices",70,"invoices",{"id":100,"doc_module":22,"doc_module_name":25,"category_name":101,"show_sort_weight":102,"slug":103},15,"Posters",60,"posters",{"id":105,"doc_module":22,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},16,"Social Media",50,"social-media",{"id":110,"doc_module":22,"doc_module_name":25,"category_name":111,"show_sort_weight":112,"slug":113},17,"Forms",40,"forms",{"id":115,"doc_module":22,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},18,"Letters",30,"letters",{"id":120,"doc_module":22,"doc_module_name":25,"category_name":121,"show_sort_weight":55,"slug":122},21,"Paper Templates","papers-templates",{"id":124,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":4,"slug":125},158,"general-158",{"code":4,"msg":82,"data":127},{"doc_id":79,"user_id":128,"nickname":42,"user_avatar":129,"doc_module":22,"category_id":124,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":110,"language":135,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":12,"update_tm":139,"read_time":140},962090880963,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","[www. nature.com/scientificreports](www. nature.com/scientificreports)  \nOPEN  \nVisualizing software refactoring using radar charts  \nAbdel‑Rahman Al‑Ghuwairi1, DimahAl‑Fraihat2*, Yousef Sharrab3, Huda Alrashidi4, NoufAlmujally5, Ahmed Kittaneh1 & Ahmed Ali1  \nRefactoring tools have advanced greatly and are being used in many large projects. As a result, a great deal of information is now available about past refactoring and its effects on the source code. However, when multiple refactoring is performed at once, it becomes more difficult to analyze their impact. Refactoring visualization can help developers create more maintainable code that is easier to understand and modify over time. Although there is an increasing interest in visualizing code changes in software engineering research, there has been relatively little research on visualizing the process of refactoring. In this paper, we propose a Radar Chart Refactoring Visualization (RcRV) approach to visualize software refactoring of source code across multiple software releases. Radar charts are a form of 2D visualization that can show multiple variables on a single chart. The RcRv receives input from developers or through refactoring identification tools, such as Ref‑Finder, to generate charts. The generated charts can show the changes made during the refactoring process, highlighting areas of the trend of refactoring over evolution for multiple refactoring, multiple methods, and multiple classes. The evaluation study conducted to assess the usefulness ofthe RcRV tool has shown that the proposed tool is useful to developers, appealing, and easy to use. The proposed method of visualization can be beneficial for developers and maintainers to detect design violations and potential bugs in the code, thus saving time and effort during the development and maintenance process. Therefore, this research presents a significant contribution to the software engineering field by providing developers with an efficient tool to enhance code quality and maintainability.  \nSoftware refactoring is a well-known practice that is used to improve the quality of software systems. Refactoring involves making changes to the code structure without affecting the system’s functionality1. It is essential for software engineers to refactor their code to ensure that it remains maintainable, scalable, and reusable2,3. Recently, contemporary refactoring tools have been advancing rapidly and are now being widely utilized in several large projects. Consequently, a vast amount of information is available on past refactoring activities and their effects on the source code4. However, when multiple refactoring is performed simultaneously, it becomes increasingly challenging to analyze their impact. Researchers propose the use of visualization tools for refactoring to improve code comprehension and make it easier for developers to navigate complex codebases5. Visualizations are essential tools for software engineers to understand the impact of their code changes. Visualizing the refactoring can be especially helpful for new developers who are unfamiliar with the codebase6.  \nRefactoring visualization is vital for developers because it allows them to understand the structure of the code. Additionally, visualization can aid developers in detecting potential code issues that violate design principles, pinpointing code paths that are vulnerable to bugs, and ultimately reducing the time required during the development process6. Despite the increasing interest in visualizing code modifications in software engineering research, there has been limited research on visualizing the refactoring process. Further, several software tools have been developed to support refactoring but there is a lack of effective visualizations to aid developers in understanding the impact of these changes7.  \nIn this paper, we propose a novel approach to visualize software refactoring using radar charts. A radar chart, also known as a spider ","cbCaijHEDdcrHqcJ","https://ap.wps.com/l/cbCaijHEDdcrHqcJ","pdf",1904105,"English","# Introduction\n# Radar Chart Refactoring Visualization (RcRV)\n## Data input and chart generation\n## Use cases and comparative axes","[{\"question\":\"What problem does RcRV address in software refactoring analysis?\",\"answer\":\"It addresses the difficulty of analyzing the impact when multiple refactorings are performed simultaneously, by visualizing refactoring changes across releases.\"},{\"question\":\"How does RcRV generate its visualizations?\",\"answer\":\"RcRV produces radar charts from developer inputs or refactoring identification tools such as Ref-Finder, showing changes across multiple dimensions.\"},{\"question\":\"What benefits does the paper claim for developers and maintainers?\",\"answer\":\"The approach helps detect design violations and potential bugs and improves code comprehensibility, saving time and effort during development and maintenance.\"}]","Visualizing software refactoring using radar charts | PDF",1791839933,6]