Guiding application building using business constraint metadata

• US 20060253830A1
• Filed: 05/06/2005
• Published: 11/09/2006
• Est. Priority Date: 05/06/2005
• Status: Abandoned Application

• Current Assignee: Callidus Software, Inc. (SAP SE)
• Original Assignee: Callidus Software, Inc. (SAP SE)
• Inventors: Liaw, Weikuo, Rajanala, Arun Kumar, Roopreddy, Ravindar R.
• Application Number:
  US11/123,980
• Publication Number:
  US 20060253830A1
• Time in Patent Office: Days
• US Class Current: 717/105
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

A computer-implemented method and system are provided for guiding application building using a registry of components, wherein the components are stored as metadata having a reference to one or more saved software procedures that are used to build custom applications. Aspects of the present invention include allowing a user to define an application definition based on business requirements, wherein the application definition comprises a process flow defining a series of process steps, user actions, and domain objects. Each process step identifies one or more domain objects from the business requirements, and each domain object is represented by one or more components in the component registry. A restricted set of components is then created using the components from the component registry that represent the domain objects specified in the application definition. During application building, only access to the restricted set of components is allowed, thereby improving correctness of the application by imposing constraints on the components available to build the application.

Claims

1. A computer-implemented method for guiding application building using a registry of components, wherein the components are stored as metadata having a reference to one or more saved software procedures that are used to build custom applications, the method comprising:

allowing a user to define an application definition based on business requirements, wherein the application definition comprises a process flow defining a series of process steps, user actions, and domain objects, wherein each process step identifies one or more domain objects from the business requirements, and wherein the domain objects are represented by one or more components in the component registry;

creating a restricted set of components using the components from the component registry that represent the domain objects specified in the application definition; and

only allowing access to the restricted set of components during application building, thereby improving correctness of the application by imposing constraints on the components available to build the application.

2. The method of claim 1 wherein the creation of the restricted set of components further includes:

for each step in the process flow, mapping the actions and domain objects specified in the step to corresponding components in the component registry, and using the identified components as the restricted set of components for the step so that when the step of the process flow is built during application building, only those components are made available.

3. The method of claim 2 further including:

providing the component registry during a component design phase;

allowing the user to create the application definition during an application design feature design phase; and

creating the restricted set of components during an application building phase.

4. The method of claim 3 further including:

guiding the user during the application building phase by displaying a user interface workspace that displays the process steps defined for the custom application, wherein for each step, the restricted set of components is displayed for user selection in order to build the step.

5. The method of claim 4 further including:

reading metadata rules for the components selected by the user and assembling the selected components as specified.

6. The method of claim 1 wherein the application definition further includes:

allowing the user to define the actions as at least one of role-based actions and task-based actions.

7. The method of claim 1 further including:

validating assembly and functionality of the application using the application definition to validate the functionality of the assembled steps;

after validating the assembled application, storing the application as runtime metadata that specifies the components selected by the user; and

after the application is deployed for use by an end user, using a runtime engine to run the application, wherein runtime engine reads the metadata in the runtime data and invokes the specified components.

8. The method of claim 1 further including:

implementing the components as object-oriented class templates that are stored as metadata definitions referencing one or more saved software procedures that are invoked at runtime, wherein the component registry include different types of components, including any combination of user interface components, user interface controls, process steps, user actions, business objects, and validators, and business logic rules.

9. The method of claim 8 further including:

identifying in the metadata for at least a portion of the components, the validator associated with the component, such that when the component is placed into the custom application, the validator associated with the component is automatically added to the application.

10. An application design tool for guiding a user through component-based application building, comprising:

a component registry for storing components as metadata having a reference to one or more saved software procedures;

a first module that enables a user to define an application definition based on business requirements for a custom application;

constraint metadata generated from the application definition;

a second module for guiding the user through a process of building an application using components from the component registry, wherein the constraint metadata is applied to the second module for restricting which components from the component registry are made available during assembly of the application; and

a runtime engine for reading application at runtime and invoking the specified components.

11. The application design tool of claim 10 wherein the constraint metadata is generated by:

for each step in the process flow, mapping the actions and domain objects specified in the step to corresponding components in the component registry, and using the identified components as the restricted set of components for the step so that when the step of the process flow is built during application building, only those components are made available.

12. The application design tool of claim 11 wherein the component registry is created during a component design phase.

13. The application design tool of claim 12 wherein a vendor of the application design tool bundles the component registry with the application design tool and makes the application design tool available to customers for designing and building custom applications.

14. The application design tool of claim 13 wherein the first module is invoked during an application design feature design phase to create the application definition.

15. The application design tool of claim 14 wherein the restricted set of components is created during an application building phase.

16. The application design tool of claim 15 wherein the application definition comprises a process flow defining a series of process steps, user actions, and domain objects.

17. The application design tool of claim 10 wherein the second module displays a user interface workspace that displays the process steps defined for the custom application and, for each step, the restricted set of components for user selection in order to build the step.

18. The application design tool of claim 17 wherein the second module reads metadata rules for the components selected by a user and assembling the selected components as specified by the constraint metadata.

19. The application design tool of claim 10 wherein the first module allows a user to define actions as at least one of role-based actions and task-based actions.

20. The application design tool of claim 10 wherein the second module validates assembly and functionality of the application using the constraint metadata to validate the functionality of the assembled steps.

21. The application design tool of claim 20 wherein the second module stores the validated application as runtime metadata that specifies the components selected by the user.

22. The application design tool of claim 21 wherein after the application is deployed for use by an end user, the runtime engine reads the metadata in the runtime data and invokes the specified components.

23. The application design tool of claim 10 wherein the components are implemented as object-oriented class templates that are stored as metadata definitions referencing one or more saved software procedures that are invoked at runtime, wherein the component registry include different types of components, including any combination of user interface components, user interface controls, process steps, user actions, business objects, and validators, and business logic rules.

24. The application design tool of claim 23 wherein the metadata for at least a portion of the components identifies the validator associated with the component, such that when the component is placed into the custom application, the validator associated with the component is automatically added to the application.

25. A computer-readable medium containing program instructions for guiding application building using a registry of components, wherein the components are stored as metadata having a reference to one or more saved software procedures that are used to build custom applications, the program instructions for:

allowing a user to define an application definition based on business requirements, wherein the application definition comprises a process flow defining a series of process steps, user actions, and domain objects, wherein each process step identifies one or more domain objects from the business requirements, and wherein the domain objects are represented by one or more components in the component registry;

creating a restricted set of components using the components from the component registry that represent the domain objects specified in the application definition; and

only allowing access to the restricted set of components during application building, thereby improving correctness of the application by imposing constraints on the components available to build the application.