9.Limitations and Future Work
The cloud service provider model can be used for any company planning on migrating their software services to the cloud. The senior management in such a company should perform pairwise comparisons for both the objectives and criteria and leave the experts to choose the best strategy. Experts’ opinions are also relevant for any other uses of the model. Here, the weights for the objective and criteria are relevant only to BMF because they are unique to its needs. The strategy weights are global and can be used for any other applications.
Future work should be conducted to find out which IaaS platform should be purchased. If an HDM model was created for this purpose, the pairwise comparisons should be conducted by the senior management of BMF or subcontracted to a consulting firm. Vendors selling the IaaS service should not be doing the pairwise comparisons.
References
1.D. Kocaoglu, “Hierarchical Decision Modeling”, Engineering and Technology Management Department, Portland State University, Portland, 1987.
2.A. K. Sadhu, “Delphi technique”, Managementversity, 29 November 2014. http://managementversity.com/delphi-technique/. Accessed: 10 March 2017.
3.P. Mell and T. Grance, “The NIST definition of cloud computing”, Technical report, National Institute of Standards and Technology, US Department of Commerce, September 2011. http://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf. Accessed: 16 March 2017.
Chapter 3
Technical Transformation: Cloud Computing
Amit Pingle* and Tugrul Daim*,†,‡
*Portland State University, Portland, Oregon, USA
† Higher School of Economics, Moscow, Russia
‡ Chaoyang University of Technology, Taiwan
Abstract
This project used a Hierarchical Decision Model (HDM) approach by dividing the model hierarchies into Mission, Objectives, Goals, Strategies and Actions, also called MOGSA. The fundamental criteria used for assessment are: Innovation Factor, Technological Factor, Usability Factor and Economic Factor. These four primary evaluation criteria were further divided into seven subcriteria: Complexity, Compatibility, Security, Architecture, Usefulness, Ease of Use and Cost. These criteria were evaluated using a pairwise comparison method. Four cloud computing platforms were considered for the project: Amazon Web Services, Google Cloud Platform, IBM Bluemix and Microsoft Azure. A group of experts was used to measure and compare results of the HDM. This group includes application developers working in different domains and had been using cloud computing platforms. The range of inconsistency recorded was between 0.02 and 0.04, whereas the disagreement between the judgments was 0.055. Despite individual responses by some of the evaluators, Amazon Web Services was the preferred cloud computing platform, thus making the HDM a better methodology to quantify and counterbalance all individual preferences while making complex decisions.
Keywords: Technology assessment, cloud computing, web services.
1.Introduction
Cloud service is an integral part of today’s business. With rapidly increasing amounts of data, Internet of Things (IoT) and applications, their presence in our lives today demand high storage and computing power. Cloud computing makes it easier for businesses by providing them high computing power as an alternative to investing in costly infrastructure. Using cloud computing, people and enterprises can operate any application on a plug and play basis without really investing on hardware. Organizations not only get save a lot of money, maintenance also becomes easier since the platform provider takes care of its speed and technical abilities.
Hence, it becomes very important for any business to carefully choose the appropriate cloud service provider that can provide the desired speed and computing power required for the business.
An application developer wanted to choose the best cloud computing platform for one of the application he had developed. He was undecided which cloud service provider he should choose. Many possible decisions he had to make were discussed, such as choosing a cloud computing platform and the type of hardware that would be compatible with it. After much discussion without any results, he decided to use the HDM because it would help solve the problem in a better way. While going through the process it was observed that many application developers face the same problem in choosing a cloud service provider. Instead of using the HDM for just one developer, he decided to use it to help other developers to choose between Amazon Web Services, Microsoft Azure, Google Cloud Platform and IBM Bluemix.
To make the HDM and research more vigorous, the panel of experts would be expanded to 13 application developers from different domains, where each would give their valued assessments.
2.Methodology
The methodology that has been used in this project was the Hierarchical Decision Model (HDM), which was developed by David Cleland and Dundar Kocaoglu. For any HDM, the basic structure of the hierarchy is presented in the MOGSA form [1]. This model consists of five levels—Mission, Objectives, Goals, Strategies and Actions. Each of these levels has a specific function for the model [2]. Nevertheless, it is not essential to have all five levels in a model, though it needs to have at least three levels, which are Mission, Objectives (criteria) and Actions (decisions).
3.Hierarchical Decision Model
The HDM—a multilayered method for studying complex decisions—was developed in 1979 using a similar concept as the Analytical Hierarchy Process (AHP) methodology, but with a different pairwise comparison scale and judgmental quantification technique [3]. Depending on how simple or complex the decision-making problem is, the number of hierarchical levels is determined.
HDM is a methodology that breaks down a problem into different hierarchies or sublevels. The approach an HDM takes is that it considers any problem as an association of sub-problems, which can be broken down into hierarchies or levels. The most common approach in a HDM consists of three important decision hierarchies: Impact or Mission level, Target or Objective level and Operational or Action level [4]. Each level comprises of multidimensional components [4].
The top level which is the objective, leads to benefits. The bottom level, which is the alternative, results from multiple actions. Each decision element at every level has an impact on different elements at the next higher level. A hierarchy can be determined as a completed hierarchy if each element of the given hierarchy is evaluated with respect to each element in the next hierarchy [2]. Any complex decision problem can be expressed as an analytical hierarchical decision.
3.1.Pairwise comparison