Code morphing manager

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.

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.

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.

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.