Safety-Critical Data Checking In Object-Oriented Systems

• US 20100094816A1
• Filed: 09/09/2008
• Published: 04/15/2010
• Est. Priority Date: 09/09/2008
• Status: Abandoned Application

• Current Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Original Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Inventors: Allshouse, Richard A., Lamana, Michael, Groves, Robert B. JR.
• Application Number:
  US12/207,246
• Publication Number:
  US 20100094816A1
• Time in Patent Office: Days
• US Class Current: 707/697
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

Methods for detecting the corruption of vital data during the execution of object-oriented programs are disclosed. In accordance with the illustrative embodiments, code is generated at run-time for computing a checksum of vital data in an object, and the code is inserted into the object. When the object is created, this code is executed to compute an initial checksum, and subsequently the code re-computes the checksum during program execution so that a change in the checksum—and inferentially, a change in one or more vital data—can be detected. The checksum is subsequently re-computed during program execution—either periodically, or in response to events such as when the object is modified or when a method of the object is invoked.

Claims

1. A method comprising:

generating, at run-time, a software object that comprises one or more safety-critical data;

generating, at run-time, code for detecting a change in a value of said safety-critical data; and

inserting, at run-time, said code into said software object.

2. The method of claim 1 wherein said code periodically computes a checksum of said safety-critical data.

3. The method of claim 1 wherein said code computes a checksum of said safety-critical data when said software object is created.

4. The method of claim 1 wherein the instantiated code template computes a checksum of said safety-critical data whenever said software object is modified.

5. A method comprising:

generating, at run-time, a software object that comprises;

(i) one or more safety-critical data, and

(ii) a code template for detecting a change in a value of said safety-critical data; and

instantiating said code template at run-time.

6. The method of claim 5 wherein the instantiated code template computes a checksum of said safety-critical data when said software object is first accessed.

7. The method of claim 5 wherein the instantiated code template computes a checksum of said safety-critical data whenever said software object is modified.

8. The method of claim 5 wherein said software object comprises a method M, and wherein the instantiated code template computes a checksum of said safety-critical data whenever said method M is invoked.

9. A method comprising:

generating, at run-time, a collection object that;

(i) is capable of holding one or more constituent objects, wherein at least one of said constituent objects is capable of storing a respective safety-critical datum, and

(ii) comprises a code template for computing a cumulative checksum over all of the safety-critical data of said constituent objects; and

instantiating said code template at run-time.

10. The method of claim 9 wherein the instantiated code template is executed when said collection object is initially populated.

11. The method of claim 9 wherein the instantiated code template is executed when said collection object is first accessed.

12. The method of claim 9 wherein said collection object comprises a method M, and wherein the instantiated code template is executed whenever said method M is invoked.

13. The method of claim 9 wherein the instantiated code template is executed when a constituent object is removed from said collection object.

14. The method of claim 9 wherein said collection object also comprises code for updating said cumulative checksum when a new constituent object is added to said collection object.

15. An object class comprising:

one or more safety-critical data; and

a segment of memory that is populated at run-time with code for detecting a change in a value of said safety-critical data.

16. The object class of claim 15 wherein said code periodically calculates a checksum of said safety-critical data.

17. The object class of claim 16 wherein said code is a code template that is instantiated at run-time.

18. The object class of claim 15 wherein said code computes a checksum of said safety-critical data when an instance of said object class is created.

19. The object class of claim 15 wherein said code computes a checksum of said safety-critical data when an instance of said object class is first accessed.

20. The object class of claim 15 wherein said code computes a checksum of said safety-critical data whenever an instance of said object class is modified.