METHOD AND SYSTEM FOR DETECTION OF INTEGRITY CONSTRAINT VIOLATIONS

• US 20080059841A1
• Filed: 10/31/2007
• Published: 03/06/2008
• Est. Priority Date: 07/28/2003
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Burke, Michael, Shmueli, Oded, Raghavachari, Mukund, Bordawekar, Rajesh
• Granted Patent: US 8,209,301 B2
• Time in Patent Office: Days
• US Class Current: 714/38
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 16/24565 Triggers; Constraints
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

A system (and method) of detecting an error in a database interaction, includes providing information about at least one of at least first and second software systems, and a mapping between at least a portion of the at least first and second software systems, and examining the at least one of the first and second software systems and the mapping to determine an error in an interaction between the at least first and second software systems.

Claims

1. A method for detecting an error in an interaction between a plurality of software systems, comprising:

providing information about at least one of at least first and second software systems, and a mapping between at least a portion of said at least first and second software systems;

automatically generating a check based upon the information and the mapping;

inserting said check into at least one of said first and second software systems; and

examining said at least one of said first and second software systems and said mapping to determine an error in an interaction between said at least first and second software systems based upon said check.

2. The method of claim 1, wherein said information provided about at least one software system of said at least first and second software systems includes at least one of:

an XML schema of said at least one software system;

integrity constraints of said at least one software system, said integrity constraints of said at least first and second software systems being represented in a common constraint model;

a specification of said at least one software system;

a unified modeling language (UML) model of said at least one software system; and

code of said at least one software system.

3. The method of claim 1, wherein said information provided about at least one software system of said at least first and second software systems includes at least one of:

information about a sub-component of said at least one software system; and

information about less than an entirety of said at least one software system.

4. The method of claim 1, wherein one of said first and second software systems comprises at least one of a database, an application, an extensible markup language (XML) repository and an XML database,

wherein said information provided about said at least one software system of said at least first and second software systems includes at least one of schema information of said database and information about values in said database, and programming language types.

5. The method of claim 1, wherein said mapping is provided one of explicitly and inferred from said information about said at least first and second software systems.

6. The method of claim 1, wherein said error comprises one of an integrity constraint violation, a potential error representing a warning that an error may occur, and a definite error representing one of that an error will occur and that an error has occurred, wherein said error is found prior to said interaction between the at least first and second software systems.

7. The method of claim 1, wherein said error is found one of during said run time of the at least first and second software systems and prior to any of said interaction between the at least first and second software systems.

8. The method of claim 1, wherein said check is one of:

inserted at a location directed by a programmer;

performed after an interaction between said at least first and second software systems;

performed before an interaction between said at least first and second software systems; and

performed prior to an end of a transaction.

9. The method of claim 2, further comprising:

performing static analysis of said at least first and second software systems to at least one of simplify, eliminate, and approximate said check;

analyzing said integrity constraints in said common constraint model; and

based on said analyzing, if an inconsistency is detected, then outputting an error.

10. The method of claim 2, further comprising one of:

modifying said integrity constraints in said common constraint model; and

generating a check from said integrity constraints.

11. The method of claim 1, further comprising:

providing a shadow database in one of said at least first and second software systems,

said shadow database containing partial knowledge of the other of said at least first and second software systems and being used to perform a check,

wherein said partial knowledge includes at leaset one of;

partial knowledge of data values in said other of said at least first and second software systems; and

partial knowledge of non-existence of data values in said other of said at least first and second software systems.

12. The method of claim 1, further comprising:

reporting said error, wherein said reporting comprises one of;

notifying before running at least one of said at least first and second software systems;

notifying while running at least one of said at least first and second software systems;

allowing said one of said at least first and second software systems to address said error;

suggesting how said error may be addressed.

13. A method of detecting an error in a database interaction, comprising:

examining database code for database constraints;

examining application code for application-level constraints;

automatically generating a check based upon said database constraints and said application-level constraints;

inserting said check into at least one of said database code and said application code; and

analyzing a mapping between said database code and said application code, to determine an error in a database interaction, based upon said check.

14. The method of claim 13, further comprising:

generating a check in said application code for enforcing said database and application-level constraints.

15. The method of claim 13, further comprising:

forming a shadow database in said application code representing a portion of said database.

16. The method of claim 13, wherein said error comprises an integrity constraint violation.

17. The method of claim 13, further comprising:

inputting said database constraints and said application-level constraints, and said mapping into a common constraint model; and

before a program including said application and interacting with said database, is run and after said inputting, performing a static analysis to identify locations of where an error may arise.

18. The method of claim 13, further comprising:

after identifying said error and prior to running a program including said application, raising a notification.

19. The method of claim 13, wherein, at runtime of said program, when an error is detected as occurring, raising a notification.

20. A method of detecting an integrity constraint violation in a database interaction, comprising:

examining a database schema;

examining an application type;

automatically generating a check based upon said database schema and said application type;

inserting said check into one of said database schema and said application type; and

analyzing a mapping between said database schema and said application type, to determine whether an integrity constraint violation will occur in said database interaction with said application based upon said check,

wherein said database schema provides each of the integrated constraints defined in the database, and

wherein said application type includes application code including integrity constraints defined therein.

21. The method of claim 20, further comprising one of:

generating a check in said application code for enforcing said database and application-level constraints; and

forming a shadow database in application code representing a portion of said database.

22. The method of claim 20, further comprising:

inputting said database schema, said application type, and said mapping into a common constraint model;

before a program including said application and interacting with said database, is run and after said inputting, performing a static analysis to identify locations of where said integrity constraint violation may arise.

23. The method of claim 20, further comprising:

after determining said integrity constraint violation and prior to running a program including said application, raising a notification;

further comprising at least one of;

at runtime of said program, when an integrity constraint violation is determined to occur, raising a notification; and

analyzing a common constraint model receiving said database schema, application type, and mapping, to determine an inconsistency between said database schema and said application type, wherein if no said inconsistency is determined, then taking all of the common constraints and analyzing the application code with respect to the common constraints for an error in the application code, wherein if no said error is determined in the application code, then inserting a check into said application code to enforce the constraints at runtime.

24. A system of detecting an error in a database interaction, comprising:

a module for examining a database code for database constraints;

a module for examining an application code for application-level constraints;

a module for automatically generating a check based upon said database constraints and said application-level constraints;

a module for inserting said check into one of said database code and said application code; and

an analyzing unit for analyzing a mapping between said database code and said application code, to determine an error in a database interaction based upon said check.

25. A method for detecting an error in an interaction between a plurality of software systems, comprising:

providing information about at least one of at least first and second software systems, and a mapping between at least a portion of said at least first and second software systems; and

statically examining said at least one of said first and second software systems and said mapping to determine an error in an interaction between said at least first and second software systems.