How about a *testable* definition, Gregg? One that I can use to
evaluate a system to determine whether it's architecture is SOA or
not, as well as understand what changes I'd need to make for it to
become SOA (including what advantages I'd gain in doing so).
Mark.
On 10/10/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
> Gervas Douglas wrote:
> > If only life were so simple, whoever you are (please sign your messages
> > in future: this is a convention of this Group - Moderator). Still, I
> > think it is probably about time the Great Minds of this Group's
> > Distinguished Denizens had another crack at defining SOA.
>
> SOA is the rewiring of business (not just enterprise) software and people
> systems to be visible as domain targeted services that allow the business to
> trivially interact with these systems. This creates a decoupling from the
> business processes which facilitiates a separate development and evolution
> path
> of the systems and the business's services.
[snip]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> 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/
