Abstract

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.

Discussion

FormForVirtualLibrary edit

Title Aspect-Oriented User Requirements Notation
Authors Gunter Mussbacher
Type Conference
Conference/Journal Title Models 2007 Doctoral Symposium
Volume/Number
Editors
Publisher
Month October
Year 2007
Pages
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
Topic revision: r4 - 06 Nov 2009, AzaliaShamsaei
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback