Editing Computer-aided maintenance (section)

==Strategies for finding fixes==
#The ''bubble-up'' strategy simply records pairs of symptoms and fixes. The most frequent set of pairs is then presented as a tentative solution, which is then attempted. If the fix works, that fact is further recorded, along with the configuration of the presenting system, into a ''solutions database''.
#Oddly enough, shutting down and [[booting]] up again manages to 'fix,' or at least 'mask,' a [[computer bug|bug]] in many computer-based systems; thus ''reboot'' is the remedy for distressingly many symptoms in a 'fix database.' The reason a reboot often works is that it causes the [[RAM]] to be flushed. However, typically the same set of actions are likely to create the same result demonstrating a need to refine the "startup" applications (which launch into memory) or install the latest fix/patch of the offending application.
#Currently, most expertise in finding fixes lies in human domain experts, who simply sit at a replica of the computer-based system, and who then 'talk through' the problem with the client to duplicate the problem, and then relate the fix.