The Delta Insurance Company is having a policyholder subsystem which has started giving trouble. Over the years, the application evolved from using fixed length, multi-record type files to using a hierarchic database to using a relational database. The programs did not change much, but the data structures changed radically. Program code was patched to provide for the new data structure. The amount of people-time allocated to policyholder maintenance grew 15% per year over the last five years and is now costing as much per year as it did in 1980 to develop the original application. No one ever considered reevaluating the subsystem for redevelopment, but they would like to now. Upon inspection, the documentation was found to be up-to-date and includes flow charts and data flow diagrams. There are no current diagrams of the data structure. There are also no historical files of decisions or of changes. Apply the concepts of change management to discuss how should the company get this application in order? What type( s) of maintenance should they consider for the next set of changes?