An ontology for executable business processes

Faculty of Informatics-Papers, 2006

BPEL4WS is one of the most utilized business process development languages. It can be used to develop executable business processes as a combination of Web Services interactions in a specific sequence called process flow. But still BPEL4WS lacks sufficient representation of business process semantics required for business processes automation. On the other hand OWL-S (OWL for Web Services) is designed to present such kind of semantic information. There exists similarity in the conceptual model of OWL-S and ...

Communications in Computer and Information Science, 2014

Coloured Petri Nets (CPNs) have formal semantics and can describe any type of workflow system, behavioral and syntax wise simultaneously. They are widely studied and successfully applied in modelling of workflows and workflow systems. There is an inherent problem regarding business processes modelled with CPNs sharing and subsequently their reuse need to be considered. The Semantic Web technologies, such as ontologies, with their characteristics demonstrate that they can play an important role in this scenario. In this paper, we propose an ontological approach for representing business models in a meta-knowledge base. Firstly, the CPN ontology is defined to represent CPNs with OWL DL. Secondly, we introduce four basic types of manipulation operations on process models used to develop and modify business workflow patterns. To the best of our knowledge, representing business process definitions and business workflow patterns as knowledge based upon ontologies is a novel approach.

Formal Ontologies Meet Industry, 2017

Business process modelling (BPM) notations describe processes using a graphical representation of process-relevant entities and their interplay. Despite the wide literature on the comparison between different modelling languages, the BPM community still lacks an ontological characterisation of process constructs. Purpose of this paper is to start filling this gap by providing a first ontological analysis of the main business process entities. The analysis and the resulting characterisation aim at illustrating the different perspectives that BPM languages implicitly take on business processes, as well as guiding the modellers in making an appropriate choice when selecting among different notations.

Abstract Business Process Management ,(BPM) is the approach to manage ,the execution of IT-supported business operations from a business expert’s process view rather than from a technical perspective. The motivation for BPM is that organizations are trying hard to continuously align their actual business processes, as executed by the multiplicity of systems, with the should-be processes as derived from business needs. BPM has gained significant attention by both research and industry, and many BPM tools are already available and in use. However, the degree of mechanization in BPM is still very limited, creating inertia in the necessary evolution and dynamics of business processes, and BPM does not provide a truly unified view on the process space of an organization. Wetrace back the problem of mechanization of BPM to an ontological one, i.e. the lack of machine- accessible semantics, and show that the modeling constructs of Semantic Web Services frameworks, especially WSMO [25, 26],...

Toward the Integrated Virtual Organization and Business Process Automation

An emerging technology like business process execution language (BPEL) and its implementation in BPEL for Web services (BPEL4WS) gives extra possibilities in describing business processes. It further adheres, as a technology, in a consistent way to the underlying Web service-based implementation technology and is a perfect fit for service-oriented architectures (SOA) as they are currently implemented throughout organizations as a successor to enterprise application integration (EAI). However, BPEL4WS, in its current implementation, will only serve in a static way for production workflows. In this chapter we discuss how Semantic Web services

Proceedings. IEEE International Conference on Web Services, 2004., 2004

… , 2005. ICEBE 2005. …, 2005

Business process management (BPM) is the approach to manage the execution of IT-supported business operations from a business expert's view rather than from a technical perspective. However, the degree of mechanization in BPM is still very limited, creating inertia in the necessary evolution and dynamics of business processes, and BPM does not provide a truly unified view on the process space of an organization. We trace back the problem of mechanization of BPM to an ontological one, ie the lack of machine-accessible ...

網際網路技術學刊, 2007

Bridging the semantic gap between business process models and semantic Web services becomes increasingly important in order to help automating business process integration in large organizations. Traditional workflow languages (such as BPEL4WS) support the modeling of business processes as syntax based compositions of Web services. When such processes are exported as Web services they as well expose syntactical interfaces. These syntactical interfaces allow only static composition and hence limit interactions between ...

The Business Process Execution Language for Web Services (BPEL) is an emerging standard for specifying the behaviour of Web services at different levels of details using business process modeling constructs. It represents a convergence between Web services and business process technology. This chapter introduces the main concepts and constructs of BPEL and illustrates them by means of a comprehensive example. In addition, the chapter reviews some perceived limitations of BPEL and discusses proposals to address perceived limitations of BPEL and discusses proposals to address these limitations. The chapter also considers the possibility of applying formal methods and Semantic Web technology to support the rigorous development of service-oriented processes using BPEL.

2009

Abstract The Semantic Business Process Management (SPBM) approach from the SUPER project utilizes a Semantic Execution Environment (SEE) for the automatic discovery, composition, mediation, and invocation of Web services. In order to enable the Semantic Execution Environment, an engineer must create semantic descriptions of functional, nonfunctional, and behavioural aspects of Web services and enduser requirements.