Summary

In this chapter, we explained how to map your Theme/UML designs to different AOP approaches. AspectJ and AspectWerkz demonstrate considerable similarity, and the same general approach applies to both. If you use a different AOP language whose principles are rooted in AspectJ, then you will find these useful, since it is likely that the general principles of mapping from Theme/UML also apply to the language you use. At a high level, the CME also demonstrates some similarity, though it is more straightforward to maintain the separation of the base themes because the Theme approach is modeled on the same principles as the CME.

In the next two chapters, we work through two case studies to further illustrate the Theme approach. For each, starting from a requirements specification, we work through aspect-oriented analysis with Theme/Doc and aspect-oriented design with Theme/UML.