1. Use Case Modularity using Aspects Manali Bhole and Therapon Skotiniotis* Northeastern University, Boston, USA. {manali, skotthe}@ccs.neu.edu Results: Use Cases to Code mapping allows for: • Easier traceability of stakeholders requirements. • Iterative approach to development and future evolution. • Increase understandability of design through inspection of implementation. • Easier validation of implementation against requirements. Use Cases Software Modules • Easier to show that implementation covers all use cases (scenarios). Implementation phase Tangling & Scattering of use cases in software modules. Future Work: • Pointcut expressiveness vs. use case extensions needed. • Attempt more complicated scenario flows and re-assess results. • Add non-functional requirements. Problem: Loss of Use Case Modularity from Analysis and Design phase: well-defined structure involving Actors and Use Cases. UML UseCase to Implementationphase:use cases get dissolved into multiple, overlapping software modules. Extension, Weak Extension Base Optional Parts Implementation Mapping «extends» from Use Cases to AOP References: [1] Ivar Jacobson, “Use cases and Aspects -- Working together”. Invited Talk at AOSD 2003, Boston, USA. [2] Karl J. Lieberherr, “Adaptive Object Oriented Software The Demeter Method with propagation patterns”. PWS Publishing Company, Boston, 1996. [3] Bashar Nuseibeh and Steve Easterbrook . “Requirements Engineering: A roadmap”. ICSE 2000. * Part of this work has been funded by ABB Switzerland.