I've worked at a software company as a developer for almost 3 years and never once seen and/or needed a UML diagram. My class (software development degree) just got railed by our teacher for half assing our UML diagrams. I can't help but moan at the utter uselessness of reading through the directions and "circling nouns & verbs".
There are much simpler and much more useful ways to communicate project requirements and objects.
Im half venting, but pretty curious if anybody has some insight for me. Thanks!
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! http://bit.ly/2UMdIXZ