Technologies based on aspects and applied at the early stages of software development allow requirements engineers to better encapsulate crosscutting concerns in requirements models. The Aspect-oriented User Requirements Notation (AoURN) extends the User Requirements Notation (URN) with aspects and thus unifies goal-oriented, scenario-based, and aspect-oriented concepts in one graphical framework. As URN is a standard of the International Telecommunication Union, AoURN is the first standards-based and graphical approach that integrates the three aforementioned techniques. Minimal changes to URN ensure that requirements engineers can continue working with goal and scenario models expressed in a familiar notation. With AoURN, concerns in goal and scenario models, regardless of whether these concerns crosscut or not, can be managed across model types. Typical concerns in URN are non-functional requirements, use cases, and stakeholder goals. As AoURN expresses concern composition rules with URN itself, it is possible to describe rules in an exhaustive and highly flexible way that is not restricted by any specific composition language. In addition, AoURN employs a composition technique that is not based solely on language syntax but takes semantics into account, and therefore is more robust to refactoring of an aspect-oriented model. Since composition based on semantics requires precisely defined languages, the semantics of URN is clarified and the concrete syntax enhanced to capture identified semantic variations of the language. A qualitative comparison of aspect-oriented techniques for scenario-based and goal-oriented requirements engineering is presented. 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. A proof-of-concept implementation of AoURN in the jUCMNav tool is also discussed. While AoURN’s ability to encapsulate concerns across model types further bridges the gap between goals and scenarios, Early Aspects research benefits from a standardized way of modeling concerns with AoURN.
- Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.
| Title || Aspect-Oriented User Requirements Notation |
| Authors || Gunter Mussbacher |
| Type || Thesis |
| Conference/Journal Title || Ph.D. in Computer Science |
| Volume/Number || |
| Editors || |
| Publisher || EECS, University of Ottawa, Canada |
| Month || November |
| Year || 2010 |
| Pages || 341 |
| DOI || |
| Keywords || User Requirements Notation, URN, Aspects, Use Case Maps, UCM, Goal-oriented Requirement Notation, GRL, AoURN, AoUCM, AoGRL |