[vc_empty_space][vc_empty_space]
Controlling software evolution process using code smell visualization
Nabilaha, Sunindyo W.D.a
a Institut Teknologi Bandung, Bandung, Indonesia
[vc_row][vc_column][vc_row_inner][vc_column_inner][vc_separator css=”.vc_custom_1624529070653{padding-top: 30px !important;padding-bottom: 30px !important;}”][/vc_column_inner][/vc_row_inner][vc_row_inner layout=”boxed”][vc_column_inner width=”3/4″ css=”.vc_custom_1624695412187{border-right-width: 1px !important;border-right-color: #dddddd !important;border-right-style: solid !important;border-radius: 1px !important;}”][vc_empty_space][megatron_heading title=”Abstract” size=”size-sm” text_align=”text-left”][vc_column_text]© 2019 Association for Computing Machinery.Software change is inevitable, evolution becomes a part ofsoftware lifetime, and software release becomes more frequent.Hence there is a need for the project manager to inspect andcontrol the process during software development and evolution. Inthe evolutionary stage, developers will face problems related toprogram code, one of that is identification of code smells. Thisproblem could negatively affect maintainability in evolution, adeveloper needs more time and money. Visualization techniquesturn data into a visual form so that it can provide information thatis easier to understand. In software evolution, visualization mostlyis used to view structure code. Previous research on evolutionvisualization limited to visualize the addition of code, the lastupdate, release history, and information of developer that madethe last change in program. However, this visualization is notenough to support understanding for the developers. We propose avisualization method for identifying code smell of the evolutionsoftware on Java programming, so the developers can more easilyunderstand the code that will be evolved. By knowing where thesmell of code in the program, programmers can immediately dorefactoring, the time and costs needed will also be low.Visualization of code smell is something new in the domain ofsoftware evolution. Finally, this design created to build tools indetecting code smells for software evolution process control.[/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”Author keywords” size=”size-sm” text_align=”text-left”][vc_column_text]Code smell,Evolutionary stage,Identifying code,Java programming,Software Evolution,Software evolution process,Software release,Software visualization[/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”Indexed keywords” size=”size-sm” text_align=”text-left”][vc_column_text]Code smell,Process Control,Software evolution,Software maintenance,Software visualization[/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”Funding details” size=”size-sm” text_align=”text-left”][vc_column_text][/vc_column_text][vc_empty_space][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][vc_empty_space][megatron_heading title=”DOI” size=”size-sm” text_align=”text-left”][vc_column_text]https://doi.org/10.1145/3341016.3341026[/vc_column_text][/vc_column_inner][vc_column_inner width=”1/4″][vc_column_text]Widget Plumx[/vc_column_text][/vc_column_inner][/vc_row_inner][/vc_column][/vc_row][vc_row][vc_column][vc_separator css=”.vc_custom_1624528584150{padding-top: 25px !important;padding-bottom: 25px !important;}”][/vc_column][/vc_row]