|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Dean Kuo, Alan Fekete, Paul Greenfield, Surya Nepal, John Zic, Savas Parastatidis, Jim Webber, "Expressing and Reasoning about Service Contracts in Service-Oriented Computing," 2012 IEEE 19th International Conference on Web Services, pp. 915-918, IEEE International Conference on Web Services (ICWS'06), 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/ICWS.2006.62, author = {Dean Kuo and Alan Fekete and Paul Greenfield and Surya Nepal and John Zic and Savas Parastatidis and Jim Webber}, title = {Expressing and Reasoning about Service Contracts in Service-Oriented Computing}, journal ={2012 IEEE 19th International Conference on Web Services}, volume = {0}, year = {2006}, isbn = {0-7695-2669-1}, pages = {915-918}, doi = {http://doi.ieeecomputersociety.org/10.1109/ICWS.2006.62}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - CONF JO - 2012 IEEE 19th International Conference on Web Services TI - Expressing and Reasoning about Service Contracts in Service-Oriented Computing SN - 0-7695-2669-1 SP915 EP918 A1 - Dean Kuo, A1 - Alan Fekete, A1 - Paul Greenfield, A1 - Surya Nepal, A1 - John Zic, A1 - Savas Parastatidis, A1 - Jim Webber, PY - 2006 KW - null VL - 0 JA - 2012 IEEE 19th International Conference on Web Services ER - | |||
The Web Services and Service-Oriented Architectures (SOA) vision [6] is about building large-scale distributed applications by composing coarse-grained autonomous services in a flexible architecture that can adapt to changing business requirements. These services interact by exchanging one-way messages through standardised message processing and transport protocols. This vision is being driven by economic imperatives for integration and automation across administrative and organisational boundaries.
Service contracts play a critical role in SOA. They describe the functionality a service exposes to other services on the network. A contract defines the outgoing and incoming messages the service can send and receive, and the order in which they are sent and received (messaging behaviour). It provides developers and tools with the metadata to compose services into service-oriented applications.
This paper presents a concise yet expressive model for service contracts to describe messaging behaviour. The idea is simple: we use Boolean conditions to specify when a message can be sent and received, where the conditions refer only to other messages in the service contract that is, conditions only refer to a service?s externalised messaging state and not to internal state.