Updates
Latest Tweet
What's New?
Check out for latest innovation, a computer based training video collection
Like this Page
Aspect-Oriented Software Development with Use Cases Review by R. Williams
In Absentia: Unfortunate Sign of the Times
No one has reviewed this?? This is a great book. Jacobson describes it as the result of a kind of epiphanal realization that AOP could solve an inherent problem in use case design. This is how the book hooked me: rather than just showing AOP as a series of stunts, or explaining it w/the usual little examples (logging, exceptions, etc.), this book starts w/the strategic implications and then works down to the tactical. The basic premise is that the so called separation of concerns is always followed by a required recomposition of said concerns and that aspects provide a means of recomposing w/out introducing 'leaks' and the like.
It's pathetic that no one is reading this book. Ballmer was mooning last week about how he's going to erase Rational (and with it the UML). Jacobson and use cases are the best part of the UML and one of the great things about this book is it opens the door to a conception of a different design approach that short circuits some of the flab from the RUP req/spec cycle (which, when trying to be iterative, tends instead toward rapid repeat waterfall).
Despite the apparent dearth of readership, I predict this book will be seen as one of the most important of this decade.