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 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.
- Please contact email@example.com if you want a copy of this paper.
- Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.
| Title || Requirements Modeling with the Aspect-oriented User Requirements Notation (AoURN): A Case Study |
| Authors || G. Mussbacher, D. Amyot, J. Araújo, and A. Moreira |
| Type || Journal |
| Conference/Journal Title || Transactions on Aspect-Oriented Software Development VII |
| Volume/Number || LNCS 6210 |
| Editors || J. Kienzle |
| Publisher || Springer |
| Month || - |
| Year || 2010 |
| Pages || 23-68 |
| DOI || 10.1007/978-3-642-16086-8_2 |
| Keywords || Aspect-Oriented Requirements Engineering, Aspect-oriented User Requirements Notation, Scenario-based Modeling, Goal-oriented Modeling |