SneedMajnar98 |
PublicReengineering Wiki |
|
| Report of a pilot project at the German Savings and Loan Organisation. Part of a project to help member banks migrate from their mainframes to more flexible
distributed OO systems.
They recognise systems could be rewritten, incrementally reengineered or wrapped. The differentiate different levels of encapsulation (wrapping) as being: job
encapsulation; transaction encapsulation; program encapsulation; module encapsulation; and procedure encapsulation.
The pilot project concentrated on opening a chequing account for a customer.
They suggest it is worth considering reengineering the legacy code before wrapping. This will reduce the wrapping effort and future maintenance.
They adopted a 5 step testing strategy: first test the wrapped program, then the wrapper, then the wrapper and the wrapped program, next a whole transaction
starting on the client and finally test using several transactions - on after another.
The lessons they learned were: the wrapped program always needs to be amended in order to interface with the wrapper; the weakest link in the chain (and the
bottleneck) is the server to host communication; and it is time consuming to test distributed systems with 3 tier architectures.
flexibility
Related pages: Bibliography |
| This page last edited on 29 October 1999 |