Design And Implementation Of Whole Process Modeling Tool Based On BPMN And BPEL

With the development of web service and business generation technology, a standardized process definition language is needed for distributed network to support the integrated business development. Among variety of business process modeling languages and notations, BPEL and BPMN are two most famous ones. BPEL is a standard language used for business process description, which can be executed directly on computer. It combines web services together through control structure to create new business process, then execution engine is used to deploy the process and complete the entire functions. BPMN is a graphic oriented business process modeling tool which provides a set of notations. It is easy used and accepted by OMG as a formal standard.There are many different roles in business modeling process, including business analysts, software developers and business supervisions. For different users, BPEL and BPMN each has some limitations. BPEL is a powerful tool that needs complex configurations, thus it’s usually used by software developers as they are familiar with BPEL syntax. However, BPMN lack the definition of diagram storage structure in business process, which leads to a vague meaning of process elements. For those reasons, BPMN model is suitable for analysts to design business demands.This paper designed and implemented a whole process modeling tool based on BPMN and BPEL. The tool aims to provide a unified modeling environment for both business analysts and developers that users can making business models in two levers:BPMN and BPEL. Meanwhile, through the static analysis, the tool can find whether there exist business node conflicts in parallel data access. These conflicts can be optimized by matching schemes in database and finding the most suitable solution to replace it.This paper first describes the background and significance of the whole process modeling tool, and gives a brief introduction of the related technologies, including the differences and similarities between BPMN and BPEL. Then, based on the system objectives, both functional requirements and non-functional requirements are set up. Meanwhile, two key technologies:data access conflict model and model mapping schema have been introduced. According to the research, the overall structure design of the tool is given and modules are well designed and implemented. Finally, with the deployment and test case, the validity and reliability of the tool has been checked, thus a conclusion is given about what the tool has done and where it can be improved.