This paper will demonstrate a pragmatic methodology, used in conjunction with UML (unified modeling language), BPMN (business process modeling notation) along with engineering principles for describing an actionable architecture for cloud computing in the real world. The fundamental paradigm of cloud computing, whether it is for private or public usage, revolves around the provisioning of services for everyone through rich resources that can be synergized through Internet-based protocols.
The true definition of Cloud Computing is, according to the author, all about the practicalities of “outsourcing” all aspects of using computing resources to some form of external “agency”. This means that the assumption for any cloud computing usage is the fact that the “agency” has a powerful resource base (hardware, software, infrastructure, platforms, power supply, backups, failover mechanisms as well as management skills). Therefore, all users of the cloud computing services provided by the “agency” can work in a well-defined “demand-supply” mode, with an insurmountable base of possible fault-tolerant mechanisms to support best possible user experiences. The user will have the unique experience of not being worried about where his/her work is being done because cloud computing, as defined above, will enable him/her to work in a “virtualized” environment but with the feeling of being close to the resources.
However, the apparent ease available through cloud computing will raise problems associated with diverse types of risks. Hence, it is imperative to define new architectural blueprints as well as the associated business processes around them so as to provide measurable metrics that will allay the fears of any user. The architectural blueprint is not just meant to be a lot of diagrams and documents but they are to be modeled as actionable artifacts. These actionable artifacts will allow for operational excellence that covers all types of functional as well as non-functional requirements that any user expects. The MDA (model driven architecture) approach, coupled with BPM (business process modeling) and engineering principles, as posited in this paper, will allow for management of distributed communication, scheduling, security enhancements and rights (as well as many other aspects) that will make the user experience enjoyable and successful.
Table of Contents
1. INTRODUCTION
1.1 PURPOSE
1.2 BUSINESS DRIVERS
2. APPROACH
2.1 CSB (CLOUD SERVICE BUS) – FORMALISM
2.2 BPM
2.3 USE CASE MODEL (REQUIREMENTS)
2.4 SEQUENCE MODEL (SCENARIOS)
2.5 COMPONENT MODEL
2.6 DEPLOYMENT MODEL
2.7 CSB MODEL DRIVEN ARCHITECTURE
3. CONCLUSION
Objectives and Topics
This paper aims to define a pragmatic, actionable architectural model for cloud computing by integrating UML, BPMN, and engineering principles. The primary research goal is to demonstrate how a Cloud Service Bus (CSB) acts as a fundamental, programmable framework to map user requirements and business processes to real-world infrastructure, ensuring operational excellence and fault tolerance.
- Integration of Model Driven Architecture (MDA) in cloud environments.
- Formalizing the Cloud Service Bus (CSB) as a metasystem for utility-based services.
- Application of Business Process Management (BPM) to cloud lifecycles.
- Modeling requirements and dynamic behaviors through UML use case and sequence diagrams.
- Economic justification of cloud computing based on peak-to-average demand ratios.
Excerpt from the Book
1.1 Purpose
There are many types of ideas and purported cloud computing implementations that are available today. Many leading vendors and providers have “outsourcing” models that currently support private as well as public cloud computing infrastructure. Examples of PaaS (platform as a service), SaaS (software as a service), IaaS (infrastructure as a service) and the like abound today. Leaders in this whole space (AT&T, IBM, Oracle, Microsoft, HP, Amazon as well as other smaller companies) are in the cloud computing space. However, it is clear that the missing dimension is one that can cover user requirements in such a manner that an actionable computing architecture can be created so as to drive the real-world implementation of this type of service offering.
An excellent paper published by K. Mukherjee and G. Sahoo [Reference 1], in the 2009 IEEE “International Conference on Advances in Computing, Control and Telecommunication Technologies”, has provided a great deal of insight into the mathematical modeling framework vis-à-vis cloud computing as a whole. This excellent paper explains, in a very lucid manner, all the details of what the agenda of cloud computing is, along with details of runtime entities involved in cloud computing, as per the practical needs of users who pay for the services on a “pay-per-usage” or “dedicated basis”.
Summary of Chapters
1. INTRODUCTION: Outlines the purpose of defining an actionable cloud architecture and identifies key industry influencers and business drivers.
2. APPROACH: Details the methodology for describing a Cloud Service Bus (CSB) using UML, including formal models for requirements, components, and deployment.
3. CONCLUSION: Synthesizes the viability of the CSB architecture and explains the economic logic behind cloud computing adoption via demand-curve analysis.
Keywords
Cloud Computing, Actionable Architecture, Cloud Service Bus, CSB, MDA, Model Driven Architecture, BPM, Business Process Management, UML, Virtualization, Utility Computing, Infrastructure as a Service, IaaS, PaaS, SaaS
Frequently Asked Questions
What is the fundamental purpose of this paper?
The paper seeks to define a pragmatic, actionable architectural framework for cloud computing to ensure that real-world implementations meet both functional and non-functional user requirements.
What are the primary thematic areas covered?
The themes include the formalization of the Cloud Service Bus (CSB), the application of Business Process Management (BPM), and the use of Model Driven Architecture (MDA) for cloud deployment.
What is the central research question?
The research explores how to bridge the gap between abstract cloud concepts and actionable, model-based engineering to create reliable, fault-tolerant service environments.
Which scientific methods are employed?
The author employs system engineering principles combined with UML modeling (use case, sequence, component, and deployment diagrams) and BPMN for process visualization.
What topics are discussed in the main body?
The main body focuses on the CSB formalism, requirements modeling, dynamic system behavior through scenarios, and the physical mapping of components in a virtualized, programmable architecture.
Which keywords best characterize the work?
The work is characterized by terms such as Cloud Service Bus (CSB), Model Driven Architecture (MDA), Business Process Management (BPM), and Actionable Architecture.
How does the author define the "Cloud Service Bus"?
The CSB is defined as a "metasystem" that accepts various systems as inputs and outputs, serving as the foundation for a utility-type set of services that form the cloud environment.
What is the economic justification for using cloud services provided in the conclusion?
The author argues that a pure cloud solution is viable even if unit costs are higher than dedicated capacity, provided that the "peak-to-average" ratio of demand justifies the shift from fixed, peak-based infrastructure.
- Quote paper
- Mathews George (Author), 2011, Cloud Computing. Actionable Architecture, Munich, GRIN Verlag, https://www.grin.com/document/262815
