# US 8,280,919 B2 · Systems and methods for validating design meta-data

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

- Number: US 8,280,919 B2
- Document ID: US8280919B2
- Status: Granted
- Kind: B2
- Application number: 12/727,102
- Filed: 2010-03-18
- Published: 2010-07-08
- Granted: 2012-10-02
- Earliest claimed: 2003-12-08
- Assignees: Oracle International Corporation
- Inventors: Janaki Krishnaswamy; Christoph Bussler
- Web page: https://patentgrep.com/patent/US8280919B2

## 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 metadata validation process that allows for deferring object model validation until after the objects are created. The process also allows for multi-threaded processing of the validation rules, thus increasing overall performance. Validation is performed by enforcing a series of validation rules on an appropriate subject. Rules are specified according to the subject that they are validating (i.e., attribute level, association level, object level or collection level). The metadata driven validation process implements several validation types on different validation units. Correctness validation rule types ensure that a validation unit satisfies all semantic rules defined for it. Completeness validation rule types ensure that a validation unit contains all the necessary data and is ready for further use. At design time, only correctness type validation is performed. Thus, the present invention advantageously allows for incomplete objects to be created at design time. The developer, however, in this case may opt to perform completeness validation at any time. In general, a developer may opt to perform completeness and/or correctness validation at any time independent of deployment processing. In another aspect, full validation (e.g., completeness and correctness) is automatically performed on the objects during the process of creating a configuration prior to deployment.

## Claims

### Claim 1

A method for designing and validating object models, the method comprising:
receiving, at one or more computer systems, first metadata defining a model class;
receiving, at the one or more computer systems, second metadata defining a MetaClass object used to represent the model class;
receiving, at the one or more computer systems, information defining the MetaClass object as the subject of one or more validation rules;
generating, with one or more processors associated with the one or more computer systems, an instance of the MetaClass object; and
applying, with the one or more processors associated with the one or more computer systems, one or more validation rules to the instance of the MetaClass object;
wherein applying the one or more validation rules to the instance of the MetaClass object comprises:
confirming automatically that semantics of the instance of the MetaClass object complies with the information defining the MetaClass object according to one or more correctness validation rules in the one or more validation rules upon instantiation of the instance of the MetaClass object in a design environment;
confirming that data associated with the instance of the MetaClass object complies with the information defining the MetaClass object according to one or more completeness validation rules in the one or more validation rules in response to user input provided by a user interacting with the design environment; and
applying both the one or more correctness validation rules and the one or more completeness validation rules to the instance of the MetaClass object in response to deployment of a set of objects that includes the MetaClass object.

### Claim 2 (depends on 1)

The method of claim 1, wherein applying the one or more validation rules to the instance of the MetaClass object comprises applying at least one validation rule in the one or more validation rules to the instance of the MetaClass object associated by an association as a MetaAssociationEnd.

### Claim 3 (depends on 1)

The method of claim 1, wherein applying the one or more validation rules to the instance of the MetaClass object comprises applying at least one validation rule in the one or more validation rules to a MetaAssocation having the instance of the MetaClass object as a MetaAssocationEnd.

### Claim 4 (depends on 1)

The method of claim 1, wherein applying the one or more validation rules to the instance of the MetaClass object comprises applying at least one validation rule in the one or more validation rules to an instance of a MetaAttribute object associated with the MetaClass object.

### Claim 5 (depends on 1)

The method of claim 1, wherein applying the one or more validation rules to the instance of the MetaClass object comprises applying at least one validation rule in the one or more validation rules to a MetaCollection including the MetaClass object.

### Claim 6 (depends on 1)

The method of claim 1 further comprising applying, with the one or more processors associated with the one or more computer systems, the one or more correctness validation rules to the instance of the MetaClass object when the MetaClass object or an object associated therewith is automatically updated or manually updated.

### Claim 7

