Skip to main content
Article thumbnail
Location of Repository

On identifying and representing aspects

By Saqib Iqbal and Gary Allen


Identification of cross-cutting concerns (Aspects)\ud 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 paper discusses some of these methods and suggested approaches, and provides a constructive\ud critique on Aspects as Use Cases, View-Point based system of identifying Aspects, and Use Cases as Concerns. This paper also suggests a model-oriented approach for identifying and representing Aspects throughout the development life cycle

Topics: QA75
Year: 2009
OAI identifier:

Suggested articles


  1. (2005). A ConcernOriented Requirements Engineering Model,"
  2. (2001). Agent-oriented requirements engineering using congolog and i*.
  3. (2003). Architectural views of Aspects.
  4. (1997). Aspect-Oriented Programming. doi
  5. (2005). Aspect-Oriented Software Development with Use Cases:
  6. (2002). AspectOriented Requirements with UML," presented at
  7. (2004). Concern Modeling for Aspect-Oriented Software Development," doi
  8. (2003). Concerns in a Requirements Model - A
  9. (2002). Early Aspects: Aspectoriented requirements engineering and architecture design.
  10. (2004). Finding Aspects in Requirements with Theme/Doc," presented at
  11. (2004). From Goals to Aspects: Discovering Aspects from Requirements Goal Models," doi
  12. (2003). Identifying Aspectual use cases using a viewpoint-oriented requirements method. In: Early Aspects
  13. (2002). Modeling of Software Concerns in Cosmos," doi
  14. (2003). Modularization and Composition of Aspectual Requirements," presented at doi
  15. (2000). Multi-perspective specification, design and implementation of software components using Aspects," doi
  16. (2005). MultiDimensional Separation of Concerns in Requirements Engineering," presented at doi
  17. (2004). On Getting Use Cases and Aspects to Work Together”, doi
  18. (2004). Scenario Modelling with Aspects," doi
  19. (2002). towards requirements-driven information systems engineering: doi
  20. (2003). Transformation Based Approach for Weaving Use Case Models in Aspect-Oriented Requirements Analysis.
  21. (2003). Use Cases and Aspects—Working Seamlessly Together," doi

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