Regarding the length of the book, we consciously decided to keep it "short and sweet", as this style worked very effectively for Kendall and Martin Fowler on UML Distilled.
Regarding further examples, we (ICONIX) do have a series of 4 examples that follow the steps in the book available as part of our 4 CDROM multimedia tutorial series on Unified Object Modeling. The example projects on the CDs are: Video On Demand, Hospital Information System, Onboard Auto Navigation, and Portfolio/Risk Management. Further information is available on our website at http://www.iconixsw.com/CDCourses.html.
Finally, while I'd like to have been smart enough to have invented Robustness Analysis, I can't claim credit. I learned about this technique 8 years ago from Ivar Jacobson's book: "Object Oriented Software Engineering, A Use Case Driven Approach." However, I hope that Kendall and I have explained and illustrated the usefulness of this technique in connecting "what" with "how" a bit more clearly than it has been explained elsewhere.
Many software projects fail because they don't manage to bridge the "what/how gap" successfully, and trying to address this problem is probably the central idea of our book. Unfortunately the robustness diagram got left out of "core UML", but the good news is, it's easy to use UML stereotypes to make these diagrams.
Doug Rosenberg
ICONIX
doug@iconixsw.com