Mahmud, ShafquatWalker, Rob2008-02-272008-02-272004-12-20http://hdl.handle.net/1880/46087AOSD aims at improving key software engineering properties (such as traceability, comprehensibility, and evolvability) through the separation and modularization of crosscutting concerns. The majority of AOSD research focuses on individual software engineering activities (such as implementation or requirements) in isolation. One exception to this trend is the Theme approach of Clarke and colleagues, which considers the derivation of implementations from requirements through design. Evidence is currently meager for or against the claims to this approach. This paper describes a case study involving the development and evolution of a benchmark system to evaluate these claims. Alternative decision are examined to consider whether one or more feasible development processes exist in applying Theme. Lessons learned from the study are discussed for their generalizability to other scenarios.EngComputer Scienceunknown2004-765-3010.11575/PRISM/31116