Common Understanding Wiki

Common Understanding Wiki

A Common Knowledge Source of Terms and Definitions

CloudSocket Common Understanding Wiki

(You are viewing an archived version of this page. (2.9), Go to the latest version.)
Wiki: General

Common Technical Understanding of Business Process as a Service #

This wiki tries to achieve a common technical understanding of Business Process as a Service including the intended usage. 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 Process as a Service and CloudSocket #

Business Process as a Service (BPaaS) represents an Internet-based service where different users (so far unspecified) can register business processes, register implementations for business processes, select, annotate, and enact these processes or groups thereof.

From the view of the NIST definition, BPaaS is either a special form of Software as a Service or a very limited form of Platform as a Service (cf. Cloud Service Models and NIST Standard).

Users and Roles #

End user

X user

Y user


T2.2 Common Technical Understanding of Business Process as a Service [UULM]
This task is concerned with creating documents like public WIKI pages, 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.

This Wiki offers a BPaaS taxonomy as well as an explanation of background material in order to create a common understanding with respect to technical realisation for business process as a service in the cloud.

6 Attachments
Average (1 Vote)
No comments yet. Be the first.