This isn’t flame bait, I sincerely want to know. UML hit big in the late 90’s about the time that I was first starting to lift my head out of the VBScript/VBA morass and seeing the bigger software world. I grew up reading the old Software Development magazine and the Rational website. For a long time and even into my early Agile years I considered UML modeling to be a key skill for anybody leading software teams and definitely for anybody who was serious about learning about software design. Not so much because designing with UML is useful, but because it’s such a common communication tool in books and between developers. Or let me put that another way, I don’t find UML frequently helpful for figuring out what to do, but UML is very helpful in communicating or visualizing ideas.
I’m working up my book and I’m thinking about how to present certain ideas. My question to you is how helpful are UML diagrams to you in learning or understanding code level design constructs and concepts? I don’t see much use for static class diagrams in the book material so far, but I’ve always thought that sequence diagrams would help for some of the complex interactions. The problem for me is whether or not UML is still relevant to most developers now and in the near future. UML isn’t useful if the audience doesn’t get it.
Side question, I’m actually thinking I’m going to use CRC cards in place of class diagrams because I think it conveys more useful information and it’s easier on me. Anybody have an opinion about that?
Thanks in advance,