[aosd-discuss] Aspects in Early Stages
marash at comp.lancs.ac.uk
Fri Mar 7 09:40:52 EST 2003
In addition to the Early Aspects Workshops (as suggested by Stan) you might
also find the following papers useful:
S. M. Sutton and I. Rouvellou, "Modeling of Software Concerns in Cosmos",
International Conference on Aspect-Oriented Software Development, 2002, ACM,
Rashid, A. Moreira, and J. Araujo (2003). Modularisation and Composition of
Aspectual Requirements, 2nd International Conference on Aspect-Oriented
Software Development, ACM, pp. 11-20.
Rashid, A., P. Sawyer, A. Moreira and J. Araujo (2002). Early Aspects: A
Model for Aspect-Oriented Requirements Engineering. IEEE Joint International
Conference on Requirements Engineering, IEEE Computer Society Press 199-202.
J. Grundy, "Aspect-Oriented Requirements Engineering for Component-based
Software Systems", 4th IEEE International Sympsium on RE, 1999, IEEE
Computer Society Press, pp. 84-91.
From: discuss-admin at aosd.net [mailto:discuss-admin at aosd.net]On Behalf Of
suttonsm at verizonesg.net
Sent: 07 March 2003 01:46
To: discuss at aosd.net
Subject: Re: [aosd-discuss] Aspects in Early Stages
Absolutely it is possible. At the early stages you may or may not be able
to predict the concerns that will be crosscutting at later stages, but
plenty of concerns are crosscutting at early stages.
To have aspects all you need is a decomposition according to one concern
dimension and some representation of another concern dimension that
crosscuts that. Dominant decompositions can be found in any early stage
representation, e.g., by object class in a domain model and by use case in
the functional requirements. But use cases may crosscut domain object
classes, and domain object classes may crosscut use cases.
If you know that you will be using an object-oriented approach to
implementing your system, you can guess that certain nonfunctional and even
some functional concerns will crosscut the object hierarchy. (If you are
using a functional implementation, then you can guess that some objects may
crosscut the functional hierarchy.)
If you are interested in aspects at the early stages of development, you
may want to investigate the Early Aspects workshops that are held in
conjunction with the AOSD conference:
Early Aspects 2002:
Early Aspects 2003:
suttonsm at verizonesg.net
> Hi Friends,
> Is it really possible to identify aspects in early stages of software
> development like requirements analysis? Or crosscutting concerns are
> typical of the late stages?
> Anderson Davis
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss