How many findings is each color of technical debt?

The company where I work at uses the Architecture Dashboard tool to analyze every app we developed. We're now writing a report to pass on to the developers in which we wish to show specific numbers of findings of each code pattern and its respective category, and together with that info we would like to include a number scale so they can see why their app has the color it has in terms of numbers of findings.

In order to do that, I'd like to use numbers based on how the tool itself categorizes the modules/apps, but I haven't found it anywhere on the documentation. I know it assigns the colors based on number of findings AND based on the dependencies, but I'd like to know if there is any type of scale we can use ignoring the dependencies (for example: from 1-100 total findings it gets the color green, from 200-400 it's yellow, etc.)

Why don't you just give the developers access to the architecture dashboard. It already does assign colors to applications based on the findings and their impact on technical debt. 

It seems to me that it is a waste of time to write a report about this as you can just give the developers direct access to the tool, and it helps them point out where these findings are.

If you want developers to only see their apps. Use lifetime teams to categorize these apps and give the developers access to what they should see. 

https://success.outsystems.com/Documentation/11/Managing_the_Applications_Lifecycle/Manage_technical_debt/How_does_Architecture_Dashboard_work

Also, anything above 50 findings in any given application is extremely problematic. It should be around 0.


If you absolutely want to write a report, automate it with the new API:

https://success.outsystems.com/Documentation/11/Reference/OutSystems_APIs/Architecture_Dashboard_API 

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.