CODE-LEVEL MODULE VERIFICATION

• US 20170357494A1
• Filed: 06/08/2016
• Published: 12/14/2017
• Est. Priority Date: 06/08/2016
• Status: Active Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Owin, Kenneth J., Reed, David C., Rios, Esteban, Smith, Max D.
• Application Number:
  US15/176,300
• Publication Number:
  US 20170357494A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44552 Conflict resolution, i.e. enabling coexistence of conflicting executables

Abstract

A method for verifying that software modules have a consistent code level is disclosed. In one embodiment, such a method includes updating a software product comprising a plurality of software modules. Upon updating the software product, the method updates a code-level table that documents an expected code level for each of the software modules. When a software module is called, the method determines an actual code level of the software module and compares the actual code level with the expected code level indicated in the code-level table. If the actual code level matches the expected code level, the method allows execution of the software module. If the actual code level does not match the expected code level, the method terminates execution of the software module. A corresponding system and computer program product are also disclosed.

Claims

1. A method for verifying that software modules have a consistent code level, the method comprising:

updating a software product comprising a plurality of software modules;

creating, for the updated software product, a code-level table that documents an expected code level for each of the software modules to work together properly;

upon calling a software module of the plurality of software modules, comparing an actual code level of the software module with the expected code level indicated in the code-level table;

in the event the actual code level matches the expected code level, allowing execution of the software module; and

in the event the actual code level does not match the expected code level, terminating execution of the software module.

2. The method of claim 1, wherein calling the software module comprises initially calling the software module.

3. The method of claim 2, further comprising, in the event the actual code level matches the expected code level, marking the software module as validated.

4. The method of claim 3, further comprising, prior to any future updates to the software product but after the software module has been validated, allowing execution of the software module without comparing the actual code level to the expected code level.

5. The method of claim 3, further comprising, in the event the software module is unloaded from memory, marking the software module as unvalidated.

6. The method of claim 3, further comprising, in the event the software product is once again updated, marking the software module as unvalidated.

7. The method of claim 1, wherein comparing the actual code level comprises looking for the actual code level within the software module.

8. A computer program product to verify that software modules have a consistent code level, the computer program product comprising a computer-readable storage medium having computer-usable program code embodied therein, the computer-usable program code comprising:

computer-usable program code to update a software product comprising a plurality of software modules;

computer-usable program code to create, for the updated software product, a code-level table that documents an expected code level for each of the software modules to work together properly;

computer-usable program code to, upon calling a software module of the plurality of software modules, compare an actual code level of the software module with the expected code level indicated in the code-level table;

computer-usable program code to, in the event the actual code level matches the expected code level, allow execution of the software module; and

computer-usable program code to, in the event the actual code level does not match the expected code level, terminate execution of the software module.

9. The computer program product of claim 8, wherein calling the software module comprises initially calling the software module.

10. The computer program product of claim 9, further comprising computer-usable program code to, in the event the actual code level matches the expected code level, mark the software module as validated.

11. The computer program product of claim 10, further comprising computer-usable program code to, prior to any future updates to the software product but after the software module has been validated, allow execution of the software module without comparing the actual code level to the expected code level.

12. The computer program product of claim 10, further comprising computer-usable program code to, in the event the software module is unloaded from memory, mark the software module as unvalidated.

13. The computer program product of claim 10, further comprising computer-usable program code to, in the event the software product is once again updated, mark the software module as unvalidated.

14. The computer program product of claim 8, wherein comparing the actual code level comprises looking for the actual code level within the software module.

15. A system to verify that software modules have a consistent code level, the system comprising:

at least one processor;

at least one memory device operably coupled to the at least one processor and storing instructions for execution on the at least one processor, the instructions causing the at least one processor to;

update a software product comprising a plurality of software modules;

create, for the updated software product, a code-level table that documents an expected code level for each of the software modules to work together properly;

upon calling a software module of the plurality of software modules, compare an actual code level of the software module with the expected code level indicated in the code-level table;

in the event the actual code level matches the expected code level, allow execution of the software module; and

in the event the actual code level does not match the expected code level, terminate execution of the software module.

16. The system of claim 15, wherein calling the software module comprises initially calling the software module.

17. The system of claim 16, wherein the instructions further cause the at least one processor to, in the event the actual code level matches the expected code level, mark the software module as validated.

18. The system of claim 17, wherein the instructions further cause the at least one processor to, prior to any future updates to the software product but after the software module has been validated, allow execution of the software module without comparing the actual code level to the expected code level.

19. The system of claim 17, wherein the instructions further cause the at least one processor to, in the event the software module is unloaded from memory, mark the software module as unvalidated.

20. The system of claim 17, wherein the instructions further cause the at least one processor to, in the event the software product is once again updated, mark the software module as unvalidated.