A non-transitory computer-readable medium storing code executable by one or more processors of one or more computer systems for designing and validating object models, the non-transitory computer-readable medium comprising:
code for receiving first metadata defining a model class;
code for receiving second metadata defining a MetaClass object used to represent the model class;
code for receiving information defining the MetaClass object as the subject of one or more validation rules;
code for generating an instance of the MetaClass object; and
code for applying one or more validation rules to the instance of the MetaClass object;
wherein the code for applying the one or more validation rules to the instance of the MetaClass object comprises:
code for confirming automatically that semantics of the instance of the MetaClass object complies with the information defining the MetaClass object according to one or more correctness validation rules in the one or more validation rules upon instantiation of the instance of the MetaClass object in a design environment;
code for confirming that data associated with the instance of the MetaClass object complies with the information defining the MetaClass object according to one or more completeness validation rules in the one or more validation rules in response to user input provided by a user interacting with the design environment; and
code for applying both the one or more correctness validation rules and the one or more completeness validation rules to the instance of the MetaClass object in response to deployment of a set of objects that includes the MetaClass object.

### Claim 8 (depends on 7)

The non-transitory computer-readable medium of claim 7, wherein the code for applying the one or more validation rules to the instance of the MetaClass object comprises code for applying at least one validation rule in the one or more validation rules to the instance of the MetaClass object associated by an association as a MetaAssociationEnd.

### Claim 9 (depends on 7)

The non-transitory computer-readable medium of claim 7, wherein the code for applying the one or more validation rules to the instance of the MetaClass object comprises code for applying at least one validation rule in the one or more validation rules to a MetaAssocation having the instance of the MetaClass object as a MetaAssocationEnd.

### Claim 10 (depends on 7)

The non-transitory computer-readable medium of claim 7, wherein the code for applying the one or more validation rules to the instance of the MetaClass object comprises code for applying at least one validation rule in the one or more validation rules to an instance of a MetaAttribute object associated with the MetaClass object.

### Claim 11 (depends on 7)

The non-transitory computer-readable medium of claim 7, wherein the code for applying the one or more validation rules to the instance of the MetaClass object comprises code for applying at least one validation rule in the one or more validation rules to a MetaCollection including the MetaClass object.

### Claim 12 (depends on 7)

The non-transitory computer-readable medium of claim 7 further comprising code for applying the one or more correctness validation rules to the instance of the MetaClass object when the MetaClass object or an object associated therewith is automatically updated or manually updated.

### Claim 13

A system for designing and validating object models, the system comprising:
a processor; and
a memory in communication with the processor and configured to store a set of instructions executable by the processor to:
receive first metadata defining a model class;
receive second metadata defining a MetaClass object used to represent the model class;
receive information defining the MetaClass object as the subject of one or more validation rules;
generate an instance of the MetaClass object; and
apply one or more validation rules to the instance of the MetaClass object;
wherein to apply the one or more validation rules to the instance of the MetaClass object the set of instructions are executable by the processor to:
confirm automatically that semantics of the instance of the MetaClass object complies with the information defining the MetaClass object according to one or more correctness validation rules in the one or more validation rules upon instantiation of the instance of the MetaClass object in a design environment;
confirm that data associated with the instance of the MetaClass object complies with the information defining the MetaClass object according to one or more completeness validation rules in the one or more validation rules in response to user input provided by a user interacting with the design environment; and
apply both the one or more correctness validation rules and the one or more completeness validation rules to the instance of the MetaClass object in response to deployment of a set of objects that includes the MetaClass object.

### Claim 14 (depends on 13)

The system of claim 13, wherein to apply the one or more validation rules to the instance of the MetaClass object the set of instructions are executable by the processor to apply at least one validation rule in the one or more validation rules to the instance of the MetaClass object associated by an association as a MetaAssociationEnd.

### Claim 15 (depends on 13)

The system of claim 13, wherein to apply the one or more validation rules to the instance of the MetaClass object the set of instructions are executable by the processor to apply at least one validation rule in the one or more validation rules to a MetaAssocation having the instance of the MetaClass object as a MetaAssocationEnd.

### Claim 16 (depends on 13)

The system of claim 13, wherein to apply the one or more validation rules to the instance of the MetaClass object the set of instructions are executable by the processor to apply at least one validation rule in the one or more validation rules to an instance of a MetaAttribute object associated with the MetaClass object.

### Claim 17 (depends on 13)

The system of claim 13, wherein to apply the one or more validation rules to the instance of the MetaClass object the set of instructions are executable by the processor to apply at least one validation rule in the one or more validation rules to a MetaCollection including the MetaClass object.

### Claim 18 (depends on 13)

The system of claim 13 wherein the set of instructions are executable by the processor to apply the one or more correctness validation rules to the instance of the MetaClass object when the MetaClass object or an object associated therewith is automatically updated or manually updated.
