Handling unanticipated requirements change with aspects

Abstract. Supporting software evolution and maintenance are two of the major issues of aspect-oriented software development. This paper adds to aspect-orientation by proposing (i) a classification of concerns, (ii) volatile concerns to be kept separately and handled as candidate aspects independently of the crosscutting property, (iii) the use of adaptable use cases and activity diagrams to cope with generic model elements that facilitate the composition of concerns, (iv) the extension of the use case model to support our ideas. 1