Requirements modeling with the aspect-oriented user requirements notation (AoURN): a case study

  • Authors:

  • Gunter Mussbacher;Daniel Amyot;João Araújo;Ana Moreira

  • Affiliations:

  • SITE, University of Ottawa, Ottawa, ON, Canada;SITE, University of Ottawa, Ottawa, ON, Canada;CITI, FCT, Universidade Nova de Lisboa, Caparica, Portugal;CITI, FCT, Universidade Nova de Lisboa, Caparica, Portugal

  • Venue:
  • Transactions on aspect-oriented software development VII
  • Year:
  • 2010

Quantified Score

Hi-index 0.00

Visualization

Abstract

The User Requirements Notation (URN) is a recent ITU-T standard that supports requirements engineering activities. The Aspect-oriented URN (AoURN) adds aspect-oriented concepts to URN, creating a unified framework that allows for scenario-based, goal-oriented, and aspect-oriented modeling. AoURN is applied to the car crash crisis management system (CCCMS), modeling its functional and non-functional requirements (NFRs). AoURN generally models all use cases, NFRs, and stakeholders as individual concerns and provides general guidelines for concern identification. AoURN handles interactions between concerns, capturing their dependencies and conflicts as well as the resolutions. We present a qualitative comparison of aspect-oriented techniques for scenario-based and goal-oriented requirements engineering. An evaluation carried out based on the metrics adapted from literature and a task-based evaluation suggest that AoURN models are more scalable than URN models and exhibit better modularity, reusability, and maintainability.