System and Method for Managing and Using Data Model

• US 20160004729A1
• Filed: 09/14/2015
• Published: 01/07/2016
• Est. Priority Date: 09/13/2014
• Status: Abandoned Application

• Current Assignee: Jumbo SA
• Original Assignee: Jumbo SA
• Inventors: Evans, Aaron
• Application Number:
  US14/853,288
• Publication Number:
  US 20160004729A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/212 with details for data modelling support

Abstract

Disclosed is a system and method for defining data structures for client-server system. In one embodiment, the present invention provides a compiler-enforced data model across distributed systems for providing system stability and the ability to identify and fix violations of the data model contract in a more efficient manner.

Claims

1. A system for enforcing a data model for a distributed application in a software development, comprising:

at least one client network device operating a client application;

said client application having a first data model, a view, a controller, and a first data binding module;

at least one server network device operating a server application;

said server application having a second data model, a first application programming interface (API), a controller, and a second data binding module;

a master schema describing a third data model, a third data binding module, a data structure, a second API, an API introspection facility, and a data object;

said client application, said server application, and said master schema in communication over a network;

a source, code for each of said first data binding module, said second data binding module, said first data model, said second data model, said first API, and said view;

at least one of a schema generator configured to consume said master schema and create as one new schema; and

a source code generator configured to consume at least one of said at least one new schema and said master schema and to generate said source code, wherein said source code is in compliance with said third data model.

2. The system of claim 1, further comprising a schema enforcer that is configured to consume said at least one new schema, said master schema, and said source code and to ensure said source code is in compliance with said data third model.

3. The system of claim 1, wherein said master schema comprises annotations, further wherein said source code generator uses said annotations to identify relevant portions of said master schema to generate or modify said source code.

4. The system of claim 2, wherein said schema enforcer comprises at least one source code compiler, a database binding framework, a data marshaller, and an interpreter.

5. The system of claim 1, wherein said at least one new schema comprises a fourth data binding module, a third API, a second data object, a transport, and a second view.

6. The system of claim 1, further comprising a data storage in communication with said client application, wherein said data storage saves changes to data locally on said client application in said data storage, thereby allowing said client application to transmit said changes to said server application.

7. The system of claim 1, further comprising a data storage in communication with said server application.

8. A system for enforcing a data model for a distributed application in a software development, comprising:

at least one client network device operating a client application;

said client application comprising a first data binding module, a first data model, a view,

at least one server network device operating a server application, wherein said server application comprises a plurality of enterprise applications;

said server application comprising a second data binding module, a second data model, and an API;

said client application in communication with said plurality of enterprise applications via said server application over a network, wherein said at least one network device interacts with said plurality of enterprise applications in a type-safe manner;

a master schema describing a unified data model, said unified data model derived from individual data models of said plurality of enterprise applications; and

a source code for each of said first data binding module, said second data binding module, said first data model, said second data model, said API, and said view, wherein said source code reflects said unified data model.

9. The system of claim 8, further comprising a schema enforcer that is configured to consume said source code and to ensure said source code is in compliance with said unified data model.

10. The system of claim 8, wherein said master schema comprises annotations, further wherein said source code generator uses said annotations to identify relevant portions of said master schema to generate or modify said source code.

11. The system of claim 9, wherein said schema enforcer comprises at least one source code compiler, a database binding framework, a data marshaller, and an interpreter.

12. The system of claim 8, further comprising a data storage in communication with said client application, wherein said data storage saves changes to data locally on said client application in said data storage, thereby allowing said client application to transmit said changes to said server application.

13. The system of claim 8, further comprising a data storage in communication with said server application.

14. A non-transitory computer storage medium, comprising executable instruction, which when executed by a computer, cause said computer to:

create a master schema, wherein said master schema describes a data model, a data binding module, a data structure, an API, an API introspection facility, and a data object;

establish a network connection among a first distributed application, a second distributed application, and said master schema;

make changes to said master schema to generate an updated master schema and/or generate a new schema via a schema generator; and

read said master schema, said updated master schema, and said new schema and generate a source code via a source code generator, wherein said source code is consistent with said master schema, said updated master schema, said new schema, and said data model.

15. The non-transitory computer storage medium of claim 14, further comprising instructions for providing said updated master schema and/or said new schema to a schema enforcer.

16. The non-transitory computer storage medium of claim 15, further comprising instructions for compiling said updated master schema and/or said new schema via annotations relevant to said schema enforcer.

17. The non-transitory computer storage medium of claim 16, further comprising instructions for modifying a source code to generate an updated source code;

and

ensuring that said updated source code is compliant with said updated master schema and/or said new schema.

18. The non-transitory computer storage medium of claim 14, further comprising instructions for saving changes to data locally on said first distributed application in a data storage;

and

transmitting said changes to said second distributed application.

19. The non-transitory computer storage medium of claim 14, further comprising instructions for establishing said network connection between said first distributed application and a plurality of enterprise applications via said second distributed application.