Extending the User Requirements Notation with Aspect-Oriented Concepts

  • Gunter Mussbacher
  • Daniel Amyot
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5719)


In November 2008, the User Requirements Notation (URN) was approved as Recommendation Z.151 by the Standardization Sector of the International Telecommunication Union (ITU-T). URN is the first and currently only standard that supports both goal-oriented and scenario-based modeling for requirements engineering activities. The Aspect-oriented URN (AoURN) is a recent extension of URN that combines goals, scenarios, and aspects in one framework. AoURN is a candidate for future versions of the URN standard. We first summarize the basic concepts and notation of AoURN and then discuss advanced features of AoURN that are necessary for large-scale modeling. Based on our experience with AoURN modeling, we present a list of requirements including rationale for an aspect-oriented extension of Z.151 that succinctly expresses the required features to evolve URN into a complete aspect-oriented modeling framework.


User Requirements Notation Goal-oriented Requirement Language Use Case Maps Aspects Aspect-oriented Modeling Aspect-oriented Requirements Engineering Aspect-oriented User Requirements Notation 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Amyot, D., Mussbacher, G.: Development of Telecommunications Standards and Services with the User Requirements Notation. Workshop on ITU System Design Languages (2008),
  2. 2.
    Araújo, J., Coutinho, P.: Identifying Aspectual Use Cases Using a Viewpoint-Oriented Requirements Method. In: Early Aspects 2003: Aspect-Oriented Requirements Engineering and Architecture Design, Workshop of the 2nd International Conference on Aspect-Oriented Software Development, Boston (2003)Google Scholar
  3. 3.
    Araújo, J., Moreira, A.: An Aspectual Use Case Driven Approach. In: Pimentel, E., Brisaboa, N.R., Gómez, J. (eds.) VIII Jornadas de Ingeniería de Software y Bases de Datos (JISBD 2003), pp. 463–468. Alicante (2003)Google Scholar
  4. 4.
    Chitchyan, R., et al.: Survey of Analysis and Design Approaches,
  5. 5.
    Chung, L., Nixon, B.A., Yu, E., Mylopoulos, J.: Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, Dordrecht (2000)CrossRefzbMATHGoogle Scholar
  6. 6.
    Clarke, S., Baniassad, E.: Aspect-Oriented Analysis and Design: The Theme Approach. Addison-Wesley, Reading (2005)Google Scholar
  7. 7.
    The AspectJ Project,
  8. 8.
    International Telecommunication Union: Recommendation Z.150 (02/03), User Requirements Notation (URN) / Language Requirements and Framework,
  9. 9.
    International Telecommunication Union: Recommendation Z.151 (11/08), User Requirements Notation (URN) / Language definition,
  10. 10.
    Jacobson, I., Ng, P.-W.: Aspect-Oriented Software Development with Use Cases. Addison-Wesley, Reading (2005)Google Scholar
  11. 11.
    jUCMNav website, University of Ottawa,
  12. 12.
    Lencastre, M., Araújo, J., Moreira, A., Castro, J.: Towards Aspectual Problem Frames: an Example. Expert Systems Journal 25(1), 74–86 (2008)CrossRefGoogle Scholar
  13. 13.
    Mussbacher, G., Amyot, D.: Goal and Scenario Modeling, Analysis, and Transformation with jUCMNav. In: 31st International Conference on Software Engineering (ICSE 2009), Companion volume, pp. 431–432. IEEE, Los Alamitos (2009)CrossRefGoogle Scholar
  14. 14.
    Mussbacher, G., Amyot, D.: Heterogeneous Pointcut Expressions. In: Early Aspects, Workshop of the 31st International Conference on Software Engineering (ICSE 2009), Vancouver (2009)Google Scholar
  15. 15.
    Mussbacher, G., Amyot, D.: On Modeling Interactions of Early Aspects with Goals. In: Early Aspects, Workshop of the 31st International Conference on Software Engineering (ICSE 2009), Vancouver (2009)Google Scholar
  16. 16.
    Mussbacher, G., Amyot, D., Weiss, M.: Visualizing Early Aspects with Use Case Maps. In: Rashid, A., Aksit, M. (eds.) Transactions on AOSD III. LNCS, vol. 4620, pp. 105–143. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  17. 17.
    Mussbacher, G., Amyot, D., Araújo, J., Moreira, A., Weiss, M.: Visualizing Aspect-Oriented Goal Models with AoGRL. In: Second International Workshop on Requirements Engineering Visualization (REV 2007). IEEE Computer Society Press, Los Alamitos (2007)Google Scholar
  18. 18.
    Mussbacher, G., Amyot, D., Weigert, T., Cottenier, T.: Feature Interactions in Aspect-Oriented Scenario Models. In: Reiff-Marganiec, S., Nakamura, M. (eds.) Feature Interactions in Software and Communication Systems X, pp. 75–90. IOS Press, Amsterdam (2009)Google Scholar
  19. 19.
    Mussbacher, G., Amyot, D., Whittle, J., Weiss, M.: Flexible and Expressive Composition Rules with Aspect-oriented Use Case Maps (AoUCM). In: Moreira, A., Grundy, J. (eds.) Early Aspects Workshop 2007 and EACSL 2007. LNCS, vol. 4765, pp. 19–38. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  20. 20.
    Mussbacher, G., Whittle, J., Amyot, D.: Semantic-Based Interaction Detection in Aspect-Oriented Scenarios. In: 17th International Requirements Engineering Conference (RE 2009). IEEE Computer Society Press, Los Alamitos (to be published, 2009)Google Scholar
  21. 21.
    Mussbacher, G.: Aspect-Oriented User Requirements Notation: Aspects in Goal and Scenario Models. In: Giese, H. (ed.) MoDELS Workshops 2007. LNCS, vol. 5002, pp. 305–316. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  22. 22.
    Mylopoulos, J., Castro, J., Kolp, M.: Tropos: A framework for requirements-driven software development. In: Brinkkemper, J., Solvberg, A. (eds.) Information Systems Engineering: State of the Art and Research Themes, pp. 261–273. Springer, London (2000)Google Scholar
  23. 23.
    Pourshahid, A., Mussbacher, G., Amyot, D., Weiss, M.: An Aspect-Oriented Framework for Business Process Improvement. In: Babin, G., Kropf, P., Weiss, M. (eds.) MCeTech 2009. LNBIP, vol. 26, pp. 290–305. Springer, Heidelberg (2009)Google Scholar
  24. 24.
    Rashid, A., Moreira, A., Araújo, J.: Modularisation and Composition of Aspectual Requirements. In: 2nd International Conference on Aspect Oriented Software Development (AOSD), pp. 11–20. ACM Press, New York (2003)CrossRefGoogle Scholar
  25. 25.
    URN Virtual Library,
  26. 26.
    van Lamsweerde, A., Letier, E., Darimont, R.: Managing Conflicts in Goal-Driven Requirements Engineering. IEEE Transactions on Software Engineering 24(11), 908–926 (1998)CrossRefGoogle Scholar
  27. 27.
    Whittle, J., Jayaraman, P., Elkhodary, A., Moreira, A., Araújo, J.: MATA: A Unified Approach for Composing UML Aspect Models based on Graph Transformation. In: Transactions on Aspect-Oriented Software Development. LNCS. Springer, Heidelberg (to be published)Google Scholar
  28. 28.
    Yu, E.: Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering. In: 3rd IEEE International Symposium on Requirements Engineering, pp. 226–235. IEEE Computer Society Press, Los Alamitos (1997)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Gunter Mussbacher
    • 1
  • Daniel Amyot
    • 1
  1. 1.SITEUniversity of OttawaOttawaCanada

Personalised recommendations