2 ms·

Thanks for sharing this. If I may ask, would Ilograph (diagramming tool I made) alleviate the two issues you've raised? It aims to show cross-cutting dependenci

by Veuxdo 5y ago

Thanks for sharing this. If I may ask, would Ilograph (diagramming tool I made) alleviate the two issues you've raised? It aims to show cross-cutting dependencies via perspectives, and has an interactive layout to make complex perspectives easier to read. It's definitely a "long term" diagram solution, as opposed to quick sketches. Would love to know how close it gets to the mark. Example: https://app.ilograph.com/demo.ilograph.Ilograph/Request https://app.ilograph.com/demo.ilograph.Ilograph/Request

frederikb 5y ago
I've seen you mention it before. At first glance it seems interesting and I definitely agree that having multiple perspectives available to view and explore the model of a complex system is key. It reminds me of https://structurizr.com/ https://structurizr.com/ which builds upon the C4 model for visualizing architecture. Using these tools successfully is also a question of the goal: are we using them to model and plan up-front or are we visualizing the status quo (for onboarding, change analysis or other purposes). If it's the latter then you need to investigate how to (partly) derive the model from the single source of truth - your code base of applications and infrastructure. Otherwise there is a strong likelyhood of the model diverging from the truth and thus losing its value.