OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [soa-rm] Definition of Service:From concall


Ah - thanks for the clarification (I didn't catch that digitization was the primary point at the end). Yes, this is the difference between a non-mostly-or-completely-automated service, and a mostly-or-completely-automated service. I say "mostly-or-completely automated" instead of just "automated", because something like a workflow process - which may have human-oriented tasks - may still be considered to be a service (a "process-oriented" service) by some, yet it is not fully automated.
 
So I agree that those types of services (non-mostly-or-completely-automated) are out of our scope. But it's a curious question whether or not a shoe shining service can have an architecture - I say perhaps, it's just not a technical architecture.
 
Joe
 
Joseph Chiusano
Booz Allen Hamilton
O: 703-902-6923
C: 202-251-0731
Visit us online@ http://www.boozallen.com
 


From: Sally St. Amand [mailto:sallystamand@yahoo.com]
Sent: Wednesday, August 10, 2005 5:57 PM
To: Chiusano Joseph
Cc: SOA-RM
Subject: RE: [soa-rm] Definition of Service:From concall

Joe
How are they digitized? They are not services in the context of SOA.
 
Oops, I forgot about microwaving. For your empty stomach, not your scuffed shoes.
 
Sally


Chiusano Joseph <chiusano_joseph@bah.com> wrote:
> From this perspective shoe shining and food delivery are not services. So a logical conclusion is that 'services' are not absolute.
 
Are we sure about that? Why would they not be?
 
Joe
 
Joseph Chiusano
Booz Allen Hamilton
O: 703-902-6923
C: 202-251-0731
Visit us online@ http://www.boozallen.com
 
 

From: Sally St. Amand [mailto:sallystamand@yahoo.com]
Sent: Wednesday, August 10, 2005 4:52 PM
To: SOA-RM
Subject: [soa-rm] Definition of Service:From concall

hi all
On todays call I was trying to present my definition of what a service is. If I had a whiteboard
 
Org has          Translates              Digitized
 
Need              Task           +          wire enable    =  Service
Capability
 
 
Start from the perspective that an org has a need (or is offering a capability). That need gets translated into a task, eg get an airline seat [which is a finer granularity; or an activity, make a trip reservation, which is more complex] The task has to have technical details added to allow it to be provided and/or consumed. The end result is a service in the context of our work for SOA.
 
A service is based on the functionality it is providing. That functionality is not just the business (or mission) task/activity but the digital requirements, eg encryption, endpoints. A service is multi faceted.
 
From this perspective shoe shining and food delivery are not services. So a logical conclusion is that 'services' are not absolute.
 
 Sally
 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]