IODBInput/Output Data Base
References in periodicals archive ?
While legacy systems evolve at a very slow rate, the IODB and the applications that utilize it evolve at a very high rate.
By treating the legacy data as objects whose definitions are immutable, and by treating the IODB as a dynamic object system whose definition is fluid, allows data integration issues to be viewed as object mapping.
In this case the definition of the IODB is rather fluid, but the applications are expected to continue to work as the IODB changes.