I'd like to just add my 2bits worth in to this discussion; the usefulness of UML and it's advantages/disadvantages are not actually the issue, it doesn't make this book any better or worse. This is a good book, if you would like to learn UML.
If I just play devils advocate and say that UML is a good visual representation of a 'System' (software or other) that is non platform or environment specific (i.e. Windows or Unix. C++ or Java) but does lack contraints that would normally apply in a development environment, then maybe it would be worth looking at the future of modelling and tighten the rules, and maybe come up with something like OCL (Object Constraint Language, see link below.) which is an extension to UML that is more capable of modelling a state oriented system (i.e. Most software programs).
Object Constraing Language, IBM's Perspective.
"There is no evidence to suggest that any of the apparent losses reported were real losses of nuclear material," the authority added.
To paraphrase; "It's not lost, we just don't know where it is".
--
a very worried Londoner
I'd like to just add my 2bits worth in to this discussion; the usefulness of UML and it's advantages/disadvantages are not actually the issue, it doesn't make this book any better or worse. This is a good book, if you would like to learn UML. If I just play devils advocate and say that UML is a good visual representation of a 'System' (software or other) that is non platform or environment specific (i.e. Windows or Unix. C++ or Java) but does lack contraints that would normally apply in a development environment, then maybe it would be worth looking at the future of modelling and tighten the rules, and maybe come up with something like OCL (Object Constraint Language, see link below.) which is an extension to UML that is more capable of modelling a state oriented system (i.e. Most software programs). Object Constraing Language, IBM's Perspective.