> None of the jargon is necessarily wrong but it's not grounded in the reality of the current software systems at all. Oddly enough, I'm having this discussion

> None of the jargon is necessarily wrong but it's not grounded in the reality of the current software systems at all. Oddly enough, I'm having this discussion right now with a few other people at a new company. They want new documents to describe the ideal and I want it to describe how things work currently and evolve it over time. OTOH, I've never gotten the impression that any of them are technically weak, I think they just view their role differently than I do. Much like how a TDD proponent will start imagining unit tests are the point, I think these architects have started to think these documents and diagrams are the point.