Code morphing manager

• US 20040172637A1
• Filed: 02/28/2003
• Published: 09/02/2004
• Est. Priority Date: 02/28/2003
• Status: Abandoned Application

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Koutyrine, Oleg
• Application Number:
  US10/375,141
• Publication Number:
  US 20040172637A1
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 8/52 Binary to binary

Abstract

Embodiments of the present invention provide a method and system for converting software from a source version to a target version. In one embodiment, a plurality of code morphers may be associated based on the input version and the output version of each code morpher. A sequerice of code morphers may be determined based on the source version and the target version, and then applied to the software. In another embodiment, a graph having a plurality of nodes and a plurality of edges between the nodes may be created. Each of the plurality of nodes may correspond to a version, while each of the plurality of edges may correspond to a code morpher. A path through the graph may be constructed from a source node, associated with the source version, to a target node associated with the target version. A sequence of code morphers may be determined from the path and then applied to the software. In a further embodiment, a finite state automata having a plurality of states and a plurality of transitions between the states may be created. Each of the plurality of states may correspond to a version, while each of the plurality of transitions may correspond to a code morpher. A path through the finite state automata may be constructed from a start state, associated with the source version, to an accept state associated with the target version. A sequence of code morphers may be determined from the path and then applied to the software.

Claims

1. A method for converting software from a source version to a target version, comprising:

creating a graph having a plurality of nodes and a plurality of edges, each of the plurality of nodes corresponding to a version and each of the plurality of edges corresponding to a code morpher having an input version and an output version;

constructing a path from a source node, associated with the source version, to a target node associated with the target version;

determining a sequence of code morphers based on the path; and

applying the sequence of code morphers to the software.

2. The method of claim 1, wherein the path comprises a shortest path between the source node and the target node.

3. The method of claim 1, wherein the path comprises an optimum path between the source node and the target node.

4. The method of claim 1, wherein the input version of a first code morpher in the sequence equals the source version, and the output version of a last code morpher in the sequence equals the target version.

5. The method of claim 4, wherein the input version of each code morpher after the first code morpher in the sequence is equal to the output version of an immediately preceding code morpher in the sequence.

6. The method of claim 5, wherein the output version of each code morpher before the last code morpher in the sequence is equal to the input version of an immediately succeeding code morpher in the sequence.

7. The method of claim 1, wherein the software includes a plurality of elements associated with a runtime framework.

8. The method of claim 7, wherein:

the source version is associated with a first runtime framework version; and

the target version is associated with a second runtime framework version.

9. The method of claim 8, wherein said applying the sequence of code morphers comprises:

for each code morpher in the sequence of code morphers;

identifying at least one of the plurality of elements; and

converting each of the identified elements from the input version to the output version.

10. The method of claim 9, wherein the plurality of elements include variables.

11. The method of claim 9, wherein the plurality of elements include data structures.

12. The method of claim 9, wherein the plurality of elements include classes.

13. The method of claim 9, wherein the plurality of elements include functions.

14. A computer readable medium including instructions adapted to be executed by at least one processor to implement a method for transforming software from a source version to a target version, the method comprising:

creating a graph having a plurality of nodes and a plurality of edges, each of the plurality of nodes corresponding to a version and each of the plurality of edges corresponding to a code morpher having an input version and an output version;

constructing a path from a source node, associated with the source version, to a target node associated with the target version;

determining a sequence of code morphers based on the path; and

applying the sequence of code morphers to the software.

15. The computer readable medium of claim 14, wherein the path comprises at least one of a shortest path and an optimum path.

16. The computer readable medium of claim 14, wherein the input version of a first code morpher in the sequence equals the source version, and the output version of a last code morpher in the sequence equals the target version.

17. The computer readable medium of claim 16, wherein the input version of each code morpher after the first code morpher in the sequence is equal to the output version of an immediately preceding code morpher in the sequence.

18. The computer readable medium of claim 17, wherein the output version of each code morpher before the last code morpher in the sequence is equal to the input version of an immediately succeeding code morpher in the sequence.

