SPTP — use of multiple stereotype

I find the use of multiple stereotypes just to get the tags required to do a simple global RMA analysis, plus all the indirection necessary. ugly, ugly, ugly. A thought occurred to me - why not highly-specific analysis subprofiles, where we would define a set of stereotypes like <<RMAG_Task>> which would be <<CRConcurrnent>>, <<SASchedulable>> and <<SAAction>> all bundled together? (RMA Global is where I got RMAG). Thus we could stereotype elements such as active objects and resources very simply. A small set of internally consistent tags with the right properties that map specifically to the kind of analysis to be perform would make the profile much easier to use.

Closed, no change