Dependency resolution system and method for an integrated computing system
US-2018314531-A1 · Nov 1, 2018 · US
US9817677B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9817677-B2 |
| Application number | US-201113092790-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 22, 2011 |
| Priority date | Apr 22, 2011 |
| Publication date | Nov 14, 2017 |
| Grant date | Nov 14, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The technology provides for rule based data driven validation in which a rule engine identifies which rules are applicable to target data items of a target data object by their data types including any inherited data types. Additionally, a condition for a rule or a rule exemption is implemented also as a rule which is processed by the rule engine like any other rule. In one embodiment, a validation system includes an abstract rule store of rule instance data items which link to corresponding concrete rules which may be in different data formats. A corresponding rule provides access to rule logic which implements the corresponding rule. A rule engine and the abstract rule store may be accessed over a network by an application requesting validation of a target data object. Furthermore, in some examples, the data driven rule store can be implemented using the Microsoft .NET™ framework.
Opening claim text (preview).
What is claimed is: 1. A computer implemented method for rule based data driven validation comprising: receiving over a communication network a target data object in a validation request from an executing software application; identifying one or more target data member items of the target data object based on stored data type definitions; identifying a data type and any inherited data type for the one or more target data member items; identifying one or more rules applicable to each target data item based on a target data identifier associated with each applicable rule having a same data type or an inherited data type of the target data item by a rule engine identifying one or more rule instance data items based on the one or more target data items, at least one rule instance data item comprises a condition which is implemented as another rule instance data item accessible by the rule engine like any other rule instance data items, and the rule engine identifying one or more rules linked to the identified one or more rule instance data items as the one or more applicable rules; in response to determining, via rule execution criteria, the condition of the at least one rule instance data item has been satisfied, as determined by a result of separately executing the another rule instance data item using rule logic decoupled from the software application to determine whether the at least one rule instance data item is to be executed, executing the identified one or more applicable rules after determining that the condition has been satisfied; returning a validation result data object to the software application, wherein the target data object identifies each target data member item by a class identifier and a property identifier; and identifying a data type and any inherited data type for the one or more target data item members comprises determining data types and class membership based on identifying matches with the class identifier and the property identifier for each target data member item and the data type and any inherited data type. 2. The computer implemented method of claim 1 wherein the target data member item is defined to be of a class data type; and the inherited data type of the target data member item includes any base class of the class data type. 3. The computer implemented method of claim 1 wherein the target data identifier associated with each applicable rule is the target data identifier in a rule instance data item which links to the respective applicable rule by at least the target data identifier. 4. The computer implemented method of claim 1 wherein the rule execution criteria includes determining whether to skip execution of the applicable rule based on the result from executing the another rule identified as the condition. 5. The computer implemented method of claim 1 wherein the rule execution criteria includes determining whether to alter execution of the applicable rule based on the result from executing the another rule identified as the condition. 6. The computer implemented method of claim 1 wherein executing the identified one or more applicable rules subject to rule execution criteria further comprises locating virtual machine instructions for execution of the one or more applicable rules in one or more files based on a rule identifier associated with each rule. 7. A data driven validation system comprising: one or more processors; a memory; an abstract rule store stored in the memory linking one or more rule instance data items to one or more corresponding rules stored in a concrete rule store, each rule instance data item comprising a target data identifier identifying a data type of a target data item processed by its respective linked one or more corresponding rules, and at least one rule instance data item comprises a condition which is implemented as another rule instance data item and an exemption data item, prior to executing a corresponding rule for which the condition has been satisfied, accessible by the rule engine like any other rule instance data item and is attached to the one or more rule instance data items, wherein the another rule is independently executed to determine whether the at least one rule instance data item is to be executed; a validation software interface executing on the one or more processors for receiving a validation request comprising a target data object from an executing application, the target data object including one or more target data items of the object to be validated; a rule engine executing on the one or more processors for accessing the one or more rule instance data items communicatively coupled to the validation software interface to receive the validation request; the rule engine identifies one or more rule instance data items based on the target data identifier which are applicable to the one or more target data items; the rule engine executes rule logic, which is decoupled from a client device executing the application requesting the validation, and processing the one or more rule instance data items of the corresponding one or more rules linked to the identified one or more rule instance data items, without having to update the application wherein the target data object identifies each target data member item by a class identifier and a property identifier; and identifying a data type and any inherited data type for the one or more target data item members comprises determining data types and class membership based on identifying matches with the class identifier and the property identifier for each target data member item and the data type and any inherited data type. 8. The system of claim 7 , wherein the rule engine aggregates a validation result value for each rule applied to each target data item of the target data object in a validation result object for the target data object; based on the validation result values, the rule engine sets an overall validation status for the validation request; and the validation software interface sends the validation result object to the executing software application. 9. The system of claim 7 , further comprising a plurality of concrete rule stores storing rules in a plurality of concrete data formats in the memory. 10. The system of claim 9 , wherein the plurality of concrete data formats comprises at least one of the following: extensible markup language (XML); and structured query language (SQL). 11. The system of claim 7 , wherein the rule engine executes the rule logic corresponding to the condition implemented as another rule instance for determining whether an exemption action with respect to the corresponding rule is to be applied. 12. The system of claim 7 wherein each rule instance data item of the abstract rule store comprises a target data identifier including a class identifier and a property identifier; the rule engine further comprises a rule validator which receives the target data object and each target data item of the object is identifiable by a class identifier and a property identifier; and the rule validator searches class and property identifiers of rule instance data items for a match. 13. The system of claim 12 further comprising one or more files including virtual machine instructions for executing rule logic and meta data; and the rule validator searches the meta data for identifying the rule logic of the corresponding rule. 14. The system of claim 7 , wherein the exemption action comprises overriding at least one parameter value of the corresponding rule and executing the corresponding rule using the overridden parameter value.
Physics · mapped topic
Inheritance · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.