Good afternoon, I am developing a UML architecture for my program and so far I really like this tool, because It helps to compactly visualize the system. But how to visualize a project after it is written, when it is more rational to make changes directly in the code than in UML diagrams?

I could make appropriate changes to the UML-diagram before making changes to the code, but this approach turns the UML into the “fifth leg”, IMHO.

How to make changes to the project and at the same time continue to see the whole picture? Can the need for visualization be the result of a lack of programming experience?

  • one
    Use tools that build UML by code. DO NOT attempt to detail everything in the UML. - Nofate
  • Such tools are not available for all languages. For example, Qt signals and slots cannot normally be represented as UML class diagrams. And I just use Qt. Tell me more please, what are the names of the tools that convert code into diagrams? - RareScrap

0