RE: [soa-rm-ra] intro discussion for Wednesday [was: [soa-rm-ra] positioning SOA on the cusp between IT and business]

["Lublinsky, Boris" <boris.lublinsky@navteq.com>]

Nice addition 
Business services has many dimensions, including connectivity, security,
etc. 
(I do not particularly like the slide, depicting business service as a
legacy app, but this aside). If you remember good old days, people tend
to talk about components and componentware (for example J2EE container),
providing run time support for components. I would extend this to a
serviceware, provided by IT, and comprised from infrastructure services
and frameworks, that allows to SOAsize business services.
The thing that I am very keen on is the traceability between business
service and IT artifact/deployment. This is what provides business IT
alignment - it allows them to talk about the same thing.
The other thing is that by applying decomposition to business problem as
a whole (not a particular application) SOA now starts to break islands
of data and automation that contemporary IT suffers from. User service,
for example, can be externalize, thus relieving other services and
processes to deal with user data. So business level, vs application
level decomposition is another distinguishing feature of SOA

-----Original Message-----
From: Estefan, Jeff A (3100) [mailto:jeffrey.a.estefan@jpl.nasa.gov] 
Sent: Wednesday, September 23, 2009 3:45 PM
To: soa-rm-ra@lists.oasis-open.org
Subject: RE: [soa-rm-ra] intro discussion for Wednesday [was:
[soa-rm-ra] positioning SOA on the cusp between IT and business]

Rex and Boris,

Like both proposed updates.  (Note that departure from Rex's version to
Boris' version starts with "Business needs drive..." vs "Business
drives...".)

I think the additional distinction of business services being supported
and implemented by IT is a useful addition that Boris provides; however,
I'm going to beat Ken to the jump on this one and note what he and his
MITRE colleagues very eloquently point out in their SOA training
materials (see attached slides which are an excerpt from the full deck)
and that's the distinction between a "business service" and the ability
to bring that service to bear (i.e., a "SOA service").  If we decide to
include Boris' additional context to Rex's original proposed update,
then we will also need to clearly differentiate "business service" from
"SOA service".

Cheers all!

 - Jeff


The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above.  If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited.  If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files.