Skip to content

Please allow system diagrams even when components are not semantically correct

When trying to add new functionality or new components to a system it is very useful to be able to just hook up some dummy components and interfaces to visualize and try out how the architecture will be affected. Having the diagram show something is a very useful tool while refactoring.

All you need to draw a system diagram is the system and the component required/provided ports. So why does this fail to generate a diagram if I change a function signature and I am in the middle of a refactor?

Currently there are some problems with this way of working:

  • System diagrams cannot be drawn unless all ports are connected, this used to work before (#69)
  • If component behavior has a semantic problem, i.e. a function parameter was removed, the entire system refuses to draw.
    • Another semantic issue regularly occurring while changing systems is having a dummy component with empty behavior
  • Generating a system diagram is SO SLOW, why does it take over 30 seconds to draw a system with 20 components on a i9 processor?!

The system diagram could be a useful tool to use during development and refactoring, but in the current state it is basically useless for this.