Cloud Computing. Actionable Architecture

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.