|
Ideal provides legacy migration services via a proprietary
redevelopment methodology that recreates an equivalent application in the targeted
architecture. The process is both rapid and highly cost affective. No conversion
or translation tools are utilized, rather, Ideal uses your current application
as the prototype for the target application.
Architecture
Ideal will redevelop your legacy applications with
your choice of one of the following architectures:
All projects start with the development of an architecture document, so that we
can address your standards and development conventions.
No Magic Bullet
Ideal redevelopes legacy applications by hand, because we've learned through
experience that conversion and translation tools don't produce maintainable
software. There are certainly cases where these tools are suitable, but
most often, legacy applications have an evolutionary future, wherein
management realizes the need to adapt features and functionality over time.
Conversion and translation tools are not effective at providing output
that lends itself to adaptation. Moreover, Ideal will demonstrate how
our methodology saves money up front, as well as over the long haul.
|
|
Here's how it works: |
Let's say your company has a PowerBuilder 9 application that you wish to migrate to J2EE,
.Net or PHP. Our project team will start by identifying each screen within the
application. Next, with a visual representation of the screen in hand, we define the
relationship of each screen to the database(s). Finally, we define the business logic
code functions that create actions within the screen, such as what happens when a
button is selected or if an item is chosen in a dropdown box.
Now we have the foundation of your application within a specification document that
uses your current application, in its legacy form, as a prototype. This prototype,
along with the specification, serve as the blueprint for the target application. Coding
begins with screen design. Depending on your current architecture, for instance,
PowerBuilder, there are elements that cannot be replicated exactly within web based
software. So, our project team finds alternative solutions and presents them to you
for approval. Items like tabs in PowerBuilder work a little different in web apps.
With the screens approved, we start tying code to the database - matching each
field on a screen with the appropriate table and field within the appropriate database.
Sticking to the PowerBuilder example, chances are you would be migrating from Sybase
to an alternative database at the same time. If so, we migrate all stored procedures
to the target database, whether it be Oracle, SQL or MYSQL. If not, we tie our code to
the current database.
Next, we're ready to start developing business logic code that will cause things to
happen in your application. Logic such as user permissions is created and implemented.
Soon, we are ready to start with data testing and beyond that, user and functional
testing. Finally, we deliver your new software and you now own a well-written
application that can easily be maintained and modified by your staff, Ideal, or the
vendor of your choosing.
|
|
