Use case maps for object-oriented systems
Use case maps for object-oriented systems
Quality-driven software architecture composition
Journal of Systems and Software - Special issue on: Software architecture - Engineering quality attributes
Introduction to the user requirements notation: learning by example
Computer Networks: The International Journal of Computer and Telecommunications Networking - ITU-T system design languages (SDL)
Modelling strategic relationships for process reengineering
Modelling strategic relationships for process reengineering
From Goals to Aspects: Discovering Aspects from Requirements Goal Models
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Weaving Multiple Viewpoint Specifications in Goal Oriented Requirements Analysis
APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference
Visualizing Aspect-Oriented Requirements Scenarios with Use Case Maps
REV '06 Proceedings of the 1st international workshop on Requirements Engineering Visualization
Visualizing Aspect-Oriented Goal Models with AoGRL
REV '07 Proceedings of the Second International Workshop on Requirements Engineering Visualization
Flexible and expressive composition rules with aspect-oriented use case maps (AoUCM)
Proceedings of the 10th international conference on Early aspects: current challenges and future directions
Visualizing early aspects with use case maps
Transactions on aspect-oriented software development III
An expressive aspect composition language for UML state diagrams
MODELS'07 Proceedings of the 10th international conference on Model Driven Engineering Languages and Systems
Conceptual Modeling: Foundations and Applications
Refactoring-Safe Modeling of Aspect-Oriented Scenarios
MODELS '09 Proceedings of the 12th International Conference on Model Driven Engineering Languages and Systems
Requirements modeling with the aspect-oriented user requirements notation (AoURN): a case study
Transactions on aspect-oriented software development VII
Requirements modeling with the aspect-oriented user requirements notation (AoURN): a case study
Transactions on aspect-oriented software development VII
| Hi-index | 0.00 |
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.