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 framework. Minimal changes to URN ensure that requirements engineers can continue working with goal and scenario models expressed in a familiar notation. At the same time, 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 (NFRs), use cases, and stakeholder goals. As AoURN expresses concern composition rules with URN itself, it is possible to describe rules in a highly flexible way that is not restricted by any specific composition language. Aspects can improve the modularity, reusability, scalability, and maintainability of URN models. Considering the strong overlap between NFRs and crosscutting concerns, aspects can help bridge the gap between goals and scenarios. On the other hand, Early Aspects (EA) research can benefit from a standardized way of modeling concerns with AoURN.
- 24 Jun 2008
- 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: Aspects in Goal and Scenario Models |
| Authors || G. Mussbacher |
| Type || Conference |
| Conference/Journal Title || Models in Software Engineering - Workshops and Symposia at MoDELS 2007 |
| Volume/Number || LNCS 5002 |
| Editors || H. Giese |
| Publisher || Springer |
| Month || June |
| Year || 2008 |
| Pages || 305-316 |
| DOI || 10.1007/978-3-540-69073-3_32 |
| Keywords || Aspect-oriented Requirements Engineering, Aspects, Use Case Maps, Goal-oriented Requirement Language, User Requirements Notation |