-
Key: SOAML11-8
-
Legacy Issue Number: 15322
-
Status: open
-
Source: SINTEF ( Brian Elvesæter)
-
Summary:
On page 40 it is stated that "Capabilities represent an abstraction of the ability to affect change" and there is a lot of explanation why modelling capabilities makes sense on what I perceive to be the business perspective on an SOA.On page 63 it is stated that "Alternatively, Capabilities may realize ServiceInterfaces using standard UML Realization. This approach is somewhat different in that it says that the Service Interface is a "specification" and the Capability "implements" this specification."In my view here the concept "capability" is used on two different abstraction levels: 1) abstract business view, and 2) IT implementation view. This should be avoided!
-
Reported: SoaML 1.0 — Thu, 1 Jul 2010 04:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT