IBM has formalized on a SOA design methodology and its
constructs that ought to be defined and created - it
is now packaged through Rational Unified Process (RUP)
and is called RUP-SOMA.
For more on it read Chapter 4 of the book 'Executing
SOA - A Practical Guide for the Service Oriented
Architect' -> 
http://www.amazon.com/Executing-SOA-Practical-Service-Oriented-Architect/dp/0132353741/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1214196499&sr=8-1

-Tilak
--- "Dey, Santanu" <[EMAIL PROTECTED]> wrote:

> in other words SOA has not yet translated into a
> *definitive set* of
> implementable design constructs (or re-usable
> patterns) that can *
> exclusively* characterise the architectural style
> beyond debate...
> 
> On Fri, Jun 6, 2008 at 8:37 PM, Dey, Santanu
> <[EMAIL PROTECTED]> wrote:
> 
> > I have struggled to define a "service" in the
> first place..
> > What is a service? We all know SOA and WS are not
> the same... Must a
> > service be machine discoverable? Must it follow
> WS*? How decoupled and
> > atomic should the services be? how important are
> service life cycle
> > management, service operations management aspects?
> >
> > Then there are questions specific to
> quintessential SOA characteristics....
> > What do you think at the minimum should be
> followed? Is service registry a
> > must? Do you need to define a Common Message
> Format? Should the architecture
> > support the capability to compose and orchestrate
> services? is a BPM layer
> > essential? is a Service Bus needed ? how important
> is service
> > virtualization? Which standards to be followed?
> >
> > without having clear answers to many questions
> questions such as above we
> > can not unambiguously define SOA.
> >   On Thu, Jun 5, 2008 at 10:41 PM, Rob Eamon
> <[EMAIL PROTECTED]> wrote:
> >
> >>   +1
> >>
> >> -Rob
> >>
> >> --- In
>
service-orientated-architecture@yahoogroups.com<service-orientated-architecture%40yahoogroups.com>,
> >> Michael Poulin
> >> <[EMAIL PROTECTED]> wrote:
> >> >
> >> > I would disagree with "üA service-oriented
> architecture is
> >> essentially a collection of services"; it is not
> an architecture.
> >> >
> >> > - Michael
> >>
> >>  
> >>
> >
> >
> 



      

Reply via email to