68
Views
3
Comments
How to ArchitectureDashboard

I have a few questions about how to operate ArchitectureDashboard.

A customer at work has implemented ArchitectureDashboard and is having trouble figuring out where to start modifying it because there are so many red applications and the customer is following OutSystems best practices and doesn't know what would be better by modifying it.

I myself do not have a deep understanding of ArchitectureDashboard yet, and would like to know if you have any examples of how you are operating it.

Also, regarding usage, a customer has requested that when the status of a modified area is set to resolved, the area that has been modified will no longer be displayed. Is such a feature available?

I cut this image from the OutSystems page because I thought it was hard to imagine from the text alone.



2021-12-07 07-28-47
Arnold Ayaoan Jr

Hi @Suzuki Yuki,

What we do is we check the Architecture findings as often as possible and try to fix those finding in ServiceStudio. As to how we fix those findings, we follow the recommendation of the platform which is found on How to fix section after drilling down to each findings like below:

There are also times where we don't intend to fix some recommendation so we just change the status to Won't fix.


Hope this helps.

Regards,

Arnold

2021-12-07 07-28-47
Arnold Ayaoan Jr

You can also refer to this documentation for further info: https://success.outsystems.com/Documentation/11/Managing_the_Applications_Lifecycle/Manage_technical_debt

2019-09-24 13-53-39
Nuno Fernandes

Hi Suzuki

You need first create a plan with your customer to give time in sprint to allow the code refactoring. You must stop features developments and do one or more refactoring sprints. Don't do the refactoring  at the same time creating new features.

I advise 1 week sprints with promotion into prod in the end.

Give priority to security first, then performance, architecture and leave maintainability to the end.

Architecture dashboard inside each issue explains how to fix. 

More than fix this issues this should me a developer mindset understand all best practices and do things right at first shot.

At the end of the day each developer should look in Arch if we create any issue and in the planning of the next day he should prepare the fix of the issue.


Best

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