Theme: An Approach for Aspect-Oriented Analysis and Design
Elisa Baniassad
Abstract
Elisa Baniassad
Abstract
Aspects are behaviours that are tangled and scattered across a system. In requirements documentation, aspects manifest themselves as descriptions of behaviours that are intertwined, and woven throughout. Some aspects may be obvious, as specifications of typical crosscutting behaviour. Others may be more subtle, making them hard to identify. In either case, it is difficult to analyse requirements to locate all points in the system where aspects should be applied. These issues lead to problems achieving traceability of as-pects throughout the development lifecycle. To identify as-pects early in the software lifecycle, and establish sufficient traceability, developers need support for aspect identifica-tion and analysis in requirements documentation. To ad-dress this, we have devised the Theme approach for viewing the relationships between behaviours in a requirements doc-ument, identifying and isolating aspects in the requirements, and modelling those aspects using a design language. This paper describes the approach, and illustrates it with a case study and analysis. 1.
OpenAlex reports 277 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Aspects are behaviours that are tangled and scattered across a system. In requirements documentation, aspects manifest themselves as descriptions of behaviours that are intertwined, and woven throughout. Some aspects may be obvious, as specifications of typical crosscutting behaviour. Others may be more subtle, making them hard to identify. In either case, it is difficult to analyse requirements to locate all points in the system where aspects should be applied. These issues lead to problems achieving traceability of as-pects throughout the development lifecycle. To identify as-pects early in the software lifecycle, and establish sufficient traceability, developers need support for aspect identifica-tion and analysis in requirements documentation. To ad-dress this, we have devised the Theme approach for viewing the relationships between behaviours in a requirements doc-ument, identifying and isolating aspects in the requirements, and modelling those aspects using a design language. This paper describes the approach, and illustrates it with a case study and analysis. 1.
Key concepts: Traceability, Documentation, Computer science, Theme (computing), Requirements traceability, Identification (biology), Aspect-oriented programming, Software engineering