# US 2008/0313613 A1 · Method for statically checking an object-oriented computer program module

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0313613 A1
- Document ID: US20080313613A1
- Status: Published application
- Kind: A1
- Application number: 12/077,830
- Filed: 2008-03-21
- Published: 2008-12-18
- Earliest claimed: 2007-03-21
- Assignees: Carnegie Mellon University
- Inventors: Kevin M. Bierhoff; Jonathan Aldrich
- Web page: https://patentgrep.com/patent/US20080313613A1

## CPC

- G06F 9/44589: {Program code verification, e.g. Java bytecode verification, proof-carrying code (high-level semantic checks G06F8/43; prevention of errors by analysis, debugging or testing of software G06F11/36)}
- G06F 9/4488: {Object-oriented}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method for statically checking an object-oriented computer program module includes the step of identifying objects within a computer program module, at least one of the objects having a plurality of references thereto, possibly from multiple clients. A discipline of permissions is imposed on the objects identified within the computer program module. The permissions enable tracking, from among a discrete set of changeable states, a subset of states each object might be in. A determination is made regarding whether the imposed permissions are violated by a potential reference to any of the identified objects. The results of the determination are output to a user.

## Claims

### Claim 1

A method for statically checking an object-oriented computer program module, comprising:
identifying objects within a computer program module, at least one of said objects having a plurality of references thereto;
imposing a discipline of permissions to the objects identified within the computer program module that enables tracking, from among a discrete set of changeable states, a subset of states each object might be in;
determining whether the imposed permissions are violated by a potential reference to any of the identified objects; and
outputting the result of said determining.

### Claim 2 (depends on 1)

The method of claim 1, wherein said imposing a discipline of permissions includes imposing permissions that permit multiple independent references to an object.

### Claim 3 (depends on 1)

The method of claim 1 wherein said imposing a discipline of permissions includes imposing a permission selected from the group comprising:
a permission allowing a read-only reference to an object, where other references can read and write to the object;
a permission allowing a read/write reference to an object, where all other references to the object are read-only;
a permission allowing a read-only reference to an object, where all other references to the object are also read-only;
a permission allowing a single reference to an object; and
a permission allowing a read/write reference to an object, where other references to the object can also be read/write references.

### Claim 4 (depends on 1)

The method of claim 1, wherein said determining is based on each of said objects assuming states that change perceptibly and non-monotonically within a guaranteed state space.

### Claim 5 (depends on 4)

The method of claim 4 wherein said imposing a discipline of permissions comprises imposing permissions that can be associated with a fraction of an object.

### Claim 6 (depends on 1)

The method of claim 1 wherein said determining is based on each of said objects having a state represented by a hierarchical state machine.

### Claim 7 (depends on 1)

The method of claim 1, wherein said determining is based on said objects having a superclass state and a subclass state, and wherein said superclass state and said subclass may be different.

### Claim 8

A method for statically checking an object-oriented computer program module, comprising:
identifying objects within a computer program module;
partitioning identified objects into a plurality of dimensions each dimension assigned to a client;
each client independently tracking, from among a discrete set of changeable states, a subset of states each object might be in within that client's dimension;
imposing a discipline of permissions in which the operations that a client can invoke involving an object are limited to those operations in which the invoked operation changes the state of the object only in that client's dimension;
determining whether the imposed permissions are violated; and
outputting the result of said determining.

### Claim 9 (depends on 8)

The method of claim 8 wherein said imposing a discipline of permissions includes imposing a permission selected from the group comprising:
a permission allowing a read-only reference to an object, where other references can read and write to the object;
a permission allowing a read/write reference to an object, where all other references to the object are read-only;
a permission allowing a read-only reference to an object, where all other references to the object are also read-only;
a permission allowing a single reference to an object; and
a permission allowing a read/write reference to an object, where other references to the object can also be read/write references.

### Claim 10 (depends on 8)

The method of claim 8, wherein said determining is based on each of said objects assuming states that change perceptibly and non-monotonically within a guaranteed state space.

### Claim 11 (depends on 8)

The method of claim 8, wherein said determining is based on each of said objects having a state represented by a hierarchical state machine.

### Claim 12 (depends on 8)

The method of claim 8, wherein said determining is based on said objects having a superclass state and a subclass state, and wherein said superclass state and said subclass may be different.

### Claim 13

A method for statically checking an object-oriented computer program module, comprising:
identifying objects within a computer program module;
imposing a discipline of permissions to the objects identified within the computer program module such that for each object, only one client may have read/write permission to said object, track said object's state from among a discrete set of changeable states, and perform any legal operation on said object given said object's current state while all other clients may have read-only access to said object, and can perform only operations that do not affect said object's state and are legal given the client's knowledge of said object's current state;
determining whether the imposed permissions are violated; and
outputting the result of said determining.

### Claim 14 (depends on 13)

The method of claim 13 wherein said imposing a discipline of permissions includes imposing at least one additional discipline selected from the group comprising:
a permission allowing a single reference to an object; and
a permission allowing a read/write reference to an object, where other references to the object can also be read/write references.

### Claim 15 (depends on 13)

The method of claim 13, wherein said determining is based on each of said objects assuming states that change perceptibly and non-monotonically within a guaranteed state space.

### Claim 16 (depends on 14)

The method of claim 14, wherein said imposing a discipline of permissions comprises imposing permissions that can be associated with a fraction of an object.

### Claim 17 (depends on 13)

The method of claim 13, wherein said determining is based on each of said objects having a state represented by a hierarchical state machine.

### Claim 18 (depends on 13)

The method of claim 13, wherein said determining is based on said objects having a superclass state and a subclass state, and wherein said superclass state and said subclass may be different.

### Claim 19

A method for statically checking an object-oriented computer program module, comprising:
identifying objects within a computer program module, said objects having discrete states that change perceptibly and non-monotonically within a guaranteed state space;
imposing a discipline of permissions to the objects identified within the computer program module such that a plurality of clients can each have a permission that enables tracking a subset of states each object might be in;
determining whether the imposed permissions are violated; and
outputting the result of said determining.

### Claim 20

A method for statically checking an object-oriented computer program module, comprising:
identifying objects within a computer program module, at least one of said objects having a plurality of references thereto;
imposing a discipline of permissions to the objects identified within the computer program module that enables tracking, from among a discrete set of changeable states represented by a hierarchical state machine, a subset of states each object might be in;
determining whether the imposed permissions are violated by a potential reference to any of the identified objects; and
outputting the result of said determining.

### Claim 21

A method for statically checking an object-oriented computer program module, comprising:
identifying objects within a computer program module, at least one of said objects having a plurality of references thereto;
imposing a discipline of permissions to the objects identified within the computer program module that enables tracking, from among a discrete set of changeable states including a superclass state and a subclass state which may differ, a subset of states each object might be in;
determining whether the imposed permissions are violated by a potential reference to any of the identified objects; and
outputting the result of said determining.
