Section 20.1.  Achieving the Right Balance

20.1. Achieving the Right Balance In the preceding parts of this book, we went into great detail on the theoretical basis for aspects. We provided a systematic approach for applying use cases and aspects to achieve better separation of concerns. We demonstrated how to apply the approach from requirements to code and how to establish a resilient architecture based on the approach. It is time for you to apply the approach to your project. We recognize that every project is differentdifferent complexity, different technologies, different levels of formality, and so on. Every project team is different as well, with various backgrounds and skill sets. You definitely need to tailor the approach to suit the specific needs of your project. In this chapter, we discuss how you can adopt aspect orientation, specifically, the approach described in this book. This chapter is not about adopting a new approach in an organization. Adopting a new technology in an organization means organizational change, and it involves getting a champion, identifying pilot projects, and morethat is an entirely separate topic. Rather, the premise is this: given that you want to apply use cases and aspects on an already chosen project, what should you do in that project? Which areas of our approach should you apply? How do you balance your existing approach with the new approach? The remainder of this chapter is a guide to adopting the approach to a project discussed in this book. In particular, we look at the following considerations: Selecting the areas (or disciplines) within the methodology you want to adoptrequirements, design, implementation, testing, and so on. Balancing current and proposed approaches for software development at different phases of a project. For each consideration, we discuss some of the adoption challenges you are likely to face and show you how to resolve them.