Hi All,

 

In the On Demand market you don’t sell software. The customer buys a solution. The vendor’s responsibility is their actual success with the solution on a daily basis. The technology & tools are the vendors problem. Tools are what vendors used to sell customers when their solutions didn’t work. It’s more like the restaurant business than the software business.

                                              

 

Best,

                                                                                                         

Bill Appleton
CTO
DreamFactory Software
tel. 408-399-7454  x 102
fax. 408-351-9005
cel. 408-656-3024
[EMAIL PROTECTED]

 

 

 


From: [email protected] [mailto:[email protected]] On Behalf Of Vikas Deolaliker
Sent: Thursday, February 23, 2006 5:22 PM
To: [email protected]
Subject: Re: [service-orientated-architecture] SAAS vs SOA

 

Anne,

 

I don't understand the distintion you make between software service and business service that uses software as a means. Couldn't SF.COM be seen as a company offering CRM service? Software then is only a means to this CRM service. Or I may want to start a settlement center and instead of purchasing the settlement software system, I could lease it online from some settlement service. I guess, I see some of your point in that when a business service has some manual intervention, you classify that as a business service if it is fully automated, you classify that as a software service. Right?

 

Isn't SaaS just a delivery channel for services that are exposed by vendors? More services can be mined from the vendor's data center should the data vendor decide to implement SOA. Does this reconcile the two?


Vikas



----- Original Message ----
From: Anne Thomas Manes <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, February 22, 2006 12:42:12 PM
Subject: Re: [service-orientated-architecture] SAAS vs SOA

Here's how I see it:

SaaS is a business model that applies to organizations whose primary product is software (i.e., software vendor). These vendors can license the software to other organizations who will deploy it and run it as they deem fit, or the vendors can host the software (either themselves or through a service agency) and licenses user subscriptions to the software.

The classic example of a SaaS vendor is Salesforce.com.

A SaaS application does not need to be service-oriented, although service-orientation would be a valuable feature in that it will enable easier integration with other software.

SOA is a software design discipline in which application functionality is implemented as reusable services that can be shared by many different applications.

Organizations whose primary product is not software ( i.e., not a software vendor) should not be thinking in terms of SaaS. Non-vendors should be focused on selling their business services (healthcare, financial, manfacturing, etc). Very often delivery of these business services involves the use of software -- but the software is simply the means to the services -- not the service itself. If you are a financial services company specializing in settlement services, then you are selling settlement services, not software services -- even if the settlement service is implemented using software.

Anne

On 2/22/06, Paul Denning <[EMAIL PROTECTED]> wrote:

I am trying to reconcile or form a mental model of Software As A
Service (SAAS) and SOA.

How does an On-Demand Application (ODA) relate to a "service"?

How are they (SAAS, SOA) similar and how are they different?

Thoughts?

Any good links?

Paul







Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/service-orientated-architecture/

<*> 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/


 

 



SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




Reply via email to