Writing Effective Use Cases
ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
ASAAM: Aspectual Software Architecture Analysis Method
WICSA '04 Proceedings of the Fourth Working IEEE/IFIP Conference on Software Architecture
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)
A Dynamic Component and Aspect-Oriented Platform
The Computer Journal
An Aspect Oriented Model Driven Framework
EDOC '05 Proceedings of the Ninth IEEE International EDOC Enterprise Computing Conference
IEEE Software
XWeave: models and aspects in concert
Proceedings of the 10th international workshop on Aspect-oriented modeling
An automatic transformation from COSA software architecture to CORBA platform
NOTERE '08 Proceedings of the 8th international conference on New technologies in distributed systems
Using AOSD and MDD to Enhance the Architectural Design Phase
OTM '09 Proceedings of the Confederated International Workshops and Posters on On the Move to Meaningful Internet Systems: ADI, CAMS, EI2N, ISDE, IWSSA, MONET, OnToContent, ODIS, ORM, OTM Academy, SWWS, SEMELS, Beyond SAWSDL, and COMBEK 2009
On the symbiosis of aspect-oriented requirements and architectural descriptions
Proceedings of the 10th international conference on Early aspects: current challenges and future directions
Transactions on aspect-oriented software development IV
Deriving detailed design models from an aspect-oriented ADL using MDD
Journal of Systems and Software
Hi-index | 0.00 |
Aspect-Oriented (AO) Software Development has been created to offer improved separation of concerns mechanisms. AO concepts first appeared at the programming level and are now being addressed at the early stages of the software development life cycle. Currently, there are several AO approaches available for the various software development phases, but each one usually encompasses a single phase of the software process. This results in a wide gap between proposals at different levels of abstractions, raising several problems when trying to map artifacts between proposals from adjoining levels. This gap is clearly noticeable when an AO architecture design is intended to be derived from an AO requirements specification, since some requirements artifacts in AO approaches cannot be easily mapped to architectural artifacts. This paper explains how to reduce this gap by using model transformations between AO requirements engineering models and AO architecture design models. The goal is to automate part of the process of deriving an AO software architecture from an AO requirements specification.