There has been a recent discussion in connection with several issues that questioned the clarity of Figures 13, 14, and 26 in the 06 July 2011 public review draft. In addition to text added to sections 4.1.1.3 and 4.1.1.3.1, the following will be done to resolve the issues.
1. Figures 14 and 26 have an <<interface>> stereotype on the service interface class. In both of those, this is description of the service interface and not the interface itself, as the stereotype would indicate. The stereotype will be removed.
2. One could interpret Figure 13 (and the others) as saying the service interface (the thing) has Behavior and Information models, and this implies independent functionality rather than access to the functionality of the underlying capability. Making it clear that we are talking about service interface description and not the service interface thing is important. “Service Interface” in the models will be changed to “Service Interface Description” (and <<interface>> removed).
3. A service can have Behavior models but a given interface may not make use of all things in a more inclusive model. There was a concern that we are implying every service interface implements everything in the models. The surrounding wording will be examined for ways to make it clear the description must clearly provide relevant information and how the Behavior and Information Models support that but the ideas presented are meant to be an abstract discussion of description and not the operational details for a given service.
These changes will be implemented in the current revisions.
Ken
---------------------------------------------------------------------------
Dr. Kenneth Laskey
MITRE Corporation, M/S H305 phone: 703-983-7934
7515 Colshire Drive fax: 703-983-1379
McLean VA 22102-7508