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

• US 9,038,015 B1
• Filed: 04/18/2014
• Issued: 05/19/2015
• 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:
  US14/256,667
• Time in Patent Office: 396 Days
• Field of Search: None
• US Class Current: 717/102
• 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 creating a development platform for mobile device applications interacting with a mainframe computer system comprising:

a. providing a preconstructed computer code set of connectors for a first set of information providers, first set of integration providers, and a first set of system behaviors;

b. defining a second set of information providers with which the mobile device application will interact;

c. defining a second set of integration providers with which the mobile device application will interact;

d. defining a second set of system behaviors of the mobile device application;

e. creating a machine readable domain model from the second set of information providers, second set of integration providers, and second set of integration providers;

f. processing the domain model using a domain model processor to generate a mobile device application/mainframe interface having app specific connectors associated the second set of information providers, second set of integration providers, and second set of system behaviors, and wherein said app specific connectors are derived from the first set of information providers, first set of integration providers, and first set of system behaviors; and

g. storing the mobile device application/mainframe interface on a development and operational computer system platform.

2. The method of claim 1, wherein the second set of information providers is data sources, messaging, or logic execution.

3. The method of claim 1, wherein the second set of integration providers is advertising, financial transactions, or social interaction.

4. The method of claim 1, wherein the second set of system behaviors is performance, analytics, security, or quality/testing.

5. The method of claim 1, wherein the domain model is in XML format.

6. The method of claim 1, wherein the preconstructed computer code set of connectors is stored on the development and operational computer system platform.

7. The method of claim 1, wherein the app specific connectors associated with the second set of information providers include destination server IP address, credentials, and target data name.

8. The method of claim 1, wherein the second set of information providers include data sources and messaging, the second set of system behaviors include analytics and security.

9. The method of claim 1, wherein the second set of information providers, second set of integration providers, and second set of system behaviors is generated from a user'"'"'s selections from pre-populated menus, and stored in computer memory in a machine readable format, and wherein the domain model is automatically created from the stored, user selected second set of information providers, second set of integration providers, and second set of system behaviors.

11. The method of claim 1 wherein the information provider is data sources, messaging, or logic execution.

12. The method of claim 1 wherein the integration provider is advertising, financial transactions, or social interaction.

13. The method of claim 1 wherein the system behaviors is performance, analytics, security, or quality/testing.

14. The method of claim 1 wherein information provider includes data sources and messaging and the system behaviors includes analytics and security.

15. The method of claim 1 wherein the mobile device application/mainframe interface stored on the development and operational computer system platform also contains at least portions of the preconstructed code set of generic connectors.

16. The method of claim 15 wherein mobile device application/mainframe interface is in compiled computer code format.

10. A method for interfacing mobile device applications with a mainframe computer system comprising:

a. creating a machine readable domain model defining at least one information provider with which the mobile device application will interact, at least one integration provider with which the mobile device application will interact, and at least one system behavior of the mobile device application;

b. processing the domain model using a domain model processor to automatically generate an mobile device application/mainframe interface having at least one app specific connector associated the at least one information provider, at least one integration provider, and at least one system behavior, and wherein said at least one app specific connector is derived from a preconstructed computer code set of generic connectors associated with said at least one information provider, at least one integration provider, and at least one system behavior;

c. storing the mobile device application/mainframe interface on a development and operational computer system platform.

17. The method of claim 10 wherein the machine readable domain model is in markup language format.

18. A computer system for generating a mobile software application/mainframe computer system interface comprising:

a. memory storing a preconstructed computer code set of connectors for a first set of information providers, first set of integration providers, and a first set of system behaviors;

b. logic configured to process a preconstructed machine readable domain model defining a second set of at least one information provider with which the mobile software application with interact, a second set of at least one integration provider with which the mobile software application will interact, and a second set of at least one system behavior of the mobile software application to generate the mobile software application/mainframe computer system interface having app specific connectors associated with the second set of at least one information provider, second set of integration provider, and second set of system behavior, and wherein said app specific connectors are derived from the first set of information providers, first set of integration providers, and first set of system behaviors.

19. The system of claim 18, wherein the system behaviors is performance, analytics, security, or quality/testing.

20. The system of claim 18, wherein information provider is data sources and messaging and the system behaviors is analytics and security.