Systems and methods for identifying problems of a business application in a customer support system

• US 20060242175A1
• 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 8,539,003 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/72 Code refactoring

Abstract

In accordance with embodiments of the present invention, methods and systems analyze potential logic errors or problems of a business application by receiving a model representing the business application and processing the model using an object-oriented tool. The errors or problems may be corrected in the model and the correction applied to the business application. In one exemplary embodiment, the logic errors or problems may be marked in the model for identification to a user.

Claims

1. A method of linking a customer support system to a business application composed in a first programming format, comprising:

processing a model representing the business application, wherein the model is composed in a second programming format;

determining, based on the processed model, a potential problem in the business application; and

identifying the determined potential problem by displaying a marker in the model of the business application.

2. The method of claim 1, wherein identifying the determined potential problem further includes:

displaying the marker in the model at a location where the potential problem occurs.

3. The method of claim 1, further including:

associating the displayed marker with information describing the determined potential problem.

4. A method of analyzing a business application composed in a first programming format, comprising:

receiving a model representing the business application in a second programming format;

processing the model using an object-oriented tool to identify a potential programming error; and

identifying the potential programming error by displaying a marker in the model of the business application.

5. The method of claim 4, further including:

correcting the identified potential programming error; and

applying the corrected programming error to the business application.

6. The method of claim 4, wherein processing the model using the object-oriented tool further includes at least using a code debugger.

7. The method of claim 4, wherein the second programming format is an object-oriented programming format.

8. A method of analyzing a business application, comprising:

receiving an object-oriented programming construct representing logic entities defining the business application;

processing the object-oriented programming construct using an object-oriented tool to identify a potential programming error;

marking the potential programming error of the object-oriented programming construct; and

correcting the marked potential programming error in the object-oriented programming construct.

9. The method of claim 8, further including:

applying the corrected error to the business application.

10. The method of claim 9, wherein applying the corrected error to the business application further includes:

correcting the configuration data of the business application.

11. The method of claim 9, wherein applying the corrected error to the business application further includes:

correcting the rules of the business application.

12. A system for linking a customer support system to a business application composed in a first programming format, comprising:

means for processing a model representing the business application, wherein the model is composed in a second programming format;

means for determining, based on the processed model, a potential problem in the business application; and

means for identifying the determined potential problem by displaying a marker in the model of the business application.

13. The system of claim 12, wherein identifying the determined potential problem further includes:

means for displaying the marker in the model at a location where the potential problem occurs.

14. The system of claim 12, further including:

means for associating the displayed marker with information describing the determined potential problem.

15. A system for analyzing a business application composed in a first programming format, comprising:

means for receiving a model representing the business application in a second programming format;

means for processing the model using an object-oriented tool to identify a potential programming error; and

means for identifying the potential programming error by displaying a marker in the model of the business application.

16. The system of claim 15, further including:

means for correcting the identified potential programming error; and

means for applying the corrected programming error to the business application.

17. The system of claim 15, wherein the second programming format is an object-oriented programming format.

18. A system for analyzing a business application, comprising:

means for receiving an object-oriented programming construct representing logic entities defining the business application;

means for processing the object-oriented programming construct using an object-oriented tool to identify a potential programming error;

means for marking the potential programming error of the object-oriented programming construct; and

means for correcting the marked potential programming error in the object-oriented programming construct.

19. The system of claim 18, further including:

means for applying the corrected error to the business application.

20. The system of claim 18, wherein the means for applying the corrected error to the business application further includes:

means for correcting at least one of configuration data or rules of the business application.