How to Read This Book

Of course, the most straightforward way to read this book is from start to finish. The book follows the basic structure of introduction and motivation (Chapters 1 and 2), overview and illustration of the approach (Chapters 3-6), guidance on mapping your designs to some AOP languages in Chapter 7 and examples of its application (Chapters 8 and 9).

However, different parts of the book may be of more interest than others, depending on your perspective. If you're not sure what an aspect even is, then Chapters 1, 3 and 4 will be of lots of help. They go over the basic concepts and walk you through finding aspects in a set of requirements.

If you're not convinced aspects are all that great, and are asking the question "Why do we need them anyway?" then Chapter 2 will be for you. Chapters 8 and 9 will also provide you with examples of how aspects can be applied in different kinds of systems.

If you'd like instruction on capturing aspects in design, then Chapters 5 and 6, which provide details of Theme/UML will walk you through designing the aspects and the core of your system, and on capturing the specification of their composition.