System and method of automatically maintaining and recycling software components

• US 7,590,599 B2
• Filed: 12/22/2006
• Issued: 09/15/2009
• Est. Priority Date: 12/22/2006
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: England, Laurence Edward, Xia, Chenhong
• Primary Examiner(s): Hewitt, II; Calvin L
• Assistant Examiner(s): Qayyum; Zeshan
• Application Number:
  US11/615,894
• Publication Number:
  US 20080154776A1
• Time in Patent Office: 998 Days
• Field of Search: 705/51, 705/52, 726/30
• US Class Current: 705/51
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/62 Uninstallation

Abstract

In one aspect of the disclosure, a computer program product, system and method for maintaining and recycling software components is disclosed. A first set of usage data for one or more software components is recorded. At least one of the plurality of software components is automatically removed if the first set of usage data for the at least one software component meets usage criteria specified in an expiration policy. Access is then provided to the removed software component through a remote server. A second set of usage data is now recorded for the removed software component. The removed software component is automatically re-instated if the second set of usage data meets usage criteria specified in a re-instatement policy.

Claims

1. A method for maintaining software components comprising:

storing one or more of a plurality of software components on a computer;

recording a first set of usage data for the one or more of a plurality of software components;

automatically removing at least one of the plurality of software components from the computer based on the first set of usage data of the at least one software component meeting usage criteria specified in an expiration policy;

transmitting the removed software component to a remote server;

providing access to the removed software component through the remote server;

recording a second set of usage data for the removed software component; and

automatically reinstalling the removed software component on the computer based on the second set of usage data meeting usage criteria specified in a re-instatement policy.

2. The method for maintaining software components of claim 1 wherein the usage data comprises a length of time since a last use of the software component.

3. The method for maintaining software components of claim 1 wherein the usage data comprises a number of times the software component has been accessed.

4. The method for maintaining software components of claim 1 wherein the usage data comprises information regarding utilization of hardware resources by the software component.

5. The method for maintaining software components of claim 1 wherein the expiration policy is a global expiration policy and applies to all or a group of the plurality of software components.

6. The method for maintaining software components of claim 1 wherein the expiration policy is an individual expiration policy and applies to an individual software component.

7. The method for maintaining software components of claim 1 wherein the expiration policy is set by a user of the software components.

8. The method for maintaining software components of claim 1 wherein the usage criteria specified in the expiration policy is a length of time, and the usage data meets the usage criteria if a length of time since the last use of the software component is greater than the length of time in the usage criteria.

9. The method for maintaining software components of claim 1 wherein the usage criteria specified in the expiration policy is a number, and the usage data meets usage criteria if a number of times the software component has been accessed is less than the number in the usage criteria.

10. The method for maintaining software components of claim 1 wherein access to the removed software component is provided through a remotely run web service.

11. A computer program product comprising a computer useable medium having a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:

store one or more of a plurality of software components on a computer;

record a first set of usage data for the one or more of a plurality of software components;

automatically remove at least one of the plurality of software components from the computer based on the first set of usage data of the at least one software component meeting usage criteria specified in an expiration policy;

transmit the removed software component to a remote server;

provide access to the removed software component through the remote server;

record a second set of usage data for the removed software component; and

automatically reinstall the removed software component on the computer based on the second set of usage data meeting usage criteria specified in a re-instatement policy.

12. The computer program product of claim 11 wherein the usage data comprises a length of time since a last use of the software component.

13. The computer program product of claim 11 wherein the usage data comprises a number of times the software component has been accessed.

14. The computer program product of claim 11 wherein the usage data comprises information regarding utilization of hardware resources by the software component.

15. The computer program product of claim 11 wherein the expiration policy is a global expiration policy and applies to all or a group of the plurality of software components.

16. The computer program product of claim 11 wherein the expiration policy is an individual expiration policy and applies to an individual software component.

17. The computer program product for maintaining software components of claim 11 wherein the expiration policy is set by a user of the software components.

18. The computer program product of claim 11 wherein the usage criteria specified in the expiration policy is a length of time, and the usage data meets the usage criteria if a length of time since the last use of the software component is greater than the length of time in the usage criteria.

19. The computer program product of claim 11 wherein the usage criteria specified in the expiration policy is a number, and the usage data meets usage criteria if a number of times the software component has been accessed is less than the number in the usage criteria.

20. The computer program product of claim 11 wherein access to the removed software component is provided through a remotely run web service.

21. A system for maintaining software components comprising:

a computer for storing one or more of a plurality of software components, recording a first set of usage data for the one or more of a plurality of software components, automatically removing at least one of the plurality of software components based on the first set of usage data of the at least one software component meeting usage criteria specified in an expiration policy, providing access to the removed software component through a remote server, recording a second set of usage data for the removed software component, and automatically reinstalling the removed software component based on the second set of usage data meeting usage criteria specified in a re-instatement policy; and

a transmitter for transmitting the removed software component to the remote server.

22. The system of claim 21 wherein the usage data comprises a length of time since a last use of the software component.

23. The system of claim 21 wherein the usage data comprises a number of times the software component has been accessed.

24. The system of claim 21 wherein the usage data comprises information regarding utilization of hardware resources by the software component.

25. The system of claim 21 wherein the expiration policy is a global expiration policy and applies to all or a group of the plurality of software components.

26. The system of claim 21 wherein the expiration policy is an individual expiration policy and applies to an individual software component.

27. The system of claim 21 wherein the expiration policy is set by a user of the software components.

28. The system of claim 21 wherein the usage criteria specified in the expiration policy is a length of time, and the usage data meets the usage criteria if a length of time since the last use of the software component is greater than the length of time in the usage criteria.

29. The system of claim 21 wherein the usage criteria specified in the expiration policy is a number, and the usage data meets usage criteria if a number of times the software component has been accessed is less than the number in the usage criteria.

30. The system of claim 21 wherein access to the removed software component is provided through a remotely run web service.