Re: [soa-rm] Service Contract

[Michael Stiefel <development@reliablesoftware.com>]

I agree with this.

The limitations of object modelling for service orientation is the reason 
that IBM is trying to develop SOAD (Service Oriented Analysis and Design). 
Their initial paper on this concept 
(http://www-128.ibm.com/developerworks/webservices/library/ws-soad1/) 
discusses how to group loosely coupled services on the basis of their 
related behavior and processes instead of the encapsulated behavior and 
data of tightly coupled business objects.

Michael

At 11:58 AM 4/26/2005, Don Flinn wrote:
>George
>
>The diagrams in your attachment depict services and semantics in terms
>of operations and parameters.  IMHO this is a carry over from the
>original OO orientation of UML, which implies rigid, inflexible API
>based services.  Such an approach goes against the spirit of SOA, which
>IMO should be based on loosely coupled principals.   While one could
>design an SOA based on rigid APIs, I for one would not do so.  I also
>question whether the RM should encourage the API model.  I, personally,
>would go further and discourage the API based approach in a Service
>Oriented Architecture.
>
>Don
>
>IMHO this is the legacy from UML and does
>
>On Tue, 2005-04-26 at 12:52 +0100, George Ntinolazos wrote:
> > Hi all
> >
> > Please find attached a document with notes re: Service Contracts
> >
> > Cheers
> >
> > George
> >
> > ___________________________________________
> > George Ntinolazos BSc(Hons), MSc, MBCS
> >
> > Product Director
> > Strata Software Ltd.
> > Office: +44 (0)1483 422515
> > Mobile: +44 (0)7966 652063
> > www.stratasoftware.com
> > Best Practice for Service-Oriented Architectures
> >
>--
>Don Flinn
>President, Flint Security LLC
>Tel: 781-856-7230
>Fax: 781-631-7693
>e-mail: flinn@alum.mit.edu
>http://flintsecurity.com