Re: [service-orientated-architecture] ZapThink needs help: Sample contracts?

[Ron Schmelzer]

So, do you have any concrete and real-world examples of Role Activity Diagrams? We see a lot of talk about contracts in academia and theory and analyst-speak (we do lots of that, too ;) But, this time around, we want practicality. So, I put it on the table for you Keith: do you have any real world examples of these Role Activity Diagrams and how to specifically map it to the problem at hand with Service contracts? Theory is great, but customers want real stuff now. Best, Ron Keith Harrison-Broninski wrote: Ron I would say that the metadata you describe are all business process issues rather than technical ones.  We deal with them via the construction of "Role Activity Diagrams" that describe an agreement between parties on the future operation of the process.  The diagrams are not IT but business-oriented - moreover they are generally very concise and simple for anyone to understand. If Gervas will forgive a plug in this forum, my recent book provides a complete methodology not only for construction of such diagrams but for using them to manage process change.  The book provides various examples of agreements between parties, although these tend to be focused more on human-human collaboration than on the system-system collaboration typical of current SOA implementations.  However, we did use the technique with success in a mechanistic financial services application based on SOA, although unfortunately the details are confidential so I can't supply them for your research.  There are links to books and articles describing the method at: http://www.rolemodellers.com/abstracts -- All the best Keith http://keith.harrison-broninski.info Ron Schmelzer wrote: >Hi All -- > >As you all know, one of the key parts to making loosely coupled Services >work is a well-defined contract that identifies both functional as well >as non-functional requirements for Service providers and consumers. By >now, you also probably realized that WSDL by itself is not sufficient to >provide all the metadata needed for loose coupling and late binding. >Other metadata are needed including security, semantics, QoS, SLA, >process, etc. > >So, what we are looking for are actual examples of real-world contracts, >or templates for contracts that you are using in real-world SOA >deployments, or at the very least, guidance for how those contracts can >be defined. > >So, help anyone? > >Thanks in advance! >Best, >Ron > >  > -- _____________________________________________________________ Ronald Schmelzer [EMAIL PROTECTED] Senior Analyst ZapThink LLC Direct: 781-577-2779 / Main: 781-207-0203 SPONSORED LINKS Service-oriented architecture Computer monitoring software Computer and internet software Free computer monitoring software YAHOO! GROUPS LINKS  Visit your group "service-orientated-architecture" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.