Methods of exposing a sequence of instructions into an object-oriented programming language

• US 20060241999A1
• Filed: 08/15/2005
• Published: 10/26/2006
• Est. Priority Date: 04/22/2005
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Stulski, Vitaliy, Tsyganskiy, Igor, Satsuta, Eugene, Scheinkman, Luiz, Liakh, Dmitri
• Application Number:
  US11/203,227
• Publication Number:
  US 20060241999A1
• Time in Patent Office: Days
• US Class Current: 705/9
• CPC Class Codes: G06F 8/72 Code refactoring
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling

Abstract

Embodiments of methods and systems consistent with the invention transform business application operations, rules, and schemas into OOP constructs that represent the operation, rule, or schema, emulate its operation in terms of sequence with other operations, and represent its relationship(s) to the data it operates with and upon in the business application. An automated system determines each operation that makes up a schema or rule in the business application by analyzing the database table(s) that hold the schema or rule. The system may transform the business operation into part of an OOP model by declaring or creating an empty OOP language construct to represent the operation, such as a Java™ function or method. The transformation process may be controlled by a set of transformation rules.

Claims

1. A method for modeling a sequence of operations in a business application, comprising:

identifying a plurality of table-based operation structures in the business application;

defining a set of transformation rules for converting the plurality of table-based operation structures into an object-oriented construct, wherein the object-oriented construct represents the plurality of table-based operation structures;

converting the plurality of table-based operation structures into the object-oriented construct based upon the set of transformation rules; and

expressing the object-oriented construct as an object-oriented programming language construct that models an operation from the business application.

2. The method of claim 1, wherein the business application is a payroll business application, the table-based operation structures embody a processing rule of the payroll business application, and the object-oriented construct is a Java function.

3. The method of claim 1, wherein the set of transformation rules includes a transformation rule for mapping a table-based operation structure to a method of an object.

4. The method of claim 1, wherein the set of transformation rules includes a transformation rule for mapping a table-based operation structure to a function.

5. The method of claim 1, further comprising:

providing a user interface to display the object-oriented programming language construct to a user.

6. A method for modeling a business rule from a business application in an object-oriented programming language, comprising:

identifying a plurality of operations that comprise the business rule;

defining an object-oriented programming language class to model the business rule, wherein the class includes a method corresponding to the plurality of operations that comprise the business rule; and

instantiating an object from the class, wherein the object represents the business rule.

7. The method of claim 6, wherein identifying a plurality of operations that comprise the business rule comprises:

traversing a table used by the business application.

8. The method of claim 6, further comprising:

displaying the object representing the business rule using an object-oriented programming tool.

9. The method of claim 6, further comprising:

detecting a problem associated with the object representing the business rule using an object-oriented programming tool, wherein the problem corresponds to a defect in the business rule.

10. The method of claim 6, further comprising:

manipulating the object representing the business rule using an object-oriented programming tool.

11. The method of claim 10, further comprising:

converting the manipulated object representing the business rule into a data structure usable by the business application.

12. The method of claim 11, wherein the data structure is a database table.

13. The method of claim 10, further comprising:

loading the data structure into the business application to affect a functionality of the business application.

14. The method of claim 6, wherein defining an object-oriented programming language class to model a business rule comprises:

including source code equivalents from the business rule from the business application in the class.

15. A system for modeling a business rule from a business application in an object-oriented programming language, comprising:

an identifying component adapted to identify a plurality of operations that comprise the business rule;

an transformation component adapted to define an object-oriented programming language class to model the business rule, wherein the class includes a method corresponding to the plurality of operations that comprise the business rule; and

an tool component adapted to instante an object from the class, wherein the object represents the business rule.

16. The system of claim 15, wherein identifying a plurality of operations that comprise the business rule comprises:

traversing a table used by the business application.

17. The system of claim 15, further comprising:

an object-oriented code analysis component for detecting a problem associated with the object representing the business rule using an object-oriented programming tool, wherein the problem corresponds to a defect in the business rule.

18. The system of claim 15, further comprising:

a user interface for manipulating the object representing the business rule using an object-oriented programming tool.

19. The system of claim 18, further comprising:

a converting component adapted to convert the manipulated object representing the business rule into a data structure usable by the business application.

20. The system of claim 15, further comprising:

a communications interface for loading the data structure into the business application to affect a functionality of the business application.