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: A transformation application may transform source code into transformed code using extensibility libraries. The transformation application may receive an extensibility library and the source code. The extensibility library may include one or more transformation directives that specify a business semantic preserving transform. Accordingly, the transformation application may transform a source application into a transformed application using the business semantic preserving transform. The business semantic preserving transform may change one or more original architectural classes of the source application potentially spanning multiple tiers or devices into one or more transformed architectural classes of the transformed application, in which the one or more transformed architectural classes are different from the one or more original architectural classes.

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: 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: A transformation application may transform source code into transformed code using extensibility libraries. The transformation application may receive an extensibility library and the source code. The extensibility library may include one or more transformation directives that specify a business semantic preserving transform. Accordingly, the transformation application may transform a source application into a transformed application using the business semantic preserving transform. The business semantic preserving transform may change one or more original architectural classes of the source application potentially spanning multiple tiers or devices into one or more transformed architectural classes of the transformed application, in which the one or more transformed architectural classes are different from the one or more original architectural classes.

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.