[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [soa-rm-ra] about contract for the Management Model section
--------------------------------------------------------------------------- Dr. Kenneth Laskey MITRE Corporation, M/S H305 phone: 703-983-7934 7515 Colshire Drive fax: 703-983-1379 McLean VA 22102-7508 From: mpoulin@usa.com [mailto:mpoulin@usa.com] Hello All, here is the re-worded fragment of the Management Model section related to the contracts based on the recent e-mail exchange . Please, review it before I place it into the section text. - Michael As described in sections “Participation in a SOA Ecosystem view” and “Realization of a SOA Ecosystem view”, there are several types of contractual information in the SOA ecosystem. From the management perspective, three basic types of the contractual information relate to: · relationship between service provider and consumer; · communication with the service; · control of the quality of the service execution.
a service contract is an implicit or an explicit and documented agreement between the service consumer and service provider about the use of the service based on the commitment by a service provider to provide service functionality and results [kjl] Michael, this paragraph mixes two things and I’m don’t have time right now to work a polished set of suggestions. Basically, the service description may identify alternatives. This is independent of whether we end up with an implicit or explicit contract. The actions of the participants can indicate the alternative chosen without an explicit contract. The service description provides the basis for the service contract and, in some situations, In the case of business services, it is anticipated that the service contract may take an explicit form and the agreement between business consumer and business service provider is formalized. Formalization requires up-front interactions between service consumer and service provider. In many business interactions, especially between business organisations within or across corporate boundaries, a consumer needs a contractual assurance from the provider or wants to use only a subset of the business functionality offered by the service and pay a prorated cost for this, which is possible to set via an explicit contract. So, an implicit service contract is an agreement (1) on the consumer side with the terms, conditions, features and interaction means specified in the service description "as is" or (2) a selection from alternatives that are made available through mechanisms included in the service description, and neither of these [kjl] This misses the point that the coupling is traditional and may be needed under certain conditions but most of life is implicit. Even your return example is implicit because requiring identification has not been explicitly agreed in advance and the consumer providing ID is just following through on the implicit agreement. Any form of explicit contract couples service consumer and provider. While explicit contract may be necessary or desirable in some cases like in the supply chain management, there is a model that mixes implicit and explicit contracts. Particularly, a service provider may offer (via service description) a conditional shift from implicit to explicit contract. That is, a consumer has a choice whether to stay operate with implicit contract or to meet the condition and enter into an explicit contract that may be associated with certain fees to pay. For example, Twitter offers an implicit contract on the use of its APIs to any application with the limit on the amount of service invocations; if the application needs to use more invocations, one has to enter into the explicit contract with the provider. A well-known business example is when a consumer buys some goods in a shop using implicit contract, i.e. being agree with the shop policies and prices. However, when the purchased goods are returned, the shop enters into the explicit contract with the consumer requiring its identity and address submission. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]