Back in the late 80's, there was the CASE (Computer-Aided Software Engineering) fad, when it was thought diagrams could replace code. The idea that a picture is worth a thousand words is not applicable to most of the words one would use to discuss systems designs. It is very difficult to discuss purpose and intent, or to present arguments that the design satisfies requirements or observes constraints, to justify choi…
It's intersting to see what classes aren't used at all and where all the associations accumulate.
Also, if the "previous devs" are still around it's easier to talk with them about these pictures, than to talk about 100 text files.