The rationale for software wrapping

The pressure to replace legacy software systems is growing. It is becoming increasingly difficult to fulfil the requirements of a heterogeneous, distributed business world with centralized, monolithic host-based software systems. The author considers software wrapping where old code is left in its native environment and is connected to the new object-oriented software by an API or a CORBA type interface. It is possible to define business objects on the client side while using existing mainframe batch programs and online transactions on the server side as methods