Object model based mapping

• US 8,566,780 B2
• Filed: 06/26/2007
• Issued: 10/22/2013
• Est. Priority Date: 06/26/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Tolskyakov, Andrey, Shatnawi, Mohammed Fadel, Herring, Russell Allen Jr., Hua, Justin Jiajun
• Primary Examiner(s): Nahar, Qamrun
• Application Number:
  US11/768,628
• Publication Number:
  US 20090006440A1
• Time in Patent Office: 2,310 Days
• Field of Search: 717/104, 717/105
• US Class Current: 717/104
• CPC Class Codes: G06Q 30/00 Commerce

Abstract

Object model based mapping may be provided. First, backend data may be received defining data constructs in a backend system. Then entity data may be received defining data constructs in an entity model. User selectable elements may then be received defining a process associating the backend data with the entity data. Next, code may be produced, based on the received user selectable elements, configured to implement the process.

Claims

1. A method for providing object model based mapping, the method comprising:

receiving backend data defining data constructs in a backend system;

receiving entity data defining data constructs in an entity model;

receiving user selectable elements defining a process associating the backend data with the entity data, the user selectable elements being configured to define a flow chart of the process, the flow chart of the process being represented as a state-machine diagram and being convertible into code; and

producing the code, based on the received user selectable elements, configured to implement the process represented by the flow chart, wherein producing the code comprises producing code that allows data flow from the backend system to the entity model and from the entity model to the backend system based on the flow chart process as defined by the user selectable elements.

2. The method of claim 1, wherein receiving the backend data defining data constructs in the backend system comprises receiving the backend data configured to define the backend system.

3. The method of claim 1, wherein receiving the backend data defining data constructs in the backend system comprises receiving the backend data configured to define how to access the backend system.

4. The method of claim 1, wherein receiving the backend data defining data constructs in the backend system comprises receiving the backend data defining data constructs in the backend system comprising one of the following:

a conceptual model;

a relational database; and

a set of application program interfaces (APIs).

5. The method of claim 1, wherein receiving the entity data defining data constructs in the entity model comprises receiving the entity data defining data constructs comprising one of the following:

entity classes and data logical classes.

6. The method of claim 1, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the process configured to allow data flow from the backend system to the entity model and between the entity model and the backend system.

7. The method of claim 1, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the process configured to implement customer relationship management (CRM).

8. The method of claim 1, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the process configured to map to a database on the backend system.

9. The method of claim 1, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the process configured to perform at least one data type transformation.

10. The method of claim 1, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the process configured to perform at least one data type transformation comprising at least one of the following:

strings to guides;

integers to strings;

concatenation of types; and

a mathematical transformation.

11. The method of claim 1, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the flow chart of the process that defines a work flow between the backend system and the entity model.

12. The method of claim 1, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the flow chart of the process comprising at least one activity describing the process.

13. The method of claim 1, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the flow chart of the process further comprising a sequential process.

14. A system for providing object model based mapping, the system comprising:

a memory storage; and

a processing unit coupled to the memory storage, wherein the processing unit is operative to execute code configured to implement a process, the code produced based on received user selectable elements building, within a user interface, a flow chart of the process being represented as a user-made state-machine diagram associating a backend data with an entity data, the flow chart of the process being convertible into the code, the code being configured to enable the processing unit to implement the process represented by the flow chart upon execution of the code, the backend data defining data constructs in a backend system and the entity data defining data constructs in an entity model, wherein the code produced allows data flow from the backend system to the entity model and from the entity model to the backend system based on the flow chart process as defined by the user selectable elements.

15. A computer-readable storage device which stores a set of instructions which when executed performs a method for providing object model based mapping, the method executed by the set of instructions comprising:

receiving backend data defining data constructs in a backend system, the backend data configured to define the backend system and to define how to access the backend system;

receiving entity data defining data constructs in an entity model, the entity data comprising one of the following;

entity classes and data logical classes;

receiving user selectable elements defining a process associating the backend data with the entity data, the user selectable elements defining a flow chart of the process comprising at least one activity describing the process comprising a state machines process enabling bi-directional data transforms between the backend data and the entity data, the flow chart being configured to be translated to machine code for computer execution and being representative of a work flow between the backend system and the entity model; and

producing code, based on the received user selectable elements, configured to implement the process, wherein producing the code comprises producing code that enables the bi-directional data transforms by allowing data flow from the backend system to the entity model and from the entity model to the backend system based on the flow chart process as defined by the user selectable elements.

16. The computer-readable storage device of claim 15, wherein receiving the backend data defining data constructs in the backend system comprises receiving the backend data defining data constructs in the backend system comprising one of the following:

a conceptual model;

a relational database; and

a set of application program interfaces (APIs).

17. The computer-readable storage device of claim 15, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the process configured to allow data flow from the backend system to the entity model and between the entity model and the backend system.

18. The computer-readable storage device of claim 15, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the process configured to map to a database on the backend system.

19. The computer-readable storage device of claim 15, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the process configured to perform at least one data type transformation.

20. The computer-readable storage device of claim 15, wherein receiving the user selectable elements defining the process comprises receiving the user selectable elements defining the process configured to perform at least one data type transformation comprising at least one of the following:

strings to guides;

integers to strings;

concatenation of types; and

a mathematical transformation.