System and method for creating a development and operational platform for mobile applications

• US 9,934,003 B2
• Filed: 02/19/2016
• Issued: 04/03/2018
• Est. Priority Date: 04/23/2013
• Status: Active Grant

• Current Assignee: ClearBlade, Inc.
• Original Assignee: ClearBlade, Inc.
• Inventors: Allsbrook, David Aaron
• Primary Examiner(s): Tecklu, Isaac T
• Application Number:
  US15/047,753
• Publication Number:
  US 20160170716A1
• Time in Patent Office: 774 Days
• Field of Search: None
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

The present invention provides a system and method for constructing a complete definition of a backend requirements model that can be automatically accessed and interpreted, and generated into a mobile consumable API for creation of, and use with, mobile applications. The mobile consumable API can be provided and made available to mobile app developers on a separate, stand-alone platform, and may act as an intermediary between the mobile app and the primary mainframe/enterprise/back end system. The method may include identification and definition of one or more of information providers, integration providers, and system behaviors, and creating a domain model. The domain model may be automatically codified into an API based solution as the app/mainframe interface, and stored on a development and operational platform for use.

Claims

1. A method for interfacing a software application with an enterprise computer system comprising:

a. providing a preconstructed computer code set of at least one information provider connector, wherein the information provider connector is associated with a data source;

b. defining a software application specific data set comprised of at least one information provider with which the software application will interact, wherein the information provider with which the software application will interact is a data source;

c. creating a machine readable domain model from the software application specific data set; and

d. processing the domain model using a domain model processor to generate a software application/enterprise interface having app specific connectors associated with the software application specific data set, and wherein said app specific connectors are derived from the preconstructed computer code set of connectors.

2. The method of claim 1, wherein the software application/enterprise interface is stored on a development and operational computer system platform.

3. The method of claim 1, wherein the data source is a remote sensor.

4. The method of claim 3, wherein the software application/enterprise interface receives data from the remote sensor data source and stores such data in an electronic non-transitory memory storage media.

5. The method of claim 4, wherein the data from the remote sensor data source is comprised of state data.

6. The method of claim 5, wherein the state data includes at least one of temperature, location, and time.

7. The method of claim 5, wherein the state data is used for logic execution.

8. The method of claim 5, wherein the state data is stored in at least one database in a enterprise computer system with which the software application/enterprise interface interacts.

9. The method of claim 5, wherein the state data is stored in at least one database in the development and operational platform.

10. The method of claim 7, wherein alerts are sent based on the logic execution of the state data.

11. A method for interfacing a software application with an enterprise computer system comprising:

a. providing a preconstructed computer code set of connectors comprised of at least one of (i) information provider connectors or (ii) system behavior connectors, wherein the information provider connectors or the system behavior connectors are associated with a data source;

b. defining a software application specific data set comprised of at least one of (i) information providers with which the software application will interact or (ii) system behavior connectors of the software application, wherein the information provider connectors with which the software application will interact or the system behavior connectors of the software application is a data source;

c. creating a machine readable domain model from the software application specific data set;

d. processing the domain model using a domain model processor to generate a software application/enterprise interface having app specific connectors associated with the software application specific data set; and

e. receiving state information from a data source in communication with the enterprise computer system and storing said state information in an electronic non-transitory memory storage media.

12. The method of claim 11 wherein the data source is a sensor.

13. The method of claim 11 wherein the data source is a mobile device.

14. The method of claim 11 wherein the state information received from the data source is retained in the electronic non-transitory memory storage media if the data source loses communication with the enterprise computer system.

15. The method of claim 11 the state information in the electronic non-transitory memory storage is read and used for logic execution.

16. The method of claim 11, wherein the state information includes at least one of temperature, location, and time.

17. The method of claim 14 wherein the state information in the electronic non-transitory memory storage media is read and used for logic execution.

18. The method of claim 11, wherein the domain model is in XML format.

19. The method of claim 11 wherein said app specific connectors are derived from the preconstructed computer code set of connectors.

20. A method for interfacing software applications with an enterprise computer system comprising:

a. creating a machine readable domain model defining a software application specific connector data set, said software application specific connector data set comprised of at least one information provider with which the software application will interact;

b. processing the domain model to automatically generate a software application/mainframe interface having at least one app specific connector associated with the software application specific connector data set, and wherein said at least one app specific connector is derived from a preconstructed computer code set of connectors comprised of at least one of information provider connectors; and

c. receiving state information from a data source in communication with the enterprise computer system and storing said state information in an electronic non-transitory memory storage media.

21. A method for interfacing an information provider with an enterprise computer system comprising:

a. providing a preconstructed computer code set of at least one information provider connector, wherein the information provider connector is associated with a generic data source;

b. defining a data source specific data set comprised of at least one specific information provider with which the enterprise computer system will interact, wherein the information provider with which the enterprise computer system will interact is a specific data source;

c. creating a machine readable domain model from the data source specific data set; and

d. processing the domain model using a domain model processor to generate a specific data source/enterprise interface having app specific connectors associated with the data source specific data set, and wherein said app specific connectors are derived from the preconstructed computer code set of connectors.

22. The method of claim 21, wherein the data source is a remote sensor.

23. The method of claim 22, wherein the data source/enterprise interface receives remote sensor data from the remote sensor data source and stores the remote sensor data in an electronic non-transitory memory storage media.

24. The method of claim 23, wherein the remote sensor data from the remote sensor data source is comprised of state data.

25. The method of claim 24, wherein the state data includes at least one of temperature, location, and time.

26. The method of claim 25, wherein the state data is used for logic execution.

27. The method of claim 24, wherein the state data is stored in at least one database in the enterprise computer system with which the data source/enterprise interface interacts.

28. The method of claim 24, wherein the state data is stored in at least one database in the development and operational platform.

29. The method of claim 28, wherein alerts are sent based on the logic execution of the state data.