The more I think about it the more it seems like the code itself should be the diagram. Not the code you write FOR the diagram, but the code for the feature, product, team you work on.
Feature2: Diagram {
// list feature 2 dependencies
}
Then some compilation system should be able to build a not so noisy diagram from this. Key being not so noisy (I don’t care about the 100 million sub classes here).
Here’s an example just off the top of my head:
Feature1: Diagram { // list feature 1 dependencies feature2: Feature2 }
Feature2: Diagram { // list feature 2 dependencies }
Then some compilation system should be able to build a not so noisy diagram from this. Key being not so noisy (I don’t care about the 100 million sub classes here).