Model framework for applications

• US 9,239,707 B2
• Filed: 06/28/2013
• Issued: 01/19/2016
• Est. Priority Date: 06/28/2013
• Status: Active Grant

• Current Assignee: Successfactors Incorporated (SAP SE)
• Original Assignee: Successfactors Incorporated (SAP SE)
• Inventors: Yu, Mei, Dunn, Angus
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): LUNA, ROBERTO E
• Application Number:
  US13/930,413
• Publication Number:
  US 20150007128A1
• Time in Patent Office: 935 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

A model framework is used to implement the model component of application using a model-view-controller design pattern. The model framework provides built-in functionality that defines a default behavior. Application programming interfaces (APIs) allow an application developer to modify the default behavior of the model framework in a manner that suits the data model of the application.

Claims

1. A computing device comprising:

a central processing unit (CPU); and

a memory having stored thereon an application that uses a model-view-controller design pattern, and which comprises a model component, a controller component, and a viewer component, the model component implemented using a model framework,

the model framework comprising one or more first application programming interfaces (APIs) that provide application specific configuration data to first program code comprising the model framework, which, when executed by the CPU, causes the model component to use the application specific configuration data,

the model framework comprising one or more second APIs to alter processing in second program code comprising the model framework, wherein the second program code, which, when executed by the CPU, causes the model component to exhibit default behavior, wherein the second program code having one or more changed properties, when executed by the CPU, causes the model component to exhibit one or more changes in the default behavior,

the model framework comprising one or more third APIs to provide create, read, update, and delete (CRUD) program code to the model framework that is specific to data objects of the application, wherein the CRUD program code, when executed by the CPU, causes the CPU to manage the data objects in a manner that is specific to the application.

2. The computing device of claim 1 wherein the model framework comprising third program code, which, when executed by the CPU, causes the CPU to respond to actions initiated by the controller component.

3. The computing device of claim 2 wherein the model framework comprising fourth program code, which, when executed by the CPU, causes the CPU to send notifications to the viewer component in response to processing some of the actions initiated by the controller component.

4. The computing device of claim 1 wherein one of the first APIs is an API that defines application specific data objects.

5. The computing device of claim 1 wherein one of the first APIs is an API that specifies one or more key fields to identify application specific data.

6. The computing device of claim 1 wherein one of the first APIs is an API that specifies one or more Internet addresses for communicating with one or more backend servers over a communication network to access data.

7. The computing device of claim 1 wherein the default behavior includes expiring data stored in the memory after a first period of time has elapsed, wherein one of the second APIs is an API to replace the first period of time with a second period of time, thereby changing when data is expired.

8. The computing device of claim 1 wherein the default behavior includes how data is stored and accessed in the memory, wherein one of the second APIs is an API to change how data is stored and accessed in the memory.

9. The computing device of claim 1 wherein the default behavior includes not sending a notification to the controller component or to the viewer component when a state of data stored in the memory has changed, wherein one of the second APIs is an API to enable sending notifications to the controller component or to the viewer component when the state of the data has changed.

10. The computing device of claim 1 wherein the default behavior includes expiring data when a location of the computing device changes, wherein one of the second APIs is an API to replace some of the second program code with replacement program code to handle the data in an application-specific manner, other than expiring the data, when the location of the computing device changes.

11. The computing device of claim 1 wherein the default behavior includes purging data stored in a cache memory of the computing device when a low memory condition arises, wherein one of the second APIs is an API to replace some of the second program code with replacement program code to handle the data in the cache memory in an application-specific manner, other than purging the data, when the low memory condition arise.

12. The computing device of claim 1 wherein the default behavior includes purging encrypted data when one or more encryption keys stored in the computing device have changed, wherein one of the second APIs is an API to replace some of the second program code with replacement program code to handle the encrypted data in an application-specific manner, other than purging, when said one or more encryption keys have changed.

13. The computing device of claim 1 wherein the computing device is a mobile computing device.

14. A computer-implemented method performed on a computing device, the method comprising:

storing in a memory of the computing device an application that uses a model-view-controller design pattern, and which comprises a model component, a controller component, and a viewer component, the model component implemented using a model framework,

the model framework comprising one or more first application programming interfaces (APIs) that provide application specific configuration data to first program code comprising the model framework, which, when executed by the computing device, causes the model component to use the application specific configuration data,

the model framework comprising one or more second APIs to alter processing in second program code comprising the model framework, wherein the second program code, which, when executed by the computing device, causes the model component to exhibit default behavior, wherein the second program code having one or more changed properties, when executed by the computing device, causes the model component to exhibit one or more changes in the default behavior,

the model framework comprising one or more third APIs to provide create, read, update, and delete (CRUD) program code to the model framework that is specific to data objects of the application, wherein the CRUD program code, when executed by the computing device, causes the computing device to manage the data objects in a manner that is specific to the application.

15. The computer-implemented method of claim 14 wherein the first APIs include APIs that:

define application specific data objects;

specify one or more key fields to identify application specific data; and

specify one or more Internet addresses for communicating with one or more backend servers over a communication network to access data.

16. The computer-implemented method of claim 15 wherein the Internet addresses include a first Internet address for retrieving data and a second Internet address for updating data.

17. The computer-implemented method of claim 14 wherein the second APIs include APIs that:

change a default behavior of expiring data after passage of a first time period to expiring data after passage of a second time period;

change the behavior of how data is stored and accessed in the computing device; and

select whether or not to send a notification to the controller component or to the viewer component when a state of data stored in the computing device has changed.

18. The computer-implemented method of claim 14 wherein the default behavior includes purging the data when conditions including a change in location of the computing device, low memory, or a change in one or more encryption keys arise, wherein the second APIs include APIs that change how the data is handled when one or more of the conditions arise.

19. A non-transitory computer readable storage medium having stored thereon computer program code that implements an application, the application using a model-view-controller design pattern and comprising a model component, a controller component, and a viewer component, the model component implemented using a model framework,

the model framework comprising one or more first application programming interfaces (APIs) that provide application specific configuration data to first program code comprising the model framework, which, when executed by a CPU, causes the model component to use the application specific configuration data,

the model framework comprising one or more second APIs to alter processing in second program code comprising the model framework, wherein the second program code, which, when executed by the CPU, causes the model component to exhibit default behavior, wherein the second program code having one or more changed properties, when executed by the CPU, causes the model component to exhibit one or more changes in the default behavior,

the model framework comprising one or more third APIs to provide create, read, update, and delete (CRUD) program code to the model framework that is specific to data objects of the application, wherein the CRUD program code, when executed by the CPU, causes the CPU to manage the data objects in a manner that is specific to the application.

20. The non-transitory computer readable storage medium of claim 19 being stored on a mobile computing device.