Use case maps for object-oriented systems
Use case maps for object-oriented systems
Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
N degrees of separation: multi-dimensional separation of concerns
Proceedings of the 21st international conference on Software engineering
Crosscutting quality attributes for requirements engineering
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
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)
Modeling and Composing Scenario-Based Requirements with Aspects
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Aspect-Oriented Analysis and Design
Aspect-Oriented Analysis and Design
Aspect-Oriented Software Development with Use Cases (Addison-Wesley Object Technology Series)
Aspect-Oriented Software Development with Use Cases (Addison-Wesley Object Technology Series)
Composing aspect models with graph transformations
Proceedings of the 2006 international workshop on Early aspects at ICSE
Visualizing Aspect-Oriented Requirements Scenarios with Use Case Maps
REV '06 Proceedings of the 1st international workshop on Requirements Engineering Visualization
Visualizing early aspects with use case maps
Transactions on aspect-oriented software development III
Towards integrated tool support for the user requirements notation
SAM'06 Proceedings of the 5th international conference on System Analysis and Modeling: language Profiles
Visualizing Aspect-Oriented Goal Models with AoGRL
REV '07 Proceedings of the Second International Workshop on Requirements Engineering Visualization
Modeling software product lines with AoURN
Proceedings of the 2008 AOSD workshop on Early aspects
Aspect-Oriented User Requirements Notation: Aspects in Goal and Scenario Models
Models in Software Engineering
On modeling interactions of early aspects with goals
EA '09 Proceedings of the 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design
Visualizing early aspects with use case maps
Transactions on aspect-oriented software development III
Extending the user requirements notation with aspect-oriented concepts
SDL'09 Proceedings of the 14th international SDL conference on Design for motes and mobiles
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 aspect-orientation and multi-dimensional separation of concerns have given software engineers tools to better encapsulate concerns throughout the software lifecycle. Separated concerns must be composed, even during early lifecycle phases, to obtain an overall system understanding. Concern composition languages therefore must be expressive, scalable, and intuitive. Otherwise, gains achieved by concern separation are offset by the complexity of the composition rules. This paper focuses on a composition language for the requirements modeling phase and, in particular, on composition of concerns described with use cases or scenarios. We propose that existing composition techniques (such as before and after advices from AOP) are insufficient for requirements model composition because they do not support all composition rules frequently required for use cases or scenarios. Furthermore, composition rules for a modeling language should be visual and use the same notation as the modeling language. This paper presents Aspect-oriented Use Case Maps (AoUCM) and evaluates its flexible, expressive, and exhaustive composition technique. Moreover, the composition rules are expressed in the same notation already used for UCMs. The usefulness and necessity of our composition rules are demonstrated through examples modeled with the jUCMNav tool.