Cloud adoption: prioritizing obstacles and obstacles resolution tactics using AHP

Shehnila Zardari, Rami Bahsoon, Aniko Ekárt

Research output: Chapter in Book/Published conference outputConference publication

Abstract

The enormous potential of cloud computing for improved and cost-effective service has generated unprecedented interest in its adoption. However, a potential cloud user faces numerous risks regarding service requirements, cost implications of failure and uncertainty about cloud providers' ability to meet service level agreements. These risks hinder the adoption of cloud. We extend the work on goal-oriented requirements engineering (GORE) and obstacles for informing the adoption process. We argue that obstacles prioritisation and their resolution is core to mitigating risks in the adoption process. We propose a novel systematic method for prioritising obstacles and their resolution tactics using Analytical Hierarchy Process (AHP). We provide an example to demonstrate the applicability and effectiveness of the approach. To assess the AHP choice of the resolution tactics we support the method by stability and sensitivity analysis.

Original languageEnglish
Title of host publicationSAC '14 : proceedings of the 29th annual ACM Symposium on Applied Computing
Place of PublicationNew York, NY (US)
PublisherACM
Pages1013-1020
Number of pages8
ISBN (Print)978-1-4503-2469-4
DOIs
Publication statusPublished - 24 Mar 2014
Event29th Symposium on Applied Computing - Gyeongju, Korea, Democratic People's Republic of
Duration: 24 Mar 201428 Mar 2014

Symposium

Symposium29th Symposium on Applied Computing
Abbreviated titleSAC 2014
Country/TerritoryKorea, Democratic People's Republic of
CityGyeongju
Period24/03/1428/03/14

Keywords

  • AHP for obstacle prioritization
  • goal-oriented rquirements engineering for cloud
  • obstacle resolution in cloud adoption

Fingerprint

Dive into the research topics of 'Cloud adoption: prioritizing obstacles and obstacles resolution tactics using AHP'. Together they form a unique fingerprint.

Cite this