Early Aspects 2004: Aspect-Oriented Requirements Engineering and Architecture Design
Gazebo II
Monday, 8:30, full day | 7 | · | 8 | · | 9 | · | 10 | · | 11 | · | 12 | · | 13 | · | 14 | · | 15 | · | 16 | · | 17 | · | 18 | · | 19 | · | 20 | · | 21 |
Ana Moreira, Universidade Nova de Lisboa
Awais Rashid, University of Lancaster
Elisa Baniassad, Trinity College
Bedir Tekinerdogan, University of Twente
Paul Clements, Carnegie Mellon University
Joao Araujo, Universidade Nova de Lisboa
http://www.early-aspects.net/events/oopsla04ws
Object-orientation increases the quality of software applications by localizing concerns in separate classes. Unfortunately, many concerns cannot be localized in separate classes, and instead cut across them. Crosscutting reduces the maintainability and adaptability of object-oriented applications. Aspect-orientation provides aspects to represent those concerns separately.
Most work in aspect-orientation has focused on handling aspects at the programming level. Waiting until implementation to manage aspects results in less system maintainability, and evolvability, since early design decisions have a large impact on the whole system. Traceability is also a problem: concerns handled at the code level are not adequately reflected or specified in the requirements, or vice-versa.
Early aspects is an emerging research area, which focuses on managing aspects during requirements engineering and architecture design. The identification, specification and validation of aspects early in the life cycle will help to improve the quality of object-oriented and aspect-oriented applications. This workshop provides a forum for discussion on the issues raised above.
|
