CloudSocket Technology and Terminology Wiki #

This wiki is intended to create a common technical understanding of  Business Process as a Service and CloudSocket in particular. In particular, it defines functions as a references to the project terminology that is used in all project documents such as deliverables, but also the web site and marketing material. There exist two navigation paths through this wiki. The first one takes Terminology, Tools, Technologies, and Users/Roles as a first level separator. The second path is follows a taxonomy that captures the technological background of the project ranging from Business Process Management (BPM) to cloud systems, but also incorporates new terms coined by the project.

BPaaS taxonomies and explaining background
material in order to create a common understanding with respect to technical realisation for business process as a service
in the cloud. The starting point is the Business-process and IT alignment Wiki based on the Zachmann framework and
describing business process and IT relevant modelling languages. This addresses four communities: (1) the business
process management community addressing BPaaS - Design by providing definitions, standards tools, approaches
and samples. Business and IT alignment aspects are considered via semantic lifting of business process models, IT
infrastructure model, workflow models and cloud service component models; (2) for the BPaaS Allocation a model-
driven approach in order to create BPaaS Cloudlets is described by elaborating the use of UML concept models,
semantics and smart mechanisms to check the consistency and correctness. (3) for the BPaaS execution the workflow
and SOA community providers the computer orchestration view point with standards and tools. Multi-cloud access
and the service management across several cloud-infrastructures are described and approaches are pointed out; (4) the
BPaaS Evaluation Environment defines how QoS and SLA need to be lifted to QoBP and how meta model extraction
can be used for process monitoring in a multi-Cloud environment.
In addition the concept of “Conceptual Analytics” that uses any semantically lifted conceptual meta model to map
extracted meta data form process monitor logs is elaborated.
The aim of this task is create a starting point for creating a common understanding. Hence main effort is to collect,
describe and explain all used concepts not only for the consortium members but mainly for other cooperative projects,
so that applied principles, methods and approaches are clearly explained to be easily identified for other projects and
third party member 

Hence, the collection process will be based on the technical expertise of the partners, completed with a literature research
and mainly explanation effort will be performed.
The result is a collaborative content portal in appropriate form that explains relevant technical concerns with respect
to BPaaS.

involved persons (roles), and technical requirements/constraints. In all cases, we strictly separate the use of the platform from the technical concepts that realise its functionality. This section also introduces a set of abbreviations that are summarised on the Glossary page.

• Business and IT-Cloud alignment

• Taxonomy

• Tools

• Models