I'm in agreement with Steve here. Customer Service is a service and
can very much be part of an SOA.
I reiterate my position on SOA, which is:
There is no widely-agreed upon definition of Service-Oriented
Architecture other than its literal translation that it is an
architecture that relies on service-orientation as its fundamental
design principal. Service-Orientation as a design methodology applies
the concepts of loose-coupling of producers and consumers in a
networked graph that enables development of highly-agile systems and
abstracts implementation from process, such that a service-provider
can be modified or changed without affecting the consumer. These
concepts can be applied to business, software and other types of
producer/consumer systems.
BTW, I see someone has once again changed my Wikipedia definition
from this again.
JP
__________________________________
JP Morgenthal
President & CEO
Avorcor, Inc.
46440 Benedict Drive
Suite 103
Sterling, VA 20164
(703) 649-0829 x 101: Office
(703) 554-5301 : Cell
[EMAIL PROTECTED]
__________________________________
SOA success is just a click away...
On Jun 13, 2007, at 5:49 PM, Steve Jones wrote:
Why isn't Customer Service a Service from an SOA perspective (it is
for me) it has a set of capabilities that demonstrate a real world
effect and the service provides the mechanism for accessing those
capabilities. So Customer Service is certainly a service that
complies with the OASIS SOA RM.
On 13/06/07, Jerry Zhu <[EMAIL PROTECTED]> wrote:
Business process is lower than products and services
that are in market for money. Business process
implment them so below them, or GE as you say.
Customer service is not SOA service but business value
deliverd in the use of business process.
Unfortunatedly we run out of words and use the same
word to reprsent two different things.
Jerry
--- Steve Jones <[EMAIL PROTECTED]> wrote:
> I'm still not seeing the business process that is at
> a higher level of abstraction than General Electric,
but I can see the business processes that
> are just implementations for capabilities of
> customer service...
>
> On 11/06/07, Jerry Zhu <[EMAIL PROTECTED]> wrote:
> >
> >
> > --- Rob Eamon <[EMAIL PROTECTED]
> <reamon%40cableone.net>> wrote:
> >
> > > --- In
> > >
>
[email protected]<service-orientated-
architecture%40yahoogroups.com>
> > ,
> > > Jerry Zhu
> > > <[EMAIL PROTECTED]> wrote:
> > > > ...
> > > > Is BPM needed in all business needs? no. Is
> SOA
> > > needed in all business needs? no. however if BMP
> is
> > needed, there must be SOA there.
> > >
> > > -1. I disagree. There is no direct, immutable
> tie
> > > between BPM and SOA.
> > > SOA principles can be applied to BPM but a
> > > successful BPM implementation doesn't need to
> follow
> > them. Processes can use a set of
> > > services to fulfill the process but not
> necessarily
> > > so.
> > >
> > Right, BPM with SOA is an ideal but not always
> occur
> > that way in reality.
> >
> > > Is BPM an architecture? IMO, no. SOA exists at a
> > > higher level of
> > > abstraction IMO. SOA is not a technology.
> > >
> >
> > Process is at higher level abstraction than
> service.
> > Each level has both business aspect and IT aspect.
> >
> > In business aspect, we say business model, in IT
> > aspect, we say architecture.
> >
> > Jerry
> >
> > > -Rob
> > >
> > >
> >
> >
> >
>
