Not that I have a strictly format definition but one might consider the
following:
A Service Oriented Architecture is one in which the computational
resources (hardware and software)
may be said to have a service interface that can be extracted and
processed by other services. An
example would be an architecture in which services are all functionally
described in WSDL or by some
equivalent (e.g. introspectable Java interfaces).
This definition allows us to
* compose new services from existing ones and present a similar
interface.
* manage services based on some agreed management lifecycle service
interface that maybe a
subset of the full interface description (e.g. Start, Stop,
Suspend, Resume, Configure).
* manage services based on computed SLA's in which services offer some
describable way of inspecting
parameters (counters) that are of interest to some management
service(s).
* further meta data about services may be added to support both
discovery and management which are also
well defined (e.g. Features and Properties in WSDL2.0, should it be
implemented)
Thus the implementation/realisation of an SOA is not dependent on the
platform (e.g. the App Server, the Communications
and so on). The behavior should be guaranteed regardless of the way in
which an SOA is realised. This can be achieved
through a common description of the service behaviors composed into an
architectural blue print (e.g. using WS-CDL).
Cheers
Steve T
On 15 Jan 2006, at 17:56, Eric Newcomer wrote:
> I'm sorry, I realize I should also have asked whether
> you meant that this concise definition isn't
> sufficient. There are of course more detailed
> definitions behind this.
>
> Eric
>
> --- Eric Newcomer <[EMAIL PROTECTED]> wrote:
>
> > Hi Patrick,
> >
> > I meant formal in the sense that it is as simple and
> > precise a definition as possible. As opposed to an
> > informal style of definition which is a bit more
> > impressionistic, you know, like an SOA is a kind of
> > an
> > architecture that does, you know, something like
> > define things like services and stuff.... ;-)
> >
> > Perhaps you are looking for formality in a different
> > kind of notation than English?
> >
> > Eric
> >
> > --- "Logan, Patrick D" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > > "An SOA is a style of design that guides all
> > > aspects of creating and
> > > > using business services throughout their
> > lifecycle
> > > (from conception
> > > > to retirement)."
> > >
> > > > In the preface we put it a little less
> > formally...
> > >
> > > *less* formally? In what way is the above formal?
> > >
> > > I hope I am not coming across in a rude way. That
> > is
> > > not my
> > > intention. I just seriously do not see any useful
> > > formal denotation in
> > > the above description. I would like to understand
> > > SOA in some formal
> > > way but I have not found even claims of such a
> > > definition until now.
> > >
> > > -Patrick
> > >
> > >
> > >
> > >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> > protection around
> > http://mail.yahoo.com
> >
> >
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
>
>
>
> SPONSORED LINKS
> Service-oriented architecture
> Computer monitoring 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.
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
