I was trying to say (without being as blunt as in this message) that "naked" UML could stand for Useless Markup Language.
Just because some design patterns might have similar UML class diagrams, I wouldn't infer UML is useless. Even if UML was "simply not expressive enough to fully support software development", it can be used for many scenarios, e.g.: - getting a quick overview over an application's class structure (class diagrams), - understanding how a certain algorithm involves different objects (sequence diagrams), - documenting an underlying state machine (state diagrams), etc. A modelling language doesn't need to be complete in order to be very useful for communication and documentation. And although I'm not a fan of totally UML-based software development, I consider it a great tool for these purposes. And the question is: what would you suggest instead? Use text instead of pictures to explain application design? Use some home-brewn graphical method instead of UML? What's the alternative? Fabian =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
