Hi Gregg,
 
This is pretty good!  Basically a business level test, although I would suggest there may be others as well depending on the goals of the SOA.  An SOA isn't something to invest in for its own sake - for business process automation, rapid integration, multi-channel access (i.e. multiple requester types), or cost redution through reuse.  Whatever the goal is, it definitely needs metrics for evaluation.
 
Eric

----- Original Message ----
From: Gregg Wonderly <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, October 10, 2006 6:40:04 PM
Subject: Re: [service-orientated-architecture] What is SOA?

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. When its cheaper to refine
your systems and better support the business through services that wrap the
systems, then you still don't have the "right" SOA. When it's cheaper to stay
where you are at, then you have the right SOA.

Gregg Wonderly



__._,_.___


SPONSORED LINKS
Computer software Computer security software Computer software program
Computer fax software Computer virus software

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___

Reply via email to