If you are referring to Larman's _Applying UML and
Patterns: An Introduction to Object-Oriented Analysis and Design_, 8 chapters is a very small fraction of the book. I'm only about halfway through the book, but viewed from the middle, it appears that the book does a address most, perhaps all, of the points you listed. As I recall, many of those points are initially touched the first eight chapters. However, the book often introduce a concept briefly, and then elaborates as the concept is applied there and later in the example project. Also, some of the process issues you listed that are touched a bit lightly in the first few chapters appear come up again in chapter 37.
I think Larman communicates some points as much by showing you as by telling you. I spend a good bit of time looking at exactly what he is doing with the example, and thinking about why. I seem to like the book more than some of my colleagues who remark that some of the pictures look so much like the previous pictures that they don't bother to look carefully at what's new.
I've put myself on the hook to take 486, but my approach to learning OO analyis and design is to study the book and apply it myself to learn what the author is teaching, and then, if necessary, to review with the test objectives in hand, filling in holes. However, from what I've seen, I don't expect the objectives to be a problem. (I may change my tune once I take the pre-test.)
