Skip to main content

 

 

 

 
 
Service Studio version:
 
 
OutSystems

Getting started as a developer

Template:OutSystems/Documentation_KB/ContentCollaboration
  • Edit
    Collaborate with us
    Edit this page on GitHub
  • As a developer, the Architecture Dashboard provides you with an overview of the organization's technical debt. It also provides you with a detailed overview of the technical debt of the apps in the infrastructure that need to be fixed so that the overall technical debt score is reduced.

    This guide assumes the following:

    • Your infrastructure is already set up in Architecture Dashboard.

    • Your IT user is already associated with Architecture Dashboard.

    Check the technical debt of the modules of an app

    The canvas gives you an overview of the apps in the infrastructure that you have access to.

    Each square is an app. It shows the app name and the app type.

    The color of each app shows you how high or low the technical debt is in that app.

    Technical debt tells you how difficult or easy it is to change and maintain an app or module.

    Technical debt and agility color scale

    Red means the app has high technical debt.

    To get an overview of the modules of an app, double-click the app.

    Overview of modules in an app

    Selecting a module highlights the dependencies of the module (if any).

    Module dependencies

    Find and understand the causes of technical debt in the module

    To see the causes of technical debt in the app, click the Open module report button in the side panel.

    Open module report

    You can filter the report based on a specific app, module, category, when it was analyzed, the findings status, as well as specific users.

    Filters

    To see details about a code pattern that causes technical debt, click Impact. The Impact information details why a code pattern creates technical debt.

    Impact information

    To check how to fix the code pattern, click How to fix. You can also use this information to understand the effort involved in fixing a code pattern.

    How to fix

    Fix and resolve technical debt findings

    The Findings section displays all the occurrences of the code pattern. To see in which module and element each finding occurs, click the path icon.

    Findings

    To open Service Studio and navigate to the element where a code patterns occurs, click the Open in Service Studio icon.

    Open in Service Studio

    Your browser may ask you to confirm that you want to open Service Studio. In Chrome, confirm that you want to open Service Studio by clicking Open Service Studio.

    After checking a specific finding, change the state of the finding depending on your action:

    • If you fix the finding, set the state to Resolve as already fixed. This lets other developers in your team know it's fixed. After the next synchronization, if you have solved the finding correctly, it disappears. Otherwise, the finding reverts to Open.

    • If you don't fix the finding because the finding is a false positive, set the state to Resolve as false positive. After the next synchronization, the finding is not counted towards the total technical debt score.

    • If you don't fix the finding, but the finding isn't a false positive, set the state to Resolve as won't fix and detail the reason for not fixing it. After the next synchronization, the finding is not counted towards the total technical debt score.

    • To temporarily remove the finding from the total debt calculation, set the state to Remind me later (30 days). After the next synchronization, and during the next 30 days, the finding is not counted towards the total technical debt score.

    • Was this article helpful?