At last a book about using UML, rather than simply describing the elements of the language.
Many readers will be familiar with OO concepts, but not so knowledgable about elements in UML beyond class diagrams. This book helps fill that gap.
The overarching theme is the discussion of a single project and you are shown you how to go through the Analysis and Design stages ( two cycles ) using UML.
It's oriented towards Use Cases, so if this is what you want to learn about you'll be happy.
It also covers collaboration and system sequence diagrams ( two UML standard diagrams ) and introduces constructs of the authors own e.g. contracts.
Some UML artefacts are brushed over - state diagrams and activation diagrams - so if you want to know how to use these, consult another source.
Although good as a primer, I was not convinced by this book that Use Cases are the best way to understand system requirements.