SYSTEMS AND METHODS FOR GENERATING SETS OF MODEL OBJECTS HAVING DATA MESSAGING PIPES

• US 20110055850A1
• Filed: 08/31/2009
• Published: 03/03/2011
• Est. Priority Date: 08/31/2009
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: WILLIAMSON, Eric
• Granted Patent: US 8,365,195 B2
• Time in Patent Office: Days
• US Class Current: 719/316
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

Embodiments relate to generating sets of model objects having data messaging pipes. A modeling client can host modeling logic and an application programming interface (API) to create, access, manipulate, and import/export modeling objects used in modeling applications, such as engineering, medical, financial, and other modeling platforms. The source data accepted into the modeling client can include consumer or business-level applications, whose spreadsheet, database or other content can be extracted and encapsulated in object-oriented format, such as extensible markup language (XML) format. A set of modeling objects can be connected via data messaging pipes on a selective basis, so that individual objects can transmit or receive data outputs generated by other objects. The model objects can share, exchange, or combine computational outputs, internal data, and other information from other model object(s). Multiple pipes can be established at various levels or dimensions between objects or groups of objects.

Claims

1. A method of generating a set of linked model objects, comprising:

accessing a set of source data;

generating a set of model objects from the set of source data, each model object in the set of model objects being based on at least one extracted data element and at least one attribute of the extracted data element;

selecting at least two model objects in the set of model objects to link via at least one data messaging pipe; and

establishing at least one data messaging pipe between the at least two selected model objects to generate the set of linked model objects.

2. The method of claim 1, wherein the at least one data messaging pipe comprises at least one of a socket connection, an inter-process communication (IPC) socket, a port connection, and a Transfer Control Protocol/Internet Protocol (TCP/IP) connection.

3. The method of claim 1, wherein the at least one data messaging pipe communicates data output from a first of the at least two model objects to a second of the at least two model objects.

4. The method of claim 1, wherein the at least two model objects comprises at least three model objects, and the at least one data messaging pipe comprises a plurality of data messaging pipes.

5. The method of claim 1, wherein the at least two model objects each comprise at least one model object encoded in extensible markup language (XML) format.

6. The method of claim 1, wherein the at least two model objects are exportable to at least one of a mainframe modeling platform, a database, and a modeling client.

7. The method of claim 1, wherein the set of source data comprises at least one of spreadsheet data, database data, word processing data, or presentation data.

8. A client system, comprising:

an interface to a set of source data; and

a processor, communicating with the set of source data via the interface, the processor being configured to—

generate a set of model objects from the set of source data, each model object in the set of model objects being based on at least one extracted data element and at least one attribute of the extracted data element,

select at least two model objects in the set of model objects to link via at least one data messaging pipe, and

establish at least one data messaging pipe between the at least two selected model objects to generate the set of linked model objects.

9. The system of claim 8, wherein the at least one data messaging pipe comprises at least one of a socket connection, an inter-process communication (IPC) socket, a port connection, and a Transfer Control Protocol/Internet Protocol (TCP/IP) connection.

10. The system of claim 8, wherein the at least one data messaging pipe communicates data output from a first of the at least two model objects to a second of the at least two model objects.

11. The system of claim 8, wherein the at least two model objects comprises at least three model objects, and the at least one data messaging pipe comprises a plurality of data messaging pipes.

12. The system of claim 8, wherein the at least two model objects each comprise at least one model object encoded in extensible markup language (XML) format.

13. The system of claim 8, wherein the at least two model objects are exportable to at least one of a mainframe modeling platform, a database, and a modeling client.

14. The system of claim 8, wherein the set of source data comprises at least one of spreadsheet data, database data, word processing data, or presentation data.

15. A set of linked model objects stored in a computer readable medium, comprising:

an interface to a set of model objects extracted from a set of source data, each model object in the set of model objects being based on at least one extracted data element and at least one attribute of the extracted data element; and

at least two selected model objects selected from the set of model objects; and

at least one data messaging pipe connected between the at least two selected model objects.

16. The set of linked model objects of claim 15, wherein the at least one data messaging pipe comprises at least one of a socket connection, an inter-process communication (IPC) socket, a port connection, and a Transfer Control Protocol/Internet Protocol (TCP/IP) connection.

17. The set of linked model objects of claim 15, wherein the at least one data messaging pipe communicates data output from a first of the at least two model objects to a second of the at least two model objects.

18. The set of linked model objects of claim 15, wherein the at least two model objects comprises at least three model objects, and the at least one data messaging pipe comprises a plurality of data messaging pipes.

19. The set of linked model objects of claim 15, wherein the at least two model objects each comprise at least one model object encoded in extensible markup language (XML) format.

20. The set of linked model objects of claim 15, wherein the at least two model objects are exportable to at least one of a mainframe modeling platform, a database, and a modeling client.