90 likes | 101 Views
ELISA 2003 Observations on automation in cross-platform migration. Authors: Ben Wilson and Tony Van der Beken Anubex. Who are we Overview, Anubex. Belgian Software Company; Experts in Cross-Platform IS Migration; Operates internationally with migration partner companies;
E N D
ELISA 2003Observations on automation in cross-platform migration Authors: Ben Wilson and Tony Van der Beken Anubex
Who are weOverview, Anubex • Belgian Software Company; • Experts in Cross-Platform IS Migration; • Operates internationally with migration partner companies; • Early platform-independent adopter of Application Migration and Rehosting as a viable evolution strategy; • First products were migration to Oracle and standard Oracle Development tools; • Migration without proprietary runtimes; • Influencing contributors to the OMG standardisation initiative on legacy transformation.
Why this paperMotivations • We’ve been doing this for ten years; • When we started, people were sceptical of the approach; • Acceptance has grown and demand has increased, but not much attention is being paid to research in this field; • We would like to help researchers and the industry to better understand this approach and how it works.
Cross-Platform MigrationBasis of study • Some 50 cases in Europe involving the migration of software with over .5 MLOC
Cross-Platform MigrationWhat for • Actual cross-platform migration from endangered or proprietary hardware platforms to ‘open’ distributed systems (mainly Unix or NT), or from endangered development environments to modern development tools and deployment platforms (mainly application servers such as WebSphere, etc.); • Retargeting applications from data access methods that pre-date RDBMS (networked databases, hierarchical databases, or (index) sequential files) to an RDBMS product (mainly Oracle or DB2).
100% functional, visual equivalenceBenefits • Customer protection; • A concrete frame of reference to drive the project; • Change management and overall business disruption are minimal (limited to the IT department); • Easier to test, no danger of “scope creep”; • Eliminates need for functional analysis, eliminates need for writing specifications; • No unrealistic expectations of users (user retraining rarely required; users can focus on their jobs, not on software development).
ConsequencesHow the approach impacts the organisation • How the organisation justifies project expenditure; • How technical complexity is defined and how this impacts cost to the organisation; • What restrictions are placed on large, constantly evolving systems during the transitory period; • How software maintainers adapt to working with the new technologies.
Thank You • For more info, visit www.anubex.com