Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W Wiki Home
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • SDK4ED WikiSDK4ED Wiki
  • Wiki Home
  • Wiki
  • technical debt toolbox frontend walkthrough

technical debt toolbox frontend walkthrough · Changes

Page history
Technical Debt - Front End Refactorings authored May 26, 2020 by Angeliki Tsintzira's avatar Angeliki Tsintzira
Hide whitespace changes
Inline Side-by-side
technical-debt-toolbox-frontend-walkthrough.md
View page @ 8d4835f5
......@@ -54,3 +54,35 @@ In addition, TD New code, presents the technical debt issues introduced on new m
Refactorings Panel consists of Code Refactorings, Design Refactorings and Architecture Refactorings.
![DT-8](uploads/technical-debt/RefactoringsPanel.png)
# Code Refactorings Page
Suppose that the user selects the "Code Refactorings" option from the drop-down list of Refactorings. Code Refactorings suggests
refactorings based on source code that introduce code smells. The figure below, presents a example of this type of refactorings. The rules are ranked based on
the urgency to be solved. We can also see the probability of this rule to occure and the probability change.
![DT-9](uploads/technical-debt/CodeRefactorings1.png)
if you click on a rule, a new window opens with a brief decription of the rule and examples of how to solve this code smell.
![DT-10](uploads/technical-debt/CodeRefactorings2.png)
Last, in the new window, the user can see the files that violate this rule, the line of the violation and the effort in minutes that need to be solved.
An example of this, it is shown on the figure below.
![DT-11](uploads/technical-debt/CodeRefactorings3.png)
# Design Refactorings Page
Suppose that the user selects the "Design Refactorings" option from the drop-down list of Refactorings. Design Refactorings suggests two type of refactorings,
Extract Method Opportunities and Move Class Refactorings. In the figure below, presents a example of Extract Method Opportunities for 'Neurasmus' project.
Extract Method Opportunities tries to solve the long method code smell. The box size shows the lines of code the method has and the color density the cohesion
benefit from the suggested refactoring.
![DT-12](uploads/technical-debt/DesignRefactorings1.png)
Move Class Refactorings suggests and different code structure that improves cohesion and coupling in project level. An example of this type of refactoring
is shown on the picture below.
![DT-13](uploads/technical-debt/DesignRefactorings2.png)
Clone repository
  • Advanced
  • Architectural Toolbox Description
  • Architectural Toolbox Front End
  • Architectural Toolbox Home
  • Architectural Toolbox Installation
  • Architectural Toolbox Usage
  • Decision Support Toolbox Description
  • Decision Support Toolbox Front end
  • Decision Support Toolbox Installation
  • Decision Support Toolbox Usage
  • Decision Support Toolbox
  • Energy Toolbox Description
  • Energy Toolbox Front end
  • Energy Toolbox Installation
  • Energy Toolbox Usage
View All Pages