Powerbuilder to Java Tools-based Migration скачать в хорошем качестве

Powerbuilder to Java Tools-based Migration

Arkin Software offers complete migration solution to retire Power Builder Applications. It is a tools based migration framework- comprising of a automated tools; migration methodology; and experienced consultants that facilitate factory-like precision. There are three Converter tools. (a) GUI converter converts legacy GUI into web-structure, RIA technologies or thin-client GUI, with similar look & feel. (b) Code converter converts business logic of the legacy code into equivalent java. (c) DAO converter converts SQL calls into a chosen persistent framework like SPRING JDBC or JDBC. Besides these, there are two extremely important tools. (d) Analyzer: It is this tool that helps us even if there is limited or non-existent documentation and application knowledge. This tool dives through legacy code, builds metrics and relationships to help our team to size and understand the legacy complexity and accurately estimate the migration effort. (e) Traceability Generator: It maps legacy code to converted java code in a spreadsheet format. This traceability matrix serves two purposes: One is to ensure that no legacy code is missed out during conversion; and the other is to facilitate client’s internal teams to catch up with migrated Java code. Arkin Software’s unique approach to migration is architecture-centric. That means, we start with the target architecture and migrate the legacy to that target. Never one-to-one migration. Because, migrated applications must live in production for another 20-25 years, which is possible only if they are built on right architecture. Nobody likes applications that may look like Java, but stink like legacy. Arkin Software offers tools based approach to convert 2-tier client/server applications to 3-tier or multi-tier Java based web architecture. The legacy client/server is a 2-tier application. Business logic and data access is partly coded on the UI side, and partly in the form of stored procedures running on database server. During migration, the code is segregated into different layers like - UI, Business logic, Communication, and DAO layers. The database system can remain the same, or that can also be migrated to a different one. If you prefer to have similar GUI after migration, it is possible, as it minimizes end-user re-training. If you prefer to have adaptive RIA UI to work on multiple form-factor devices, that is possible too.