19. The computer readable medium of claim 14, wherein the software includes a plurality of elements associated with a runtime framework.

20. The computer readable medium of claim 19, wherein:

the source version is associated with a first runtime framework version; and

the target version is associated with a second runtime framework version.

21. The computer readable medium of claim 20, wherein said applying the sequence of code morphers comprises:

for each code morpher in the sequence of code morphers;

identifying at least one of the plurality of elements; and

converting each of the identified elements from the input version to the output version.

22. The computer readable medium of claim 21, wherein the plurality of elements include at least one of variables, data structures, classes and functions.

23. A system for transforming application software from an application programming interface source version to an application programming interface target version, comprising:

a processor; and

a memory, coupled to the processor, storing the application software and instructions adapted to be executed by the processor to;

create a graph having a plurality of nodes and a plurality of edges, each of the plurality of nodes corresponding to a version and each of the plurality of edges corresponding to a code morpher having an input version and an output version,

construct a path from a source node associated with the source version, to a target node associated with the target version,

determine a sequence of code morphers based on the path, and

apply the sequence of code morphers to the software.

24. The system of claim 23, wherein the path comprises at least one of a shortest path and an optimum path.

25. The system of claim 23, wherein the input version of a first code morpher in the sequence equals the source version, and the output version of a last code morpher in the sequence equals the target version.

26. The system of claim 25, wherein the input version of each code morpher after the first code morpher in the sequence is equal to the output version of an immediately preceding code morpher in the sequence.

27. The system of claim 26, wherein the output version of each code morpher before the last code morpher in the sequence is equal to the input version of an immediately succeeding code morpher in the sequence.

28. The system of claim 24, wherein the software includes a plurality of elements associated with a runtime framework.

29. The system of claim 28, wherein:

the source version is associated with a first runtime framework version; and

the target version is associated with a second runtime framework version.

30. The system of claim 29, wherein said apply the sequence of code morphers comprises:

for each code morpher in the sequence of code morphers;

identify at least one of the plurality of elements; and

convert each of the identified elements from the input version to the output version.

31. The system of claim 30 wherein the plurality of elements include at least one of variables, data structures, classes and functions.

32. A method for converting software from a source version to a target version, comprising:

associating a plurality of code morphers based on an input version and an output version of each code morpher;

determining a sequence of code morphers based on the source version and the target version; and

applying the sequence of code morphers to the software.

33. The method of claim 32, wherein the input version of a first code morpher in the sequence equals the source version, and the output version of a last code morpher in the sequence equals the target version.

34. The method of claim 33, wherein the input version of each code morpher after the first code morpher in the sequence is equal to the output version of an immediately preceding code morpher in the sequence.

35. The method of claim 34, wherein the output version of each code morpher before the last code morpher in the sequence is equal to the input version of an immediately succeeding code morpher in the sequence.

36. The method of claim 35, wherein the software includes a plurality of elements associated with at least one runtime framework.

37. A method for converting software from a source version to a target version, comprising:

creating a finite state automata having a plurality of states and a plurality of transitions, each of the plurality of states corresponding to a version and each of the plurality of transitions corresponding to a code morpher having an input version and an output version;

constructing a path from a start state, associated with the source version, to an accept state, associated with the target version;

determining a sequence of code morphers based on the path; and

applying the sequence of code morphers to the software.

38. The method of claim 37, wherein the path comprises a shortest path between the start state and the accept state.

39. The method of claim 37, wherein the path comprises an optimum path between the start state and the accept state.

40. The method of claim 37, wherein the software includes a plurality of elements associated with a runtime framework.

41. The method of claim 40, wherein:

the source version is associated with a first runtime framework version; and

the target version is associated with a second runtime framework version.

42. The method of claim 41, wherein said applying the sequence of code morphers comprises:

for each code morpher in the sequence of code morphers;

identifying at least one of the plurality of elements; and

converting each of the identified elements from the input version to the output version.