I was preparing some UML material the other day, and came across the graphic below which nicely lays out the different diagrams, and most importantly, shows that critical split between a Structure Diagram and a Behaviour Diagram.
When explaining UML to novices, I find that the structure vs behaviour split is often the “Ah Ha” moment when things fall into place. Without that, the names of the diagrams are just too much to digest in a single sitting.
For those wanting more info, check out UML-Diagrams.org
We normally think of technology leading the way, taking us forward and ‘time’ (people, processes, etc) playing catch up. So it was interesting when I found an example at home where the roles were reverssed …
For very many years, IT professionals have tried to attain a certain degree of software reuse. The idea is simple – if you can reuse, then you can build “better, faster, cheaper“, and in so doing benefit from greater efficiency. One of the large drivers that has helped to reach this is the Open Source community that openly shares small and large projects and in several cases entire systems. Evidence of this success is all around us, almost to our own detriment where ‘custom software’ now looks comparatively expensive!
The Steve Jobs biography will be available in just a few weeks time. Now, while I’m not normally one to go out and get the ‘latest release’, I do think that this book will be worth the trip to the bookstore.
