Object mechanism and method for coupling together processes to define a desired processing environment in an object oriented framework

• US 6,195,791 B1
• Filed: 09/29/1998
• Issued: 02/27/2001
• Est. Priority Date: 03/11/1998
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Engstrom, Jan Olof, Proske, Barbara Regine, Graser, Timothy James, Carlson, Brent Allen, Lindblom, Ulf Jesper Thomas
• Primary Examiner(s): Hafiz, Tariq R.
• Assistant Examiner(s): BOOKER, KELVIN
• Application Number:
  US09/162,738
• Time in Patent Office: 882 Days
• Field of Search: 717/1, 717/2, 717/5, 717/4
• US Class Current: 717/100
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 9/4493 Object persistence

Abstract

In an object oriented computer system, a framework mechanism defines an infrastructure for allowing a user to couple processes in the framework together in any suitable way to define a desired process flow. A user first defines a static object structure that corresponds to the specific process flow from one process to the next. The processes in the framework may be flexibly coupled in any suitable order, so a process does not have knowledge of its predecessor or successor processes. Thus, at run-time, a process determines the next step in the process flow from the static object structure. Once a process determines its subsequent process, a client may then create the next process and invoke methods on one or more objects corresponding to the newly-created process. Each process thus determines at run-time the next step in the process flow from the static object structure that the user statically defined to configure the process flow, which defines the desired processing environment.

Claims

1. An apparatus comprising:

at least one processor;

a memory coupled to the at least one processor;

an object oriented framework mechanism residing in the memory, the object oriented mechanism including;

a static object structure that defines a plurality of processing levels coupled together to define at least one processing environment, each processing level in the static object structure including hierarchy level information that specifies allowable subsequent process steps, if any.

2. The apparatus of claim 1 wherein the static object structure is defined at configuration time for the object oriented framework mechanism.

3. The apparatus of claim 1 wherein the static object structure defines shared data and at least one shared policy.

4. The apparatus of claim 1 wherein each processing level in the static object structure also includes life cycle information corresponding to the processing level.

5. The apparatus of claim 1 further comprising a dynamic object structure having a plurality of levels that are each constructed in accordance with the hierarchy level information in the static object structure.

6. The apparatus of claim 5 wherein the dynamic object structure is constructed at run-time, when an application that uses the object oriented framework mechanism is executed.

7. The apparatus of claim 5 wherein a subsequent level in the dynamic object structure is created by invoking the hierarchy level information in the level in the static object structure corresponding to the current level to determine that the subsequent level is an allowable subsequent process step defined by the static object structure.

8. The apparatus of claim 5 wherein the framework mechanism further comprises:

a hierarchy level information class that defines at least one impact object corresponding to a processing level in the static object structure; and

a process detail class that defines at least one process detail object corresponding to a level in the dynamic object structure.

9. The apparatus of claim 5 wherein an instance of the process detail class is created using hierarchy level information in the static object structure.

10. An apparatus comprising:

(1) at least one processor;

(2) a memory coupled to the at least one processor,

(3) an object oriented order processing framework residing in the memory, the order processing framework including;

(A) a static object structure that defines a plurality of flexibly coupled process steps coupled together to define at least one order type, each process step in the static object structure including hierarchy level information that specifies allowable subsequent process steps, if any;

(B) a dynamic object structure having a plurality of order details that are each constructed in accordance with the hierarchy level information in the static object structure;

(C) a hierarchy level information class that defines at least one impact object corresponding to a process step in the static object structure; and

(D) an order detail class that defines at least one order detail object corresponding to an order detail in the dynamic object structure.

11. The apparatus of claim 10 wherein an instance of the order detail class is created using hierarchy level information in the static object structure.

12. An apparatus comprising:

a memory;

an object oriented framework residing in the memory, the object oriented framework including means for coupling together flexibly coupled processes in the object oriented framework to define a desired processing configuration by invoking at least one method on a static object structure that defines a plurality of processing levels coupled together to define at least one processing environment, each processing level in the static object structure including hierarchy level information that specifies allowable subsequent process steps, if any.

13. A method for defining a static object structure that includes a plurality of processing levels coupled together to define at least one processing environment, each level in the static object structure including hierarchy level information that specifies allowable subsequent process steps, if any, the method comprising the steps of:

defining a class hierarchy by coupling together a plurality of classes representing the plurality of processing levels; and

specifying a valid subsequent process, if one exists, for each processing level, each valid subsequent process corresponding to one of the plurality of classes at the next processing level.

14. The method of claim 13 further comprising the step of creating instances of each of the plurality of classes at run-time.

15. The method of claim 13 further comprising the step of defining life cycle information corresponding to each processing level.

16. The method of claim 13 wherein the plurality of classes correspond to a plurality of processes that may be flexibly coupled together in the framework to define a desired processing environment.

17. A method for processing a desired process type comprising the steps of:

(A) creating a static object structure that defines a plurality of processing levels coupled together to define the desired process type, each level in the static object structure including hierarchy level information that specifies allowable subsequent process steps, if any;

(B) when a client program needs to create a next step in a process flow defined by the process type, invoking a method on a current process detail;

(C) locating a process detail impact corresponding to the current process detail, the process detail impact including hierarchy level information that specifies allowable subsequent process steps, if any, that follow the process detail impact;

(D) determining from the process detail impact corresponding to the current process detail a child process detail impact corresponding to an allowable subsequent process step; and

(E) creating a child process detail that is a child of the current process detail in accordance with information in the child process detail impact.

18. The method of claim 17 further comprising the step of creating a reference in the child process detail to its corresponding child process detail impact.

19. The method of claim 17 further comprising the step of creating a reference in the child process detail to a life cycle that corresponds to the child process detail impact that corresponds to the child process detail.

20. The method of claim 17 further comprising the steps of accessing shared data and shared algorithms defined by the child process detail impact.

21. A program product comprising:

an object oriented framework mechanism mcluding a static object structure that defines a plurality of processing levels coupled together to define at least one processing environment, each processing level in the static object structure including hierarchy level information that specifies allowable subsequent process steps, if any; and

signal bearing media bearing the framework mechanism.

22. The program product of claim 21 wherein the signal bearing media comprises recordable media.

23. The program product of claim 21 wherein the signal bearing media comprises transmission media.

24. The program product of claim 21 wherein each processing level in the static object structure also includes life cycle information corresponding to the processing level.

25. The program product of claim 21 wherein the static object structure defines shared data and at least one shared policy.

26. The program product of claim 21 further comprising a dynamic object structure having a plurality of levels that are each constructed in accordance with the hierarchy level information in the static object structure.

27. The program product of claim 21 wherein the framework mechanism further comprises:

a hierarchy level information class that defines at least one hierarchical level information object corresponding to a processing level in the static object structure; and

a process detail class that defines at least one process detail object corresponding to a level in the dynamic object structure.

28. A program product comprising:

(1) an object oriented order processing framework including;

(A) a static object structure that defines a plurality of flexibly coupled process steps coupled together to define at least one order type, each process step in the static object structure including hierarchy level information that specifies allowable subsequent process steps, if any;

(B) a dynamic object structure having a plurality of order details that are each constructed in accordance with the hierarchy level information in the static object structure;

(C) a hierarchy level information class that defines at least one impact object corresponding to a process step in the static object structure; and

(D) an order detail class that defines at least one order detail object corresponding to an order detail in the dynamic object structure; and

(2) signal bearing media bearing the framework mechanism.

29. The program product of claim 28 wherein the signal bearing media comprises recordable media.

30. The program product of claim 28 wherein the signal bearing media comprises transmission media.