[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [soa-rm-ra] Disambiguating Action (Part I)
|
On May 26, 2008, at 1:38 PM, michael.poulin@uk.fid-intl.com wrote:
The service interface is one aspect needed for effective interaction. �As I said in my original email on 21 May As shown in Figure 20, the service description provides information on:� - what a service does (its functionality and the resulting real world effects),� - how to reach the service (protocols and the endpoint of service reachability),� - how to communicate with the service (the information and behavior models that make up the service interface), - what are the conditions of use (service policies and contracts), and - what measurements of performance are available and how can these be accessed (service metrics).
There is not necessarily a one-to-one correlation between needs and capabilities; the granularity� of needs and capabilities vary from fundamental to complex, and any given need may require the� combining of numerous capabilities while any single capability may address more than one need.� This was in the discussion of SOA before service was introduced, but it follows that you can get multiple RWE from interaction with a single "operation"/"action"/TBD. �For example, my accepting the terms of your proposed sale of something to me makes the thing mine and some of my money yours (pending appropriate completion).
----------------------------------------------------------------------------- Ken Laskey MITRE Corporation, M/S H305� � ��phone: 703-983-7934 7515 Colshire Drive�� � � � � � � � � � � ��fax:�� � ��703-983-1379 McLean VA 22102-7508 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]