Purpose -In the last two decades, a proliferation of business process management (BPM) modeling languages, standards and software systems has given rise to much confusion and obstacles to adoption. Since new BPM languages and notation terminologies were not well defined, duplicate features are common. This paper seeks to make sense of the myriad BPM standards, organising them in a classification framework, and to identify key industry trends. Design/methodology/approach -An extensive literature review is conducted and relevant BPM notations, languages and standards are referenced against the proposed BPM Standards Classification Framework, which lists each standard's distinct features, strengths and weaknesses. Findings -The paper is unaware of any classification of BPM languages. An attempt is made to classify BPM languages, standards and notations into four main groups: execution, interchange, graphical, and diagnosis standards. At the present time, there is a lack of established diagnosis standards. It is hoped that such a classification facilitates the meaningful adoption of BPM languages, standards and notations. Practical implications -The paper differentiates BPM standards, thereby resolving common misconceptions; establishes the need for diagnosis standards; identifies the strengths and limitations of current standards; and highlights current knowledge gaps and future trends. Researchers and practitioners may wish to position their work around this review. Originality/value -Currently, to the best of one's knowledge, such an overview and such an analysis of BPM standards have not so far been undertaken.

No abstract

Computers play an integral part in designing, modelling, optimising and managing business processes within and across companies. While Business Process Management (BPM), Workflow Management (WfM) and Business Process Reengineering (BPR) have been IT-related disciplines with a history of about three decades, there is still a lack of publications clarifying definitions and scope of basic BPM terminologies like business process, BPM versus WfM, workflow, BPR, etc. Such a myriad of similar-sounding terminologies can be overwhelming for computer scientists and computer science students who may wish to venture into this area of research. This guide aims to address this gap by providing a high level overview of the key concepts, rationale, features and the developments of BPM.

No abstract

Sung Lee HP Laboratories HPL-2012-11 cloud computing; data provenance; accountability; transparency;Provenance, a meta-data describing the derivation history of data, is crucial for the uptake of cloud computing to enhance reliability, credibility, accountability, transparency, and confidentiality of digital objects in a cloud. In this paper, we survey current mechanisms that support provenance for cloud computing, we classify provenance according to its granularities encapsulating the various sets of provenance data for different use cases, and we summarize the challenges and requirements for collecting provenance in a cloud, based on which we show the gap between current approaches to requirements. Additionally, we propose our approach, DataPROVE, that aims to effectively and efficiently satisfy those challenges and requirements in cloud provenance, and to provide a provenance supplemented cloud for better integrity and safety of customers' data.