1. A method for identifying and resolving differences between business process models, the method comprising: receiving, in a processor, a first business process model project; identifying, in the processor, a second business process model project; performing, in the processor, changes to the second business process model project; creating, in the processor, a first delta model configured to analyze, in the processor, differences between the first and second business process model projects, wherein an analysis of the differences between the first and second business process model projects are in the form of low-level changes; calculating, in the processor, dependencies of the low-level changes and a conflict-free application sequence of change operations of the first business process model project and the second business process model project, wherein the conflict-free application sequence of change operations includes independent changes defined by one of parallel independent changes and sequentially dependent changes; auto-applying, in the processor, the low-level changes and the conflict-free application sequence of change operations of the first business process model project to generate a new business process model project, wherein the low level changes are auto-applied by inserting single-entry-single-exit fragments into the first and second business model projects, wherein the auto-applying of the low level changes of the first business process model project identifies conflicts between the first and second business process model projects prior to merging the first and second business process model projects; applying, in the processor, hierarchical process merging to inspect and create a consolidated business modeler language model of the first and second business process model projects; creating, in the processor, a clone of the consolidated business modeler language model, wherein the new business process model project is the consolidated business modeler language model equivalent of an integration developer model; computing, in the processor, the auto-applied low-level changes to create a second delta model configured based on the first delta model; applying, in the processor, the second delta model to the integration developer model to generate an updated integration developer model, wherein a high-level model is changed when the low level changes are applied; responsive to changes in the business modeler language model occurring at same time as changes to the updated integration developer model: applying changes to the consolidated business modeler language model to obtain a first business modeler language, generating a second business modeler language from the updated integration developer model, consolidating the first and second business modeler languages, and merging, in the processor, the first and second business process model projects based on the consolidated first and second business modeler languages.
1. A method for identifying and resolving differences between business process models, the method comprising: receiving, in a processor, a first business process model project; identifying, in the processor, a second business process model project; performing, in the processor, changes to the second business process model project; creating, in the processor, a first delta model configured to analyze, in the processor, differences between the first and second business process model projects, wherein an analysis of the differences between the first and second business process model projects are in the form of low-level changes; calculating, in the processor, dependencies of the low-level changes and a conflict-free application sequence of change operations of the first business process model project and the second business process model project, wherein the conflict-free application sequence of change operations includes independent changes defined by one of parallel independent changes and sequentially dependent changes; auto-applying, in the processor, the low-level changes and the conflict-free application sequence of change operations of the first business process model project to generate a new business process model project, wherein the low level changes are auto-applied by inserting single-entry-single-exit fragments into the first and second business model projects, wherein the auto-applying of the low level changes of the first business process model project identifies conflicts between the first and second business process model projects prior to merging the first and second business process model projects; applying, in the processor, hierarchical process merging to inspect and create a consolidated business modeler language model of the first and second business process model projects; creating, in the processor, a clone of the consolidated business modeler language model, wherein the new business process model project is the consolidated business modeler language model equivalent of an integration developer model; computing, in the processor, the auto-applied low-level changes to create a second delta model configured based on the first delta model; applying, in the processor, the second delta model to the integration developer model to generate an updated integration developer model, wherein a high-level model is changed when the low level changes are applied; responsive to changes in the business modeler language model occurring at same time as changes to the updated integration developer model: applying changes to the consolidated business modeler language model to obtain a first business modeler language, generating a second business modeler language from the updated integration developer model, consolidating the first and second business modeler languages, and merging, in the processor, the first and second business process model projects based on the consolidated first and second business modeler languages. 3. The method as claimed in claim 1 wherein the first business process model project is a business modeler project, the second business process model project is an integration developer project and the new business process model project is a new business modeler project.