Abstract: Functional wrappers are scripts and related software that provide a way to group and invoke functionality comprising semantic intent in a legacy application. These functional wrappers allow programmatic access to functionality in legacy applications in contemporary software architectures without risk of porting errors. Additional functionality to provide features with presently expected, but not available at the time the legacy applications were developed, such as functional wrappers to provide parallelism and scaling, are disclosed. Finally, automatic generation of the functional wrappers are also disclosed.

Abstract: Functional wrappers are scripts and related software that provide a way to group and invoke functionality comprising semantic intent in a legacy application. These functional wrappers allow programmatic access to functionality in legacy applications in contemporary software architectures without risk of porting errors. Additional functionality to provide features with presently expected, but not available at the time the legacy applications were developed, such as functional wrappers to provide parallelism and scaling, are disclosed. Finally, automatic generation of the functional wrappers are also disclosed.

Abstract: Functional wrappers are scripts and related software that provide a way to group and invoke functionality comprising semantic intent in a legacy application. These functional wrappers allow programmatic access to functionality in legacy applications in contemporary software architectures without risk of porting errors. Additional functionality to provide features with presently expected, but not available at the time the legacy applications were developed, such as functional wrappers to provide parallelism and scaling, are disclosed. Finally, automatic generation of the functional wrappers are also disclosed.

Abstract: User interfaces of a software platform that generates transformed code from source code enable interaction with the codes. In various embodiments, the software platform may store the source code and the transformed code in a data store. The transformed code is a transformation of the source code by at least one business semantic preserving code transform. The at least one business semantic preserving transform causes an execution of the transformed code in a new execution scenario to produce an identical semantic effect as an execution of the source code in an old execution scenario. Subsequently, the software platform may cause a display of a user interface of the application on a display device. The user interface may provide one or more user command items for manipulating at least one of the source code or the transformed code stored in the data store.

Abstract: Techniques to automatically port applications to a mobile infrastructure using code separation with semantic guarantees are disclosed. Porting enterprise applications from to a target architecture another is effected via separating code into constituent layers of the target architecture. To preserve semantics, code transformations are enforced via an abstract syntax tree structure. The generated code may have various code wrappers and/or infrastructure elements so the ported application will operate in the target architecture. Various techniques are disclosed regarding specific code wrappers and/or infrastructure elements to address operating issues including, but not limited to, architectural issues, network latency, framework changes, regulatory issues.

Abstract: Techniques to automate the transformation of an application involving programming language constructs from a composite of source grammars to a composite of target grammars, while maintaining the fidelity of the program semantics and functionality, or extending or changing it to explode the capabilities and avoid the limitations of new technologies are disclosed. The different stages of the transformation are persisted in an annotated abstract syntax tree where the annotations represent semantic preserving transformation rules. The abstract syntax tree is then transformed according to the transformational rules. The transformed abstract syntax tree may then be traversed to generate a new translated source code application or be queried to generate output reports. Alternatively, the transformed abstract syntax tree may be subjected to another transformation as part of a chain of transformations.

Abstract: Systems for creating, generating, distributing and applying self-contained modifications (i.e., changes) to source code are described herein. At least some embodiments include a system including a client computer with processing logic, a storage device (including source code files), and a communication interface. The interface receives a container file including a transformation including a search pattern that identifies source code segments, and transformation instructions that modify the source code based at least partially on identified code segments. Processing logic software searches a representation of the source code for search pattern occurrences, and identifies the source code segments that include elements with structure and relationships that are matched by the corresponding elements represented by the search pattern.

Abstract: User interfaces of a software platform that generates transformed code from source code enable interaction with the codes. In various embodiments, the software platform may store the source code and the transformed code in a data store. The transformed code is a transformation of the source code by at least one business semantic preserving code transform. The at least one business semantic preserving transform causes an execution of the transformed code in a new execution scenario to produce an identical semantic effect as an execution of the source code in an old execution scenario. Subsequently, the software platform may cause a display of a user interface of the application on a display device. The user interface may provide one or more user command items for manipulating at least one of the source code or the transformed code stored in the data store.

Abstract: Techniques to automate the transformation of an application involving programming language constructs from a composite of source grammars to a composite of target grammars, while maintaining the fidelity of the program semantics and functionality, or extending or changing it to explode the capabilities and avoid the limitations of new technologies are disclosed. The different stages of the transformation are persisted in an annotated abstract syntax tree where the annotations represent semantic preserving transformation rules. The abstract syntax tree is then transformed according to the transformational rules. The transformed abstract syntax tree may then be traversed to generate a new translated source code application or be queried to generate output reports. Alternatively, the transformed abstract syntax tree may be subjected to another transformation as part of a chain of transformations.

Abstract: Techniques to automatically port applications to a mobile infrastructure using code separation with semantic guarantees are disclosed. Porting enterprise applications from to a target architecture another is effected via separating code into constituent layers of the target architecture. To preserve semantics, code transformations are enforced via an abstract syntax tree structure. The generated code may have various code wrappers and/or infrastructure elements so the ported application will operate in the target architecture. Various techniques are disclosed regarding specific code wrappers and/or infrastructure elements to address operating issues including, but not limited to, architectural issues, network latency, framework changes, regulatory issues.

Abstract: Systems for creating, generating, distributing and applying self-contained modifications (i.e., changes) to source code are described herein. At least some embodiments include a system including a client computer with processing logic, a storage device (including source code files), and a communication interface. The interface receives a container file including a transformation including a search pattern that identifies source code segments, and transformation instructions that modify the source code based at least partially on identified code segments. Processing logic software searches a representation of the source code for search pattern occurrences, and identifies the source code segments that include elements with structure and relationships that are matched by the corresponding elements represented by the search pattern.