Gordian Knot Summary

The separation of the user interface from data integrity reduces a very knotty problem into two parts that are easier to handle. If this cannot be done, a three-part solution is possible using ODS. The ODS option keeps an either-or situation from being forced on the mainframe and permits gradual implementation of the new architecture. The ODS option has a significant humanware development and maintenance cost. ODBC is the cheapest and fastest solution.

The business rules should not be left in the application. Business rules should move to the database or the ODS server. Leaving the business rules in the application will result in increasing evolutionary maintenance costs and a rapid regeneration of the knot.