Systems and methods for generating data visualization applications

• US 10,275,221 B2
• Filed: 02/24/2016
• Issued: 04/30/2019
• Est. Priority Date: 03/06/2015
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Thattai, Balaji T., Shanmugam, Karthikeyan, Yao, Chi, Lau, Yee Lang
• Primary Examiner(s): Aponte, Francisco J
• Application Number:
  US15/052,449
• Publication Number:
  US 20160259626A1
• Time in Patent Office: 1,161 Days
• Field of Search: 717101-113
• CPC Class Codes: G06F 16/212 with details for data modelling support
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management

Abstract

A system provides a high-level visual programming language input through a GUI. User inputs specify a data source, a workflow, processing logic, and a data store. Multiple instances of these primitives may be combined to generate multi-dimensional domain applications. The workflow and processing logic may be specified in a graphical user interface wherein nodes representing workflow actions or processing functions are picked from a palette and placed on a diagram. Interconnections between nodes are received in the interface and represent data flows or dependencies between nodes. The high-level visual programming inputs are the translated into low-level database commands and executed within an execution framework.

Claims

1. A method for generating data applications, the method comprising:

receiving, by a server system through a graphical user interface, an input data model defining an input data type and an input data structure and an output data model defining an output data type and an output data structure, wherein the input data model is constructed by executing data processing workflows that are automatically generated from a specification of a multi-dimensional model;

receiving, by the server system through the graphical user interface, a workflow, the workflow describing coordination of concurrent data processing work with respect to job dependency and precedence;

receiving, by the server system through the graphical user interface, data processing logic, the data processing logic specifying a transformation of one or more input data sets into one or more output data sets to be performed during execution of the workflow, wherein the one or more input data sets are formatted according to the input data model and the one or more output data sets are formatted according to the output data model, and wherein the input data model is different than the output data model;

receiving, by the server system through the graphical user interface, a specification of a data source to input to the workflow, wherein receiving the specification of the data source comprises receiving, in the graphical user interface, a selection of the data source and at least one property from a graphical representation of a data source repository;

receiving, by the server system through the graphical user interface, a specification of a data store to store an output of the workflow, wherein the data store defines the output data model describing data elements stored in the data store;

generating a domain application to provide an execution framework for the workflow;

executing, by the server system, the domain application;

receiving, by the data store, a query;

obtaining, by the data store, a result of the query;

transforming, by the data store, the result of the query into a transformed result having a different data model than the output data model; and

returning, by the data store, the transformed result.

2. The method of claim 1, wherein the data store is universally addressable, wherein the data store is configured to receive queries including property arguments, and wherein the data store is configured to receive assignment of input data or to be loaded with the input data.

3. The method of claim 1, further comprising:

managing, by the server system, the creating of one or more additional data models, one or more additional workflows, and one or more additional data flows.

4. The method of claim 3, where creating the one or more additional data models, the one or more additional workflows, and the one or more additional data flows comprises including in at least one of the one or more additional data models, the one or more additional workflows, the one or more additional data flows, references to the output data model, the workflow, and the data store.

5. The method of claim 4, further comprising:

combining the one or more additional data models, the one or more additional workflows, and the one or more additional data flows with the output data model, the workflow, and the data store;

wherein generating comprises generating one or more multi-dimensional domain applications.

6. The method of claim 5, wherein executing the domain application comprises executing the workflow within the execution framework, the execution framework comprising a plurality of service engines, the service engines comprising:

a raw data repository, the data source referencing the raw data repository;

a workflow engine configured to execute the workflow;

a data engine configured to execute the data processing logic;

a data store manager configured to manage storage of data within the data store; and

a data consumption service configured to retrieve data from the raw data repository for consumption by the workflow engine.

7. The method of claim 5, wherein executing includes executing multiple multi-dimensional domain applications simultaneously by the execution framework.

8. The method of claim 1, wherein receiving, by the server system, the specification of the data source comprises receiving, in the graphical user interface, a selection of the data source and at least one property from a graphical representation of a data source repository.

9. The method of claim 8, wherein receiving the data model comprises receiving, by the server system through the graphical user interface, a description of the data model with respect to a data hierarchy and one or more primitive data types.

10. The method of claim 9, wherein receiving the workflow comprises receiving, by the server system through the graphical user interface, placement of nodes and linking of nodes, wherein each node represents a sequence of commands and each link represents an execution dependency between nodes connected by the link.

11. The method of claim 10, wherein receiving the specification of the data store comprises receiving, by the server system through the graphical user interface, selection of a data destination.

12. The method of claim 11, wherein receiving the data processing logic comprises receiving, by the server system through the graphical user interface, placement of graphical elements, each graphical element representing a primitive logic function from a library of transformation commands.

13. The method of claim 12, wherein receiving the data processing logic further comprises receiving run-time scripts through the graphical user interface.

14. The method of claim 13, wherein receiving the output data model further comprises receiving definitions of derived attributes representing aggregated data values from raw data.

15. The method of claim 14, wherein receiving the output data model further comprises defining named filtering logic and applying the named filtering logic to a dimension of the plurality of dimensions according to a query criteria.

16. The method of claim 15, further comprising:

receiving a custom data representation mapped to a query pattern; and

aggregating data in the data store according to the custom data representation prior to receiving a query according to the query pattern.

17. An apparatus comprising:

a communication interface configured to enable network communications;

at least one processor coupled to the communication interface, wherein the at least one processor is configured to;

receive, through a graphical user interface, an input data model defining an input data type and an input data structure and an output data model defining an output data type and an output data structure, wherein the input data model is constructed by executing data processing workflows that are automatically generated from a specification of a multi-dimensional model;

receive, through the graphical user interface, a workflow, the workflow describing coordination of concurrent data processing work with respect to job dependency and precedence;

receive, through the graphical user interface, the data processing logic specifying transformation of one or more input data sets into one or more output data sets to be performed during execution of the workflow, wherein the one or more input data sets are formatted according to the input data model and the one or more output data sets are formatted according to the output data model, and wherein the input data model is different than the output data model;

receive, through the graphical user interface, a specification of a data source to input to the workflow, wherein receiving, by the server system, the specification of the data source comprises receiving, in the graphical user interface, a selection of the data source and at least one property from a graphical representation of a data source repository;

receive, through the graphical user interface, a specification of a data store to store an output of the workflow, wherein the data store defines the output data model describing data elements stored in the data store;

generate a domain application to provide an execution framework for the workflow;

execute the domain application;

receive, by the data store, a query;

obtain, by the data store, a result of the query;

transform, by the data store, the result of the query into a transformed result having a different data model than the output data model; and

return, by the data store, the transformed result.

18. The apparatus of claim 17, wherein the data store is universally addressable, wherein the data store is configured to receive queries including property arguments, and wherein the data store is configured to receive assignment of input data or to be loaded with the input data.

19. The apparatus of claim 17, wherein the at least one processor is configured to:

create one or more additional data models, one or more additional workflows, and one or more additional data flows.

20. The apparatus of claim 19, wherein the at least one processor is configured to create the one or more additional data models, the one or more additional workflows, and the one or more additional data flows by including in at least one of the one or more additional data models, the one or more additional workflows, the one or more additional data flows, references to the output data model, the workflow, and the data store.

21. The apparatus of claim 20, wherein the at least one processor is configured to:

combine the one or more additional data models, the one or more additional workflows, and the one or more additional data flows with the output data model, the workflow, and the data store; and

generate one or more multi-dimensional domain applications.

22. The apparatus of claim 20, wherein the at least one processor is configured to execute multiple multi-dimensional domain application simultaneously by the execution framework.