Skip to main content

Currently Skimming:


Pages 14-20

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 14...
... 14 CHAPTER 3 INTERPRETATION OF FINDINGS ASP AND THIN CLIENT VALUE PROPOSITION Across industry in general, the ASP business model has achieved early adopter acceptance as a legitimate option for obtaining outsourced computing services. Survey findings show that between 11% and 18.5% of respondents already subscribe to ASP services, and analyst predictions are for continued expansion of ASP use in the future.
From page 15...
... hosting, maintenance, support, and operation responsibilities remain inside the organization. The change that an organization makes in adopting thin client computing is that application processing moves from the desktop workstation to a central server, allowing desktop operations to proceed with a less capable or "thin" desktop software application.
From page 16...
... or if the specific competency required for the desired application is not present in the organization, then outsourcing to an ASP may be a means of compensating for the lack of internal expertise. • Technical resource availability: If the organization has internal technical expertise but if that expertise is fully occupied with current duties and cannot support an additional application, then ASP outsourcing can be a means to augment overburdened internal resources.
From page 17...
... • Determine how many concurrent users the application must support. • Estimate the cost of provisioning that application internally, including all costs for hardware, software licenses, development, application customization, operations, maintenance, technical support, help desk support, and training that may be associated with implementing the application.
From page 18...
... • Check the ASP's record for maintaining quality of service and meeting the provisions specified in SLAs. • Check the ASP's record of responding to customer problems and the ASP's record for resolving those problems.
From page 19...
... for both the customer and the ASP and should specify clear timeframes for moving to each level of escalation. • Performance metrics: The SLA should include specific, quantified metrics to be used in measuring service delivery.
From page 20...
... tured, repetitive, transaction-oriented tasks and are not for tasks requiring creative activity. Thin client applications are also not good candidates to support computationintensive processing or data-intensive processing.

Key Terms



This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.