Methods of comparing and merging business process configurations

• US 20060242207A1
• Filed: 08/15/2005
• Published: 10/26/2006
• Est. Priority Date: 04/22/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Stulski, Vitaliy, Tsyganskiy, Igor, Satsuta, Eugene, Scheinkman, Luiz, Liakh, Dmitri
• Granted Patent: US 7,542,980 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/72 Code refactoring
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Exemplary methods and systems consistent with the present invention allow a user to compare different versions of a business application using an object-oriented model of the business application. By transforming business application structures into object-oriented structures, such as object-oriented language constructs, structures, and other elements, individual differences between versions of the business applications may be identified and displayed to a user, for example, on a user interface. A user may display object-oriented models of the business application representing, for instance, the latest control version, the latest deployed version, and a test version including test modifications. Having all three versions represented in object-oriented models allows a user to perform a three-way comparison between the object-oriented models, increasing productivity and efficiency of maintaining, debugging, modifying, controlling and deploying the business application.

Claims

1. A method of determining a current version of a business application, comprising:

receiving a first version of an object-oriented model representing the business application, wherein the first version includes a plurality of objects;

receiving a second version of the object-oriented model representing the business application, wherein the second version includes a plurality of objects;

receiving a third version of the object-oriented model representing the business application, wherein the third version includes a plurality of objects;

comparing the objects of the first version, the second version, and the third version of the object-oriented model to identify differences between the first version, the second version, and the third version of the object-oriented model;

determining, for each identified difference, which version of the object-oriented model is to be associated with the first version of the object-oriented model; and

assigning the first version of the object-oriented model as a current version of the object-oriented model.

2. The method of claim 1, further comprising:

generating the first version of the object-oriented model based on a configuration of the business application stored in a version control database.

3. The method of claim 1, further comprising:

generating the second version of the object-oriented model based on a currently deployed configuration of the business application.

4. The method of claim 1, further comprising:

generating the third version of the object-oriented model based on a modified configuration of the business application.

5. The method of claim 1, wherein the business application is in a table-based format.

6. The method of claim 1, further comprising:

transforming the current version of the object-oriented model into a current version of the business application.

7. The method of claim 6, further comprising:

storing the current version of the business application in a version control database.

8. A method of comparing configurations of a business application, comprising:

generating a first object-oriented model representing a first configuration of the business application stored in a control database;

generating a second object-oriented model representing a second configuration of the business application that is currently deployed;

generating a third object-oriented model representing a third configuration of the business application that has been modified from the currently deployed configuration;

comparing objects of the first object-oriented model, the second object-oriented model, and the third object-oriented model to identify a difference between the first object-oriented model, the second object-oriented model, and the third object-oriented model;

analyzing the identified difference to determine which object-oriented model represents a desired configuration of the business application; and

designating the object-oriented model representing the desired configuration of the business application, based on the analysis of the identified difference.

9. The method of claim 8, further comprising:

transforming the designated object-oriented model to create the desired configuration of the business application; and

replacing the configuration of the business application that is currently deployed with the desired configuration of the business application.

10. The method of claim 8, further comprising:

transforming the designated object-oriented model to create the desired configuration of the business application; and

replacing the configuration of the business application stored in the control database with the desired configuration of the business application.

11. The method of claim 8, further comprising:

displaying the identified difference together with a relevant portion of the first, second, and third object-oriented models using a single user interface.

12. The method of claim 8, wherein the business application is in a table-based format.

13. The method of claim 8, further comprising:

receiving a modification to the currently deployed configuration of the business application from a user via a user interface; and

enabling the user to request comparison of configurations of the business application by selecting a button on the user interface.

14. A system for comparing configurations of a business application, comprising:

a generating component configured to

generate a first object-oriented model representing a first configuration of the business application stored in a control database,

generate a second object-oriented model representing a second configuration of the business application that is currently deployed, and

generate a third object-oriented model representing a third configuration of the business application that has been modified from the currently deployed configuration;

a comparing component configured to compare objects of the first object-oriented model, the second object-oriented model, and the third object-oriented model to identify a difference between the first object-oriented model, the second object-oriented model, and the third object-oriented model;

an analyzing component configured to analyze the identified difference to determine which object-oriented model represents a desired configuration of the business application; and

a designating component configured to designate the object-oriented model representing the desired configuration of the business application, based on the analysis of the identified difference.

15. The system of claim 14, further comprising:

a transforming component configured to transform the designated object-oriented model to create the desired configuration of the business application; and

a replacing component configured to replace the configuration of the business application that is currently deployed with the desired configuration of the business application.

16. The system of claim 14, further comprising:

a transforming component configured to transform the designated object-oriented model to create the desired configuration of the business application; and

a replacing component configured to replace the configuration of the business application stored in the control database with the desired configuration of the business application.

17. The system of claim 14, further comprising:

a displaying component configured to display the identified difference together with a relevant portion of the first, second, and third object-oriented models using a single user interface.

18. The system of claim 14, wherein the business application is in a table-based format.

19. The system of claim 14, further comprising:

a receiving component configured to receive a modification to the currently deployed configuration of the business application from a user via a user interface; and

a button on the user interface configured to enable the user to request comparison of configurations of the business application.

20. The system of claim 19, wherein the button is displayed together with the identified difference.