AOM in UML

[jeshaw2]

I've been considering the modeling of cross cutting concerns in UML.  My moniker for this is Aspect Oriented Modeling [AOM].  At present, I'm looking at how AOM may be accomplished in State Diagrams.  For example, consider the login-granted privileges that constrain the states and transitions available to a user of an application.

I'm wondering:

• Has anyone in this forum has given consideration to this topic and found a way to accomplish this?
• Would you consider a privilege to be a state?
• How would you handle modeling concurrent privileges?
• Would you consider the granting of multiple privileges to be multiple concerns or a composite concern?
• What approach would you take?

Thank you
Jim

[«Midnight»]

Priviledge as in what allows a role to do what it may?

[jeshaw2]

Priviledge as in what allows a role to do what it may?

Yes.  Perhaps some users may only read, others might be allowed to update information, etc.

[thomaskilian]

I'm wondering:

• Has anyone in this forum has given consideration to this topic and found a way to accomplish this?

Not yet

• Would you consider a privilege to be a state?

Not really. A privilege is a class (aka token or key) which allows access to certain areas.

• How would you handle modeling concurrent privileges?

This is means of the class implementation. A key chain is a good example.

• Would you consider the granting of multiple privileges to be multiple concerns or a composite concern?

Taking the key chain you have one key per secured object. This is best represented as a n-m relation.

• What approach would you take?

See above.

[jeshaw2]

Not really. A privilege is a class (aka token or key) which allows access to certain areas.

Agreed. However, once access has been granted to certain (cross cutting) areas, the system transitions into a state where such access is activated.

[thomaskilian]

Okay. But for what purpose do you want to model this system state? I probably miss here some background.

[jeshaw2]

Okay. But for what purpose do you want to model this system state? I probably miss here some background.

My example of login privileges is only an instance of a more abstract issue;  that of Aspect Oriented System Design [AOSD]. If you need back ground on that try this link to  Aspect Oriented Programming

I'm interested in the more abstract issue of modeling Cross Cutting Concerns in UML.    Jacobson demonstrates AOSD at the Use Case Level where use case Slices keep concerns separated.  It would seem useful to produce Protocol State Charts that support the Use Case Slices.

Does this help Thomas?

[thomaskilian]

Phew - looks like a lot of background I'm missing here. I had a quick look at the text you referenced and I will probably not be able to give you a meaningful feedback on a short term (Well, actually it looks like a new aspect of the wheel to me and I currently can't afford the time to study that aspect in more detail.)

[jeshaw2]

Understandable Tom.  

Although there is a growing advocacy for AOP, it is still (commercially)an emerging technology.  

I just enjoy living on the bleeding edge.  

[thomaskilian]

I know. Most times it's like professors talk when you're communicating with Paolo. Maybe he will take over the discussion