Contributed Service contract template document.
Jason Bloomberg, President of ZapThink, will be delivering this two-day workshop in London on March 15 & 16, 2012, in partnership with IRM UK.
Click here for more information and to register!
Architecture Artifact
Service Contract Template example
Discussion
5 comments for “Service Contract Template example”
Post a comment
FREE POSTERS
ZapThink's Vision for Enterprise IT in 2020
10-pack of prints for just $29.95*
SOA Implementation Roadmap
10-pack of prints for just $29.95*
Copyright © 2012 ZapThink, a Dovèl Technologies Company. 
I’ve been looking through the contract template, and have a couple of questions:
1. Can you please clarify the role of the Security – Integrity classification section? More specifically, I am not familiar with the classification levels listed (I1 -> I4 Double Intervention). Are you able to clarify?
2. For the Quality of service, what is the difference between the Capacity/Performance and Handling Time Characteristics?
That document was provided by one of our LZAs, but unfortunately, he hasn’t joined this site yet. So, can anyone else respond to Rohan’s questions?
This is an important artifact on the LZA Web site, as it’s a real-world contribution, not just an exercise. So if we can generate a discussion around it, that should be helpful to everybody.
Thanks!
– Jason
Indeed – I would be interested in any thoughts on that front.
Some other items that may be candidates for inclusion:
- WS* standards implemented.
- In the input/output sections, instead of simply indicating a field is mandatory or not, indicate cardinality.
- Potentially a RACI matrix could be included in the contact section to indicate who should be informed etc in the event of a change to the service.
- Where the service fits in the service business classification and model should be clearly stipulated. This will often influence how the service can be used.
Can someone please answer/clarify the following question related to the service interface:
Lets say I have a service which expects certain data (eg. inputXML, docType and CityName) and returns a boolean value and my service has been made inteoperable by defining it as a webservice. What will be my service interface?
1. Service Inputs & Outputs along with WSDL.
2. WSDL only.
The technical aspects of your “service interface” will be defined by your WSDL, the XML Schema that it references, and the WS-Policy that is associated with it. This will define the parameters and types associated with each operation in the service interface; i.e., the syntax for using the service.
The “service contract” is more holistic and includes (through references) the WSDL, XML Schema, and WS-Policy, but also includes non-syntactical items like pre/post-conditions and conceptual concepts like subject vocabulary (semantic model).
Your “service contract” should describe the inputs and outputs (among other things) and provide a reference to the technical interface definition (i.e., WSDL).
Your “WSDL” will only provide the technical aspects of how the service is called (sometimes that and a few comments is good enough).