On 10/10/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
> Mark Baker wrote:
> > 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).
>
> The test is this. Is it cheaper to keep doing things the way you are doing
> them, or is it cheaper to create additional services that support automation
> and
> decoupling of business processes from the systems.
There are many ways to do that. Are all of them SOA? If not, can you
be more specific? If so, are they all created equal, or are some
better than others in the general case?
Also, cost prediction is a soft science at best. Is there no way to
decide whether something is SOA by simply looking at a description of
the proposed architecture?
Mark.
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/
