Improved change tracking for software maintenance

The authors demonstrate the usefulness of change tracking information from the maintenance programmer's perspective. They split the data into logical groups and find the connections between these groups. They describe a method to incorporate problem-solving information in a change tracking database. Problem solving is discussed with regard to structured problem-solving techniques for isolating difficult problems. A relational database structure and queries to access the database are discussed. An example of how the change tracking system supports the maintenance problem-solving process is also included.<<ETX>>