The challenge is that there are different ways of "mapping" software. You could map the way programs fit into machines, and the networks between them. This wou

The challenge is that there are different ways of "mapping" software. You could map the way programs fit into machines, and the networks between them. This would be the topology. You can map the way services call upon one another with requests. This is the service graph. You can map how systems interact over events or shared resources. You could say this is the logical graph. The problem happens when you try and graph them all at once. It's the same as trying to draw a real map, with all the services, bus routes, railways, shops and administrative regions superimposed on one image. It's very busy. So I use separate maps. Tools are another matter. Personally I use Mermaid for graphs. I also have my own tools that create SVG visualisations using DAGre. This can be helpful for interactive visualisations where you can click into different nodes and explore more detail. My system uses CloudFormation templates and our in house deployment DSLs to figure out the "topology", then let the users see the different superimposed "graphs" as they see fit