System for configuration programming

• US 20020129330A1
• Filed: 11/02/2001
• Published: 09/12/2002
• Est. Priority Date: 03/08/2001
• Status: Active Grant

• Current Assignee: Shiu, Martin
• Original Assignee: Shiu, Martin
• Inventors: Shiu, Martin
• Granted Patent: US 6,925,632 B2
• Time in Patent Office: Days
• US Class Current: 717/104
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

In a development platform, a classifier for a given application defines a data model of an application model as a pattern (an object model) from a finite number of patterns (object models) that represent the possible permutations of data models. In addition, the development platform has a finite number of service objects that perform various functions/services on the object model from which the application model adopts one or more service objects. The object models and the service objects are generic to the development platform and usually a set of finite number of object models and a set of finite number of service objects can interface the application model with the various third party resources and tools.

Claims

1. A method for creating application software comprising the steps of:

storing a first set of object models representing data of an application, each object model corresponding to a basic object type;

selecting a subset of service objects from a stored set of service objects each of which can perform a function with respect to data in at least one of the object models; and

defining a flow process representing an order for operation of the subset of service objects.

2. The method according to claim 1, wherein the basic object types include:

a primitive,

a class, and

an object array.

3. The method according to claim 2, wherein the class object type includes a plurality of attributes, each of which is a basic object type.

4. The method according to claim 2, wherein the object array object type includes a plurality of elements, each of the plurality of elements being of a single basic object type.

5. The method according to claim 1, wherein at least one of the service objects provides functions with respect to an identified device driver for a resource.

6. The method according to claim 1, further comprising the step of creating and storing a set of service objects.

7. The method according to claim 6, wherein the creating and storing step includes creating at least one service object which performs different functions depending upon a basic data type of at least one of the object models.

8. A system for creating application software comprising:

means for storing a first set of object models representing data of an application, each object model corresponding to a basic object type;

a stored set of service objects each of which can perform a function with respect to data in at least one of the object models; and

means for selecting a subset of the stored set of service objects; and

means for defining a flow process representing an order for operation of the subset of service objects.

9. The system according to claim 8, wherein the means for storing includes:

means for receiving a application model representing data in the application software;

means for classifying each data element in the application model as an object model; and

means for storing each object model from the classifying means.

10. The system according to claim 8, wherein at least one of the service models can an interface function with at least one resource.

11. A system for executing an application program comprising:

a stored set of object models representing data of the application, each object model corresponding to a basic object type;

a stored set of service objects each of which can perform a function with respect to data in at least one of the object models, wherein the function of a service object is based upon a basic object type of a corresponding object model;

means for determining a basic object type of a corresponding object model upon execution of each of the stored service objects; and

means for executing a function of each service object based upon the determined basic object type of a corresponding object model.