| ... | ... | @@ -18,23 +18,17 @@ Technical Debt Panel consists of TD Analysis and TD New Code. |
|
|
|
|
|
|
|
# TD Analysis Page
|
|
|
|
|
|
|
|
Suppose that the user selects the "TD Analysis" option from the drop-down list of Technical Debt. Then he/she is navigated to the page presented in the figure below.
|
|
|
|
Suppose that the user selects a project from the listed ones and then the TD Analysis option from the drop-down list of Technical Debt. Then they are navigated to the page presented in Figure below/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As can be seen by the figure above, the page provides a drop-down list for selecting a software project and one buttons, namely ”New Analysis” (the displayed projects in the example are the three projects provided by the use case providers of the SDK4ED Project).
|
|
|
|
The TD Analysis Panel shows the assessment results of the selected software application that are parsed and presented to the user through different types of visualization. Suppose that the user selected the "Neurasmus" project from the project panel and then selected the TD Analysis Panel from the Technical Debt drop-down menu. Behind the scenes, the appropriate web services are invoked and when the results are ready the page is rendered in order to present them. The results of the "Neurasmus" project are presented in the Figures below. In the Figure above, the line chart shows the evolution of TD Aspects through software versions. It presents TD Principal, TD Interest, TD Breaking Point, and TD Cumulative Interest. From this diagram, we can conclude that TD principal increases as the software evolves. TD Interest and cumulative interest are also increased. In version 5, TD Interest starts to show a little reduction and as a result breaking point also increased. As a general rule, it is preferable to have interest reduced since it is a good indicator that the software quality has been improved resulting in a more easily maintainable software.
|
|
|
|
|
|
|
|
By clicking on the ”New Analysis” button, a new analysis of the selected software application is performed, by invoking the *TD Analysis* web services of the Technical Debt Toolbox back-end (see the [Description](technical-debt-toolbox-description) and [Usage](technica;-debt-toolbox-usage) Wiki Pages for more information regarding these services). In either case, the assessment results of the selected software application are parsed and presented to the user through different types of visualizations.
|
|
|
|
|
|
|
|
Suppose that the user selects the "Holisun Arassistance" project from the drop-down list and then clicks either on the "New Analysis" button for new version analysis or just envoke pre-analysed data. Behind the scenes the appropriate web services are invoked and when the results are ready the page is rendered in order to visualize them. The results of the "Holisun Arassistance" Project are presented in the following figures.
|
|
|
|
|
|
|
|
At the top part of the page, the results of the *TD Analysis* web service for the "Holisun Arassistance" project are presented (see the figure above).
|
|
|
|
The top line chart shows the evolution of TD Aspects throught software versions. We present TD Principal, TD Interest, TD Breaking Point and TD Cumulative Interest.
|
|
|
|
Under the line chart, principal and interest metrics on project level are shown. Principal metrics are TD Principal in minutes and currency, number of bugs, vulnerabilities, code smells and duplications. Interest metrics are breaking point, interest in currency, interest probability, maintainability ranking and interest probability ranking among projects (see the figure below).
|
|
|
|
For the “Neurasmus” project, the principal is 1470 dollars and the interest is 63.97 dollars resulting in a breaking point of 26, which means in 26 versions from now the software will no longer be sustainable. Interest probability is 29% which means that at 29% the software changes through software versions. Overall, this project got good results in terms of technical debt.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Next, TD Analysis presents some principal and interest metrics in artefact level(file/package level). For more informations of the metrics we use for object-oriented and non-object-oriented languages, see the Deliverable D3.1. Some metrics for object-oriented-language Java are shown in the figures below, the first figure presents interest metrics and the second principal metrics.
|
|
|
|
Next, TD Analysis presents some principal and interest metrics at artefact level(file/package level). For more information about the metrics we use for object-oriented and non-object-oriented languages, see the Deliverable D3.1. Some metrics for object-oriented-language Java are shown in the figures below, the first figure presents interest metrics and the second principal metrics.
|
|
|
|
|
|
|
|
|
|
|
|
|
| ... | ... | |
