Software as a Service: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Howard C. Berkowitz
(New page: '''Software as a Service (SaaS)''' is a means of delivering specific user applications services, within the broader context of cloud computing. In SaaS, the service delivered across th...)
 
imported>Howard C. Berkowitz
No edit summary
Line 1: Line 1:
{{subpages}}
'''Software as a Service (SaaS)''' is a means of delivering specific user applications services, within the broader context of [[cloud computing]]. In SaaS, the service delivered across the "cloud", commonly the [[Internet]], is standardized: the good news is that there is no application development, and the bad news is that there is no application development. There is no development time for the customer, but the customer needs to change his procedures to match the way the SaaS application works.
'''Software as a Service (SaaS)''' is a means of delivering specific user applications services, within the broader context of [[cloud computing]]. In SaaS, the service delivered across the "cloud", commonly the [[Internet]], is standardized: the good news is that there is no application development, and the bad news is that there is no application development. There is no development time for the customer, but the customer needs to change his procedures to match the way the SaaS application works.



Revision as of 22:47, 15 September 2009

This article is developing and not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
This editable Main Article is under development and subject to a disclaimer.

Software as a Service (SaaS) is a means of delivering specific user applications services, within the broader context of cloud computing. In SaaS, the service delivered across the "cloud", commonly the Internet, is standardized: the good news is that there is no application development, and the bad news is that there is no application development. There is no development time for the customer, but the customer needs to change his procedures to match the way the SaaS application works.

The lack of application development does not mean the software cannot be customized. Indeed, many successful SaaS applications have substantial flexibility in tailoring the user interface as a mashup or dashboard.

Examples include Salesforce.com customer resource management (CRM); Everdream help desk management; SuccessFactors employee performance management; and Ketera spend management software.[1]

References

  1. Galen Gruman (21 May 2007), "The Truth About Software as a Service (SaaS)", CIO