as will be appreciated by one skilled in the art , aspects of the present invention may be embodied as a system , method or computer program product . accordingly , aspects of the present invention may take the form of an entirely hardware embodiment , an entirely software embodiment ( including firmware , resident software , micro - code , etc .) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “ circuit ,” “ module ” or “ system .” furthermore , aspects of the present invention may take the form of a computer program product embodied in one or more computer - readable medium ( s ) having computer - readable program code / instructions embodied thereon . any combination of computer - readable media may be utilized . computer - readable media may be a computer - readable signal medium or a computer - readable storage medium . a computer - readable storage medium may be , for example , but not limited to , an electronic , magnetic , optical , electromagnetic , infrared , or semiconductor system , apparatus , or device , or any suitable combination of the foregoing . more specific examples ( a non - exhaustive list ) of a computer - readable storage medium would include the following : an electrical connection having one or more wires , a portable computer diskette , a hard disk , a random access memory ( ram ), a read - only memory ( rom ), an erasable programmable read - only memory ( eprom or flash memory ), an optical fiber , a portable compact disc read - only memory ( cd - rom ), an optical storage device , a magnetic storage device , or any suitable combination of the foregoing . in the context of this document , a computer - readable storage medium may be any tangible medium that can contain , or store a program for use by or in connection with an instruction execution system , apparatus , or device . a computer - readable signal medium may include a propagated data signal with computer - readable program code embodied therein , for example , in baseband or as part of a carrier wave . such a propagated signal may take any of a variety of forms , including , but not limited to , electro - magnetic , optical , or any suitable combination thereof . a computer - readable signal medium may be any computer - readable medium that is not a computer - readable storage medium and that can communicate , propagate , or transport a program for use by or in connection with an instruction execution system , apparatus , or device . program code embodied on a computer - readable medium may be transmitted using any appropriate medium , including but not limited to wireless , wireline , optical fiber cable , rf , etc ., or any suitable combination of the foregoing . computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages , including an object oriented programming language such as java , smalltalk , c ++ or the like and conventional procedural programming languages , such as the “ c ” programming language or similar programming languages . the program code may execute entirely on a user &# 39 ; s computer , partly on the user &# 39 ; s computer , as a stand - alone software package , partly on the user &# 39 ; s computer and partly on a remote computer or entirely on the remote computer or server . in the latter scenario , the remote computer may be connected to the user &# 39 ; s computer through any type of network , including a local area network ( lan ) or a wide area network ( wan ), or the connection may be made to an external computer ( for example , through the internet using an internet service provider ). aspects of the present invention are described below with reference to flowchart illustrations and / or block diagrams of methods , apparatus ( systems ) and computer program products according to embodiments of the invention . it will be understood that each block of the flowchart illustrations and / or block diagrams , and combinations of blocks in the flowchart illustrations and / or block diagrams , can be implemented by computer program instructions . these computer program instructions may be provided to a processor of a general purpose computer , special purpose computer , or other programmable data processing apparatus to produce a machine , such that the instructions , which execute via the processor of the computer or other programmable data processing apparatus , create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks . these computer program instructions may also be stored in a computer - readable medium that can direct a computer , other programmable data processing apparatus , or other devices to function in a particular manner , such that the instructions stored in the computer - readable medium produce an article of manufacture including instructions which implement the function / act specified in the flowchart and / or block diagram block or blocks . the computer program instructions may also be loaded onto a computer , other programmable data processing apparatus , or other devices to cause a series of operational steps to be performed on the computer , other programmable apparatus or other devices to produce a computer - implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks . the present invention will now be described in detail with reference to the figures . fig1 is a functional block diagram illustrating a computer system , in accordance with an embodiment of the present invention . fig1 provides only an illustration of one embodiment and does not imply any limitations with regard to the environments in which different embodiments may be implemented . in the depicted embodiment , computer system 10 may be a desktop computer , laptop computer , tablet computer , personal digital assistant ( pda ), or smart phone . in other embodiments , computer system 10 may represent any electronic device or computer system capable of sending and receiving data and executing program instructions . computer system 10 includes a software installer program 20 , software installation files 30 , software signatures 40 , and software signature capturing program 50 . software installer program 20 operates to install , uninstall , and manage software on computer system 10 . in one embodiment , software installer program 20 resides on computer system 10 . in other embodiments , software installer program 20 may reside on another computer system or computing device , provided that software installer program 20 has access to software installation files 30 and that software installer program 20 can communicate with computer system 10 . for example , software installer program 20 may reside on a computing device connected to computer system 10 over a network ( such as a local area network , wide area network , the internet , or any combination thereof ). software installation files 30 are files that may be read by software installer program 20 . in one embodiment , software installation files 30 may be in the form of standalone files , an archive of files , an executable file , or any combination thereof . in one embodiment , software installation files 30 resides on computer system 10 . in other embodiments , software installation files 30 may reside on another computer system or computing device , provided that software installation files 30 is accessible to software installer program 20 . for example , software installation files 30 may reside on a computing device connected to computer system 10 over a network ( such as a local area network , wide area network , the internet , or any combination thereof ). software signatures 40 may be a file written to and read by software signature capturing program 50 . in another embodiment , software signatures 40 may be a database such as oracle ® or an ibm ® bd2 ® database . in one embodiment , software signatures 40 resides on computer system 10 . in other embodiments , software signatures 40 may reside on another computer system or computing device , provided that software signatures 40 is accessible to software signature capturing program 50 . for example , software signatures 40 may reside on a computing device connected to computer system 10 over a network ( such as a local area network , wide area network , the internet , the public switched telephone network , or any combination thereof ). in one embodiment , software signatures 40 includes one or more software signatures determined by software signature capturing program 50 . a software signature is associated with a software package installed on computer system 10 . a software signature may be a listing of any file added to or modified on computer system 10 after a software package is installed to the clean system ( i . e . computer system 10 includes only software signature capturing program 50 , apart from the software required to run the system , such as an operating system ). software signatures 40 may also include snapshots of computer system 10 . the snapshot of a computer system may include the names and locations of all files residing on that computer system at the time of the snapshot . the snapshot may store additional information associated with each file in the snapshot including , but not limited to , file size , creation date , and date last modified . software signatures 40 may include multiple snapshots per computer system , each snapshot corresponding with a different state ( i . e . amount of software installed on the computer system at any given time ) of the computer system . software signatures 40 may also include a score associated with each software signature stored by software signature capturing program 50 . software signature capturing program 50 operates to determine and score a software signature for a software package installed on computer system 10 . software signature capturing program 50 also operates to store snapshots of computer system 10 . the snapshot of a computer system may include the names and locations of all files residing on that computer system at the time of the snapshot . in one embodiment , software signature capturing program 50 resides on computer system 10 . in another embodiment , software signature capturing program 50 may be a function of software installer program 20 . in other embodiments , software signature capturing program 50 may reside on another computer system or computing device , provided that software signature capturing program 50 has access to computer system 10 and software signatures 40 , and provided that software signature capturing program 50 can communicate with software installer program 20 . for example , software signature capturing program 50 may reside on a computing device connected to computer system 10 over a network ( such as a local area network , wide area network , the internet , or any combination thereof ). fig2 depicts a flowchart of software signature capturing program 50 for determining and scoring a software signature for a software package in accordance with one embodiment of the present invention . initially , multiple software packages ( i . e . multiple programs to be installed ) are selected for which software signatures and corresponding scores are to be generated . the installation files for these software packages are in software installation files 30 . in one embodiment , software signature capturing program 50 is started by the user . in step 200 , software signature capturing program 50 captures a snapshot of computer system 10 . computer system 10 initially includes only software signature capturing program 50 apart from software required to run the system , such as an operating system ( i . e . computer system 10 is a ‘ clean ’ system ). to create snapshots , software signature capturing program 50 traverses the entire local storage of computer system 10 and creates a listing of the names and locations of all files residing computer system 10 at the time of the snapshot . the snapshot may store additional information associated with each file in the snapshot including , but not limited to , file size , creation date , and date last modified . software signature capturing program 50 stores this snapshot in software signatures 40 as the pre - install system snapshot ( i . e . the clean system snapshot ). software installer program 20 is executed to install a software package from software installation files 30 to computer system 10 . in one embodiment , the execution of software installer program 20 may be initiated by another program . for example , a program running on a computing device connected to computer system 10 over a network may send an indication to software installer program 20 , residing on computer system 10 , to begin installing the software package . in another embodiment , execution of software installer program 20 may be initiated by a user . for example , a user may initiate software installer program 20 to install the software package on computer system 10 . software installer program 20 copies the files pertaining to the software package being installed ( i . e . the ‘ current software package ’) from software installation files 30 to the local storage of computer system 10 . the locations to which the files are copied may be user - defined or prescribed by a configuration file included in the installation files of the current software package . in one embodiment , software installer program 20 sends an indication to software signature capturing program 50 in response to a completed software package installation . in another embodiment , software signature capturing program 50 may monitor the progress of software installer program 20 during the installation of the software package . in another embodiment , software signature capturing program 50 may be a function of software installer program 20 . in another embodiment , software signature capturing program 50 may be started by a user in response to the software package being installed on computer system 10 . in step 210 , in response to the completed installation of the current software package , software signature capturing program 50 captures a snapshot of computer system 10 , which includes the files from the clean system snapshot in addition to the files from the current software package . software signature capturing program 50 stores this snapshot in software signatures 40 as the post - install system snapshot associated with the current software package . software installer program 20 is executed to uninstall ( i . e . remove ) the current software package from computer system 10 . in one embodiment , the execution of software installer program 20 may be initiated by another program . for example , a program running on a computing device connected to computer system 10 over a network may send an indication to software installer program 20 , residing on computer system 10 , to begin uninstalling the software package . in another embodiment , the execution of software installer program 20 may be initiated by a user . for example , a user may initiate software installer program 20 to uninstall the software package from computer system 10 . software installer program 20 removes the files pertaining to the software package from computer system 10 . the locations from which the files are removed may be user - defined or prescribed by a configuration file included in the installation files of the current software package . in one embodiment , software installer program 20 sends an indication to software signature capturing program 50 in response to the completion of the software package removal . in another embodiment , software signature capturing program 50 may monitor the progress of software installer program 20 during the removal of the current software package . in another embodiment , software signature capturing program 50 may be a function of software installer program 20 . in another embodiment , software signature capturing program 50 may be started by a user in response to the current software package being uninstalled from computer system 10 . in step 220 , in response to the removal of the current software package , software signature capturing program 50 captures a snapshot of computer system 10 , which includes the files from the clean system snapshot in addition to the files left over from the removal of the current software package . software signature capturing program 50 stores this snapshot in software signatures 40 as the post - uninstall system snapshot associated with the current software package . in step 230 , software signature capturing program 50 determines the software signature for current software package . in one embodiment , the software signatures for the current software package are obtained by comparing the pre - install system snapshot ( i . e . clean system snapshot ) with the post - install system snapshot associated with the current software package . in one embodiment , any file found in the post - install system snapshot that is not also found in the pre - install system snapshot may be marked as part of the software signature associated with the current software package . in one embodiment , the comparison of system snapshots may occur based only on the filenames in each snapshot . in another embodiment , the comparison may take into account changes in other information associated with each file in the snapshot including , but not limited to , file size , creation date , and date last modified . in step 230 , software signature capturing program 50 further determines whether or not a file found in the post - install system snapshot that is not also found in the pre - install system snapshot is a critical artifact of the software package . a critical artifact is a file that was removed when the software package was uninstalled ( i . e . a critical artifact is a file that is not left behind after the software is uninstalled ). in one embodiment , the critical artifacts for the current software package that was uninstalled are obtained by comparing the post - install system snapshot with the post - uninstall system snapshot associated with the current software package . in one embodiment , any file found in the post - install system snapshot that is not also found in the post - uninstall system snapshot may be marked as a critical artifact of the current software package . in one embodiment , the comparison of system snapshots may occur based only on the filenames in each snapshot . in another embodiment , the comparison may take into account changes in other information associated with each file in the snapshot including , but not limited to , file size , creation date , and date last modified . any files discovered in step 230 that are not also critical artifacts of the uninstalled program are marked as non - critical artifacts ( i . e . files that are left behind after the software has been uninstalled ) of the current software package . in decision 240 , software signature capturing program 50 determines if there is another software package for which a signature and score must be generated . in one embodiment , the installation of software packages on computer system 10 is automatically controlled by another program which sends an indication to software signature capturing program 50 to either wait for another software package to be installed , or to continue running . in another embodiment , a user will indicate whether another software package is to be installed . if software signature capturing program 50 determines that there is another software package to be installed on computer system 10 ( decision 240 , yes branch ), software capturing program 60 returns to step 210 to capture the post - install system snapshot associated with the next software package being installed . if software signature capturing program 50 determines that there is another software package to be installed on computer system 10 ( decision 240 , no branch ), software capturing program 60 continues to step 250 . in step 250 , software signature capturing program 50 determines a score for each software signature determined . the score assigned to each software signature is a measure of how accurately the presence of that software signature can point to the presence of the software package it came from . in one embodiment , the score assigned to each software signature depends on how many times the same file appears in software signatures 40 ( across multiple software packages ) as well as in how many of those appearances is the file a critical artifact . for example , a single file may be a critical artifact for two separate software packages , and also be a non - critical artifact for a third software package . the score for every file begins at unity . for every duplicate appearance of a file in software signatures 40 , the score for that file would be multiplied by a less - than - unity weight ( e . g . 0 . 7 ), and if that appearance is also as a non - critical artifact , the score would be further multiplied by a less - than - unity weight ( e . g . 0 . 5 ). in other embodiments , the scoring and weighting system may differ . software signature capturing program 60 stores the computed software signatures and their respective scores in software signatures 40 . the following descriptions of fig3 a and fig3 b illustrate the determination of a software signature from system snapshots , as well as assigning scores to software signature . fig3 a depicts a use - case scenario of capturing system snapshots and determining and scoring a software signature in accordance with one embodiment of the present invention . table 300 shows the different stages of system snapshots before and after installing ‘ program alpha ’ on a clean system and the subsequent software signature obtained from the system snapshots . in one embodiment , the contents of table 300 would be stored in software signatures 40 . before program alpha was installed , software signature capturing program 50 obtained the system snapshot for the clean system (‘ clean system files ’ column in table 300 ), and files a , b , and c make up the clean system snapshot . after installing program alpha , the post - install system snapshot ( post - install files &# 39 ; column in table 300 ) shows files a , b , c , d , e , f , and g . from these two snapshots it is possible to obtain the software signature for program alpha (‘ signature ’ column in table 300 ) by selecting all of the files that are in the ‘ post - install files ’ but are not in ‘ clean system files ’ ( i . e . the relative complement of ‘ clean system files ’ with respect to ‘ post install files ’). this gives files d , e , f , and g as a software signature for program alpha . similarly , it is possible to identify the critical artifacts (‘ critical artifacts ’ column in table 300 ) by selecting all of the files that are in the ‘ signature ’ column but are not in ‘ post - uninstall files ’ column ( i . e . the relative complement of ‘ post - uninstall files ’ with respect to ‘ signatures ’). this gives files f and g as critical artifacts , and all files for program alpha ( d and e ) are defined to be non - critical artifacts . fig3 b depicts a use - case scenario of assigning scores to software signatures in accordance with one embodiment of the present invention . table 350 depicts the signatures for three installed software packages : program alpha , program gamma , and program zeta . the process for identification of the software signature and critical artifacts of program alpha is explained in fig3 a , and similar methods are used to obtain signatures for exemplary programs gamma and zeta . once the software signatures for each software package have been identified , the software signatures are assigned a score . in one embodiment , scores start at unity , with files multiplied by a weight of 0 . 7 for each duplicate appearance , and also multiplied by 0 . 5 for each occurrence that is a non - critical artifact . for example , file d appears as a non - critical artifact in program alpha ( multiply by 0 . 5 for non - critical artifact ), again as a critical artifact in program gamma ( multiply by 0 . 7 for a repeated file ), and again as a non - critical artifact in program zeta ( multiply by 0 . 5 for non - critical artifact , multiply by 0 . 7 for a repeated file ). the total score for file d is 1 * 0 . 5 * 0 . 7 * 0 . 5 * 0 . 7 = 0 . 123 . scores for software signatures e through g are similarly computed . the highest score is unity , and is only achieved when the file is a critical artifact and is not repeated in the signature of other software packages . fig4 depicts a block diagram of components of computer system 10 in accordance with an illustrative embodiment of the present invention . it should be appreciated that fig4 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented . many modifications to the depicted environment may be made . computer system 10 includes communications fabric 402 , which provides communications between computer processor ( s ) 404 , memory 406 , persistent storage 408 , communications unit 410 , and input / output ( i / o ) interface ( s ) 412 . communications fabric 402 can be implemented with any architecture designed for passing data and / or control information between processors ( such as microprocessors , communications and network processors , etc . ), system memory , peripheral devices , and any other hardware components within a system . for example , communications fabric 402 can be implemented with one or more buses . memory 406 and persistent storage 408 are computer - readable storage media . in this embodiment , memory 406 includes random access memory ( ram ) 414 and cache memory 416 . in general , memory 406 can include any suitable volatile or non - volatile computer - readable storage media . software installer program 20 , software installation files 30 , software signatures 40 , and software signature capturing program 50 are stored in persistent storage 408 for execution by one or more of the respective computer processors 404 via one or more memories of memory 406 . in this embodiment , persistent storage 408 includes a magnetic hard disk drive . alternatively , or in addition to a magnetic hard disk drive , persistent storage 408 can include a solid state hard drive , a semiconductor storage device , read - only memory ( rom ), erasable programmable read - only memory ( eprom ), flash memory , or any other computer - readable storage media that is capable of storing program instructions or digital information . the media used by persistent storage 408 may also be removable . for example , a removable hard drive may be used for persistent storage 408 . other examples include optical and magnetic disks , thumb drives , and smart cards that are inserted into a drive for transfer onto another computer - readable storage medium that is also part of persistent storage 408 . communications unit 410 , in these examples , provides for communications with other data processing systems or devices , including resources of enterprise grid 112 and client devices 104 , 106 , and 108 . in these examples , communications unit 410 includes one or more network interface cards . communications unit 410 may provide communications through the use of either or both physical and wireless communications links . software installer program 20 , software installation files 30 , software signatures 40 , and software signature capturing program 50 may be downloaded to persistent storage 408 through communications unit 410 . i / o interface ( s ) 412 allows for input and output of data with other devices that may be connected to server computer 102 . for example , i / o interface 412 may provide a connection to external devices 418 such as a keyboard , keypad , a touch screen , and / or some other suitable input device . external devices 418 can also include portable computer - readable storage media such as , for example , thumb drives , portable optical or magnetic disks , and memory cards . software and data used to practice embodiments of the present invention , e . g ., software installer program 20 , software installation files 30 , software signatures 40 , and software signature capturing program 50 , can be stored on such portable computer - readable storage media and can be loaded onto persistent storage 408 via i / o interface ( s ) 412 . i / o interface ( s ) 412 also connect to a display 420 . display 420 provides a mechanism to display data to a user and may be , for example , a computer monitor . the programs described herein are identified based upon the application for which they are implemented in a specific embodiment of the invention . however , it should be appreciated that any particular program nomenclature herein is used merely for convenience , and thus the invention should not be limited to use solely in any specific application identified and / or implied by such nomenclature . the flowchart and block diagrams in the figures illustrate the architecture , functionality , and operation of possible implementations of systems , methods and computer program products according to various embodiments of the present invention . in this regard , each block in the flowchart or block diagrams may represent a module , segment , or portion of code , which comprises one or more executable instructions for implementing the specified logical function ( s ). it should also be noted that , in some alternative implementations , the functions noted in the block may occur out of the order noted in the figures . for example , two blocks shown in succession may , in fact , be executed substantially concurrently , or the blocks may sometimes be executed in the reverse order , depending upon the functionality involved . it will also be noted that each block of the block diagrams and / or flowchart illustration , and combinations of blocks in the block diagrams and / or flowchart illustration , can be implemented by special purpose hardware - based systems that perform the specified functions or acts , or combinations of special purpose hardware and computer instructions .