Wes wrote:
I would add a reference to the policy from the Service Description to
indicate association. I agree services have policy, but it is the
Service Description that points to the policy at design time and the
services use them at run-time.
DN: This is not needed since if a service has a policy, and a service
description described a service, then the service description can
described the service policy. It is not necessary to make lines between
every concept.
I would also add a transient run-time agreement (with a lifetime
attribute) entity as part of the interaction within the execution
context.
DN: That can be described in the text. With graphics like these, we
have to stick to a consistent level of granularity for all elements of
the graph. The text accompanying them can describe each one on more
detail.
Duane
