Software update management system with update chronology generator

Abstract

An update management system provides access to software updates (patches and upgrades) and to an update catalog server. The catalog server includes a chronology generator. When a request for an update family tree for a target update is received, the chronology generator accesses an index to find the database and record number for the target update. The record is retrieved, indicating updates superseded by the target update and updates superseding the target update. Records for the superseded and superseding updates are, in turn, retrieved. The process is iterated until there are no further superseding and no superseded updates indicated. The succession relations indicated in the retrieved records are arranged into a family tree for the target patch. The family tree can be used (along with dependency data) to help determine an update for a given workstation that optimizes performance and compatibility. Optionally, the family tree can be used to generate an update state list to assist in the optimization.

What is claimed is:  
     
         1 . A software-update management system comprising: 
 an input for receiving a request for an update chronology for a target update;    an interface for retrieving succession data from a set of databases, said databases having a record for each update, each record indicating all updates that the associated update directly supercedes; and    an update chronology generator for generating an update chronology for said target update by accessing the records for said target update and each update indicated by the record for said target update as being directly superceded by said target update, said generator being coupled to said input and to said interface.    
     
     
         2 . An update management system as recited in  claim 1  wherein said update chronology generator further accesses records for each update succeeding said target update, said update chronology further indicating all updates succeeding said target update directly or indirectly, the database record for each update indicating any updates directly superceding the respective update.  
     
     
         3 . An update management system as recited in claims  1  wherein said update chronology is an update family tree.  
     
     
         4 . An update management system as recited in claims  1  wherein each record indicates an introduction date for the respective update, said update chronology being a succession of update states.  
     
     
         5 . An update management system as recited in  claim 1  through A 4  further comprising said update database.  
     
     
         6 . A method of generating an update history, said method comprising: 
 a) receiving a request for an update chronology for a target update;    b) accessing a record for said target update in a database, said record indicating updates directly superceded by said target update;    c) accessing records for said updates directly superceded by said target update to determine updates indirectly superceded by said target update; and    d) generating an update chronology from said records, said update chronology indicating updates directly and indirectly superceded by said target update    
     
     
         7 . A method as recited in  claim 6  wherein said records identify an update, if any, superceding the respective update, step c) further involving accessing the record of any update indicated as directly succeeding said target update, said update chronology indicating updates directly and indirectly superceding said target update.  
     
     
         8 . A method as recited in claims  6  wherein said update chronology is an update family tree.  
     
     
         9 . A method as recited in claims  6  wherein each update record indicates an introduction date for the respective update, said update chronology is a succession of update states.