APPLICATION COHERENCY MANAGER

• US 20090182786A1
• Filed: 11/03/2008
• Published: 07/16/2009
• Est. Priority Date: 11/01/2007
• Status: Abandoned Application

• Current Assignee: Cybernet Systems Corporation
• Original Assignee: Cybernet Systems Corporation
• Inventors: Stokes, Devvan, Haanpaa, Douglas, Jacobus, Charles J., Beach, Glenn J.
• Application Number:
  US12/263,706
• Publication Number:
  US 20090182786A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1767 Concurrency control, e.g. optimistic or pessimistic approaches
• CPC Class Codes: G06F 16/248 Presentation of query results
• CPC Class Codes: G06F 16/50 of still image data
• CPC Class Codes: G06F 16/53 Querying
• CPC Class Codes: G06F 16/90335 Query processing
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9538 Presentation of query results

Abstract

An application coherency manager (ACM) implements and manages the interdependencies of simulation, data, and platform information to simplify the task of organizing and executing large simulations composed of numerous models and data files. One or more file systems or repositories stories raw data in the form of files, data, or models, and a graphical users interface (GUI) enabling a user to enter and receive results from a query involving the files, data, or models. One or more coherency checking modules (CCMs) are operative to determine the types and versions of, and compatibility between, the files, data, or models. A database stores processed information about the file systems or repositories and the results of previous queries, and a data aggregator and manager (DAM) that manages the flow of information between the file system or repository, the GUI, the CCMs, and the database. The invention is applicable to simulation and non-simulation type applications such as document control, source code control, image libraries, etc.

Claims

1. An application coherency manager (ACM), comprising:

one or more file systems or repositories storing raw data in the form of files, data, or models;

a graphical users interface (GUI) enabling a user to enter and receive results from a query involving the files, data, or models;

one or more coherency checking modules (CCMs) operative to determine the types and versions of, and compatibility between, the files, data, or models;

a database for storing processed information about the file systems or repositories and the results of previous queries; and

a data aggregator and manager (DAM) that manages the flow of information between the file system or repository, the GUI, the CCMs, and the database.

2. The ACM of claim 1, including multiple, distributed file systems or repositories storing raw data in the form of files, data, or models.

3. The ACM of claim 1, including multiple DAMs that cooperate to handle a very large set of files.

4. The ACM of claim 1, wherein the DAM is operative to store information regarding user-defined relationships between files, data, or models.

5. The ACM of claim 1, wherein additional CCMs may be added to the ACM without recompiling or removing other system functionality.

6. The ACM of claim 1, wherein the DAM can automatically receive and process the output of additional new CCMs.

7. The ACM of claim 1, wherein the GUI is operative to dynamically configure itself to optimize feedback to a user.

8. The ACM of claim 1, wherein new CCMs may be added or modified to identify specific types or versions of files.

9. The ACM of claim 1, wherein the file systems or repositories contain simulation information.

10. The ACM of claim 1, wherein the file systems or repositories contain source code.

11. The ACM of claim 1, wherein the file systems or repositories contain documents.

12. The ACM of claim 1, wherein the file systems or repositories contain image libraries.

13. A method of managing information, comprising the steps of:

storing raw data in one or more file systems or repositories in the form of files, data, or models;

crawling over the raw data to identify the type, nature, version, or other coherency information about the files, data, or models; and

storing the coherency information in a database for more efficient, later retrieval by a user.