Skip to main content
Article thumbnail
Location of Repository

Representing Aspects in Design

By Saqib Iqbal and Gary Allen

Abstract

Identification of cross-cutting concerns (Aspects) in the earliest phases of software development has gained in popularity over recent years. Many approaches have been suggested for identifying and representing Aspects in abstraction and design structures. Since these approaches are still relatively immature, shortcomings such as overlooking or not properly locating Aspects have been noted in almost all of these approaches. This research proposes an Aspect- Oriented Software Development Model which helps identifying Aspects at the early stages of software development and guides the way to interpret these Aspects into Design elements and finally provides a support to weave Aspects into Base program

Topics: QA75
Publisher: IEEE
Year: 2009
OAI identifier: oai:eprints.hud.ac.uk:5517

Suggested articles

Citations

  1. (2001). Agent-oriented requirements engineering using congolog and i*.
  2. (2003). Architectural views of Aspects.
  3. (1997). Aspect-Oriented Programming. doi
  4. (2003). Concerns in a Requirements Model - A Small Case Study," presented at Early Aspects
  5. (2002). Early Aspects: Aspectoriented requirements engineering and architecture design.
  6. (2003). Identifying Aspectual use cases using a viewpoint-oriented requirements method. In: Early Aspects
  7. (2003). Modularisation and Composition of Aspectual Requirements," presented at doi
  8. (2002). Towards requirements-driven information systems engineering: doi
  9. (2003). Transformation Based Approach for Weaving Use Case Models in Aspect-Oriented Requirements Analysis.

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.