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. It's main purpose is to collect, describe and explain the used concepts not only for the consortium members but also for other cooperative projects. In particular, it 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 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.

For quick access to individual terms, the Glossary page shall be used.\\

Domain-oriented Access to Content

{{File:wiki_structure.png}}

Taxonomy-oriented Access to Content

bbbb\\

\\

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.\\

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. \\

• Business and IT-Cloud alignment
• Taxonomy
• Tools
• Models

\\

\\