6 ms·
In practice, and I mean at mega-corps with government contracts that require UML diagrams for everything I've seen this as a common pattern: 1) An EA is hired
by bane 13y ago
In practice, and I mean at mega-corps with government contracts that require UML diagrams for everything I've seen this as a common pattern:
1) An EA is hired who gins up a stack of UML diagrams which are sent for review and acceptance by the customer.
2) The system is then actually designed and built regardless of (and often despite) the accepted UML diagrams.
3) The built system is then documented in a new stack of UML diagrams by the EA which are then delivered to the customer as if the first stack didn't exist.
The problem in the industry with UML is not #3, UML can be a great way of describing a complex system, the problem is #1, UML is a terrible way at blueprinting how a working system will look like in the end.
- marcosdumay 13y agoUML is just a notation. It is great for blueprinting software (except that graphics create problems, and UML is graphical), it makes no difference if they exist or not. The problem is that people are terrible for blueprinting sotfware that does not yet exist. Whatever notation you choose, the problem will still be there.
- bane 13y ago> The problem is that people are terrible for blueprinting sotfware that does not yet exist. I agree, in addition the people who usually are doing the blueprinting usually don't really know much about the nuts and bolts of actually building software (or haven't built any in a very long time).
- dreamfactory 13y agoThe worse problem is that the stack of UML diagrams in 1. is sent offshore to be implemented verbatim by many junior people working in parallel and in isolation, a manual test team produces thousands of bug reports on the resultant ball of mud which are then hastily patched over with sticky tape, and the whole sorry mess is hailed as an exemplar of software delivery process for being made to hobble over the line without exploding.