A Comprehensive Aspect-Oriented Use Case Method for Modeling Complex Business Requirements
The aspect-oriented approach separates cross-cutting concerns and models them as aspects. In this paper, we present a comprehensive aspect-oriented use case approach for modeling complex business requirements. We identify four categories of aspects: high level non-functional requirements, extending or optional requirements, included or subordinate requirements, and business rules. Our aspect-oriented use-case model comprises three different templates: base use cases, aspectual use cases, and nonfunctional aspects. The proposed method offers a systematic approach for identifying different potential aspects from complex business requirements. Moreover, our method provides a comprehensive model for documenting identified aspects and their composition to the core functionalities at an early stage of software development. The contributions of our paper include identifying and utilizing the four types of aspects and proposing the templates to document them.
KeywordsEarly Aspects Aspect-oriented modeling Aspect-oriented system development aspect-oriented use case method Aspect template
Unable to display preview. Download preview PDF.
- 1.Araújo, J., Moreira, A., Brito, I., Rashid, A.: Aspect-Oriented Requirements with UML. In: Workshop on Aspect-Oriented Modelling with UML, Dresden, Germany, pp. 1–6 (2002)Google Scholar
- 2.Araújo, J., Coutinho, P.: Identifying aspectual use cases using a viewpoint-oriented requirements method. In: Early Aspects: Aspect Oriented Requirements Engineering and Architecture Design, Boston (2003)Google Scholar
- 3.Jacobson, I., Ng, P.-W.: Aspect-oriented Software Development with Use Cases. Addison Wesley, Boston (2005)Google Scholar