2 ms·
People tried to make UML the language that software engineers communicated in. I think that failed because "what" is not enough. To really understand, you nee
by AnimalMuppet 2y ago
People tried to make UML the language that software engineers communicated in. I think that failed because "what" is not enough. To really understand, you need "why", and that always comes in words. UML isn't able to capture that. And when people thought that UML was "the way we communicate", they did UML but few words, and it wasn't enough. The optimum turns out to be mostly words with a few UML diagrams.
A second reason is that, when things changed, UML diagrams were too hard to update to correspond to the new reality.
- HelloNurse 2y ago> To really understand, you need "why", and that always comes in words. I'm open to the possibility of explaining "why" in diagrams, but certainly not in use case diagrams consisting of stick figures chained to big rectangles.