Wouter Zoons wrote:
Not sure too, but somehow I feel it should. After all, "unified" is what the U in UML is supposed to mean, right ?The classical AOP examples apply here: audit logging, security, etc
That raises (for me, at least) an interesting question: how one should properly model aspects in a UML model ?
[WZ> ] I personally consider aspects to describe non-functional
requirements, not sure that should go into a UML model (but I guess it could
somehow)
Even when they would be functional they're easy enough to implement by handI like to think that the job AndroMDA does is akin an engine that aplies aspects to a UML model.
(as opposed to trying to model them in UML)
Don't know though how to explore this concept further. Maybe in future versions AndroMDA, which today
is stereotype-driven, could explore the metamodel, so one would be able to trigger code generation from
a metadata expression.
OK. TGIF.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
