Object oriented framework mechanism for fulfillment requirements management

• US 6,014,637 A
• Filed: 04/30/1997
• Issued: 01/11/2000
• Est. Priority Date: 04/30/1997
• Status: Expired due to Term

• Current Assignee: Workday Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Fell, Kathryn Anne, Heinz, Nancy Mae, Taylor, William Robert, Tollers, Gary V.
• Primary Examiner(s): Voeltz, Emanuel Todd
• Assistant Examiner(s): Dixon, Thomas A.
• Application Number:
  US08/846,921
• Time in Patent Office: 986 Days
• Field of Search: 705/26, 705/7, 705/8, 705/9, 705/10, 707/103, 707/104
• US Class Current: 705/26.8
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing

Abstract

An object oriented framework mechanism for fulfillment requirements management provides an infrastructure that embodies the steps necessary to manage and coordinate information throughout a given fulfillment requirements process, such as coordinating product information from the marketing of products to the ordering of products to the production of products. Certain core functions are provided by the framework, which interact with extensible functions provided by the framework consumer. The architecture of the framework allows a user to determine the conditions and parameters that apply to the specific environment while allowing a programmer to interact with the framework with an interface that is consistent regardless of the specific combination of parameters specified in the fulfillment requirements manager. The extensible functions allow new fulfillment requirements environments to be easily implemented using the framework. The framework thus allows a common programming interface for fulfillment requirements managers implemented using the framework, which may be easily customized to include new or changed parameters. The framework greatly simplifies the programmer'"'"'s job of developing an end-to-end system by providing a common programming interface, and by providing established classes that may be easily extended to implement the desired fulfillment requirements environment.

Claims

1. An apparatus, the apparatus managing fulfillment requirements for at least one item, the apparatus comprising:

a processor; and

a memory coupled to the processor; and

an object-oriented framework mechanism residing in the memory and executed by the processor, the framework mechanism providing at least one fulfillment requirements environment.

2. The apparatus of claim 1 wherein the framework mechanism comprises an entity class, the entity class defining:

at least one entity object corresponding to the at least one fulfillment requirements environment; and

a first set of object methods to perform a plurality of predetermined functions to implement the fulfillment requirements environment.

3. The apparatus of claim 2 wherein the entity class is an extensible class of the framework mechanism, the implementation of which by a user defines the at least one fulfillment requirements environment.

4. The apparatus of claim 2 wherein the first set of object methods includes:

at least one object method that creates the at least one entity object;

at least one object method that validates the at least one entity object;

at least one object method that prints the at least one entity object;

at least one object method that determines if the at least one entity object is available;

at least one object method that retrieves attributes of the at least one entity object;

at least one object method that retrieves availability of the at least one entity object;

at least one object method that retrieves a description for the at least one entity object;

at least one object method that retrieves a name for the at least one entity object;

at least one object method that retrieves at least one relationship for the at least one entity object; and

at least one object method that determines in which of the at least one relationship the at least one entity is used.

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

a class derived from the entity class that defines an entity offered to a customer;

a class derived from the entity class that defines an entity that is ordered that corresponds to the entity offered to the customer; and

a class derived from the entity class that defines an entity that is delivered to the customer that corresponds to the entity offered to the customer and to the entity that is ordered.

6. The apparatus of claim 1 wherein the framework mechanism comprises an availability class, the availability class defining:

at least one availability object corresponding to at least one entity object that is part of the fulfillment requirements environment; and

a second set of object methods to determine the availability of the at least one entity object.

7. The apparatus of claim 1 wherein the framework mechanism comprises a relationship class, the relationship class defining:

at least one relationship object corresponding to a plurality of entity objects; and

a third set of object methods to determine at least one relationship between the plurality of entity objects.

8. The apparatus of claim 1 wherein the framework mechanism comprises a history class, the history class defining:

at least one history object corresponding to at least one entity object that is part of the fulfillment requirements environment; and

a fourth set of object methods for determining the history of changes made to the at least one entity object.

9. The apparatus of claim 1 wherein the framework mechanism comprises a description class, the description class defining:

at least one description object corresponding to at least one entity object that is part of the fulfillment requirements environment; and

a fifth set of object methods for retrieving a description for the at least one entity object.

10. The apparatus of claim 1 wherein the framework mechanism comprises a rule class, the rule class defining:

at least one rule object corresponding to at least one entity object that is part of the fulfillment requirements environment; and

a sixth set of object methods for retrieving at least one rule for the at least one entity object.

11. The apparatus of claim 2 wherein the framework mechanism further comprises an availability class, the availability class defining:

at least one availability object corresponding to the at least one entity object; and

a second set of object methods to determine the availability of the at least one entity object.

12. The apparatus of claim 11 wherein the second set of object methods includes:

at least one object method that determines the availability date for the at least one entity object;

at least one object method that determines the general availability date for the at least one entity object; and

at least one object method that determines the withdraw date for the at least one entity object.

13. The apparatus of claim 11 wherein the availability class is a core class of the framework mechanism, the implementation of which cannot be changed by a user.

14. The apparatus of claim 11 wherein the framework mechanism further comprises a relationship class, the relationship class defining:

at least one relationship object corresponding to a plurality of entity objects; and

a third set of object methods to determine at least one relationship between the plurality of entity objects.

15. The apparatus of claim 14 wherein the third set of object methods includes:

at least one object method that determines the availability for the at least one entity object;

at least one object method that retrieves the attributes for the at least one entity object; and

at least one object method that retrieves at least one children object, if any exist, for the at least one entity object.

16. The apparatus of claim 14 wherein the relationship class is a core class of the framework mechanism, the implementation of which cannot be changed by a user.

17. The apparatus of claim 14 wherein the framework mechanism further comprises a history class, the history class defining:

at least one history object corresponding to the at least one entity object; and

a fourth set of object methods for determining the history of changes made to the at least one entity object.

18. The apparatus of claim 17 wherein the history class is a core class of the framework mechanism, the implementation of which cannot be changed by a user.

19. The apparatus of claim 17 wherein the framework mechanism further comprises a description class, the description class defining:

at least one description object corresponding to at least one entity object; and

a fifth set of object methods for retrieving a description for the at least one entity object.

20. The apparatus of claim 19 wherein the description class is a core class of the framework mechanism, the implementation of which cannot be changed by a user.

21. The apparatus of claim 19 wherein the framework mechanism further comprises a rule class, the rule class defining:

at least one rule object corresponding to the at least one entity object; and

a sixth set of object methods for retrieving at least one rule corresponding to the at least one entity object.

22. The apparatus of claim 21 wherein the rule class is an extensible class of the framework mechanism, the implementation of which by a user defines the at least one fulfillment requirements environment.

23. The apparatus of claim 21 wherein the entity class and the rule class are extensible classes of the framework mechanism, the implementation of which by a user defines the at least one fulfillment requirements environment, and wherein the availability class, the relationship class, the history class, and the description class are all core classes of the framework mechanism, the implementation of which cannot be changed by a user.

25. The apparatus of claim 1 wherein the memory contains an application program that supports an object oriented programming environment containing the framework mechanism, and wherein the framework mechanism is extended by providing information that implements the at least one fulfillment requirements environment.

26. The apparatus of claim 1 wherein the framework mechanism comprises:

at least one core function defined by at least one core class and by the relationships between a plurality of classes within the framework mechanism, wherein the implementation of the at least one core function is defined by the framework mechanism and cannot be modified by a user of the framework mechanism; and

at least one extensible function defined by at least one extensible class, wherein the implementation of the at least one extensible function is defined by the user of the framework mechanism by extending the at least one extensible class.

24. The apparatus of clam 21 wherein the entity class has a "contains by value" relationship with the availability class, the relationship class, the history class, the description class, and the rule class.

27. A method for managing fulfillment requirements, the method comprising the steps of:

providing an extensible object oriented framework mechanism that performs the managing of the fulfillment requirements according to extended portions of the framework mechanism that are customized to provide a desired fulfillment requirements environment; and

executing the object oriented framework mechanism on an apparatus.

28. The method of claim 27 further including the step of:

extending the framework mechanism to define the desired fulfillment requirements environment.

29. The method of claim 27 further including the steps of:

(a) creating a plurality of entity objects;

(b) validating the plurality of entity objects; and

(c) printing the plurality of entity objects.

30. The method of claim 29 further including the steps of:

(d) determining a plurality of relationships between at least two of the plurality of entity objects;

(e) determining availability for at least one of the plurality of entity objects;

(f) determining a name for at least one of the plurality of entity objects;

(g) retrieving attributes for at least one of the plurality of entity objects; and

(h) determining a description for at least one of the plurality of entity objects.

31. The method of claim 29 wherein the step of creating a plurality of entity objects includes the steps of:

(1) creating a first entity object;

(2) the creation of the first entity object causing the creation of a plurality of objects that are contained within the first entity object; and

(3) the creation of a selected one of the plurality of objects causing the creation of any objects contained within the selected object until all of the plurality of entity objects and any objects associated with the plurality of entity objects are created.

32. The method of claim 30 wherein the step of validating the plurality of entity objects includes the steps of:

(1) validating a first entity object;

(2) the validation of the first entity object causing the validation of a plurality of objects that are contained within the first entity object; and

(3) the validation of a selected one of the plurality of objects causing the validation of any objects contained within the selected object until all of the plurality of entity objects and any objects associated with the plurality of entity objects are validated.

33. The method of claim 30 wherein the step of printing the plurality of entity objects includes the steps of:

(1) printing a first entity object;

(2) the printing of the first entity object causing the printing of a plurality of objects that are contained within the first entity object; and

(3) the printing of a selected one of the plurality of objects causing the printing of any objects contained within the selected object until all of the plurality of entity objects and any objects associated with the plurality of entity objects are printed.

34. A program product comprising:

an object-oriented framework mechanism for managing fulfillment requirements, the framework mechanism including an extensible fulfillment requirements mechanism that processes a plurality of orders according to extended portions of the framework mechanism; and

signal bearing media bearing the framework mechanism.

35. The program product of claim 34 wherein the signal bearing media comprises recordable media.

36. The program product of claim 34 wherein the signal bearing media comprises transmission media.

37. The program product of claim 34 wherein the framework mechanism comprises:

at least one entity object that is part of the at least one fulfillment requirements environment; and

a first set of object methods to perform a plurality of predetermined functions to implement the fulfillment requirements environment.

38. The apparatus of claim 37 wherein the entity class is an extensible class of the framework mechanism, the implementation of which by a user defines the at least one fulfillment requirements environment.

39. The program product of claim 37 wherein the first set of object methods includes:

at least one object method that creates the at least one entity object;

at least one object method that validates the at least one entity object;

at least one object method that prints the at least one entity object;

at least one object method that determines if the at least one entity object is available;

at least one object method that retrieves attributes of the at least one entity object;

at least one object method that retrieves availability of the at least one entity object;

at least one object method that retrieves a description for the at least one entity object;

at least one object method that retrieves a name for the at least one entity object;

at least one object method that retrieves at least one relationship for the at least one entity object; and

at least one object method that determines in which of the at least one relationship the at least one entity is used.

40. The program product of claim 37 wherein the framework mechanism comprises:

at least one availability object corresponding to the at least one entity object; and

a second set of object methods to determine the availability of the at least one entity object.

41. The program product of claim 37 wherein the framework mechanism comprises:

at least one relationship object corresponding to a plurality of entity objects; and

a third set of object methods to determine at least one relationship between the plurality of entity objects.

42. The program product of claim 37 wherein the framework mechanism comprises:

at least one history object corresponding to the at least one entity object; and

a fourth set of object methods for determining the history of changes made to the at least one entity object.

43. The program product of claim 37 wherein the framework mechanism comprises:

at least one description object corresponding to the at least one entity object; and

a fifth set of object methods for retrieving a description for the at least one entity object.

44. The program product of claim 37 wherein the framework mechanism comprises:

at least one rule object corresponding to the at least one entity object; and

a sixth set of object methods for retrieving at least one rule for the at least one entity object.

45. The program product of claim 37 wherein the framework mechanism further comprises:

at least one object that corresponds to an entity offered to a customer;

at least one object that corresponds to an entity that is ordered that corresponds to the entity offered to the customer; and

at least one object that corresponds to an entity that is delivered to the customer that corresponds to the entity offered to the customer and to the entity that is ordered.

46. An object oriented framework mechanism for use in an apparatus that supports an object oriented programming environment, the framework mechanism comprising:

at least one entity object that is part of the at least one fulfillment requirements environment and a first set of object methods to perform a plurality of predetermined functions to implement the fulfillment requirements environment;

at least one availability object corresponding to the at least one entity object and a second set of object methods to determine the availability of the at least one entity object;

at least one relationship object corresponding to a plurality of entity objects and a third set of object methods to determine at least one relationship between the plurality of entity objects;

at least one history object corresponding to the at least one entity object and a fourth set of object methods for determining the history of changes made to the at least one entity object;

at least one description object corresponding to the at least one entity object and a fifth set of object methods for retrieving a description for the at least one entity object; and

at least one rule object corresponding to the at least one entity object and a sixth set of object methods for retrieving at least one rule for the at least one entity object.

47. The object oriented framework mechanism of claim 46 further comprising:

at least one object that corresponds to an entity offered to a customer;

at least one object that corresponds to an entity that is ordered that corresponds to the entity offered to the customer; and

at least one object that corresponds to an entity that is delivered to the customer that corresponds to the entity offered to the customer and to the entity that is ordered.

48. The object oriented framework mechanism of claim 46 wherein the first set of object methods includes:

at least one object method that creates the at least one entity object;

at least one object method that validates the at least one entity object;

at least one object method that prints the at least one entity object;

at least one object method that determines if the at least one entity object is available;

at least one object method that retrieves attributes of the at least one entity object;

at least one object method that retrieves availability of the at least one entity object;

at least one object method that retrieves a description for the at least one entity object;

at least one object method that retrieves a name for the at least one entity object;

at least one object method that retrieves at least one relationship for the at least one entity object; and

at least one object method that determines in which of the at least one relationship the at least one entity is used.

49. The object oriented framework mechanism of claim 46 wherein the framework mechanism comprises:

at least one core function defined by relationships between a plurality of classes within the framework mechanism, wherein the implementation of the at least one core function is defined by the framework mechanism and cannot be modified by a user of the framework mechanism; and

at least one extensible function defined by at least one extensible class, wherein the implementation of the at least one extensible function is defined by the user of the framework mechanism by extending the at least one extensible class.

50. A method for managing fulfillment requirements, the method comprising the steps of:

(A) providing at least one entity object that is part of an object-oriented framework mechanism that provides at least one fulfillment requirements environment and a first set of object methods to perform a plurality of predetermined functions to implement the fulfillment requirements environment;

(B) providing at least one availability object corresponding to the at least one entity object and a second set of object methods to determine the availability of the at least one entity object;

(C) providing at least one relationship object corresponding to a plurality of entity objects and a third set of object methods to determine at least one relationship between the plurality of entity objects;

(D) providing at least one history object corresponding to the at least one entity object and a fourth set of object methods for determining the history of changes made to the at least one entity object;

(E) providing at least one description object corresponding to the at least one entity object and a fifth set of object methods for retrieving a description for the at least one entity object;

(F) providing at least one rule object corresponding to the at least one entity object and a sixth set of object methods for retrieving at least one rule for the at least one entity object; and

(G) executing the object oriented framework mechanism on an apparatus to process at least one order.

51. The method of claim 50 further including the step of:

extending the framework mechanism to define the desired fulfillment requirements environment.

52. The method of claim 51 further including the steps of:

selecting functions required by the desired fulfillment requirements environment; and

extending the framework mechanism to implement an object method within the first set of object methods that performs all the selected functions.

53. The method of claim 52 further including the steps of:

selecting at least one creation criterion for determining whether a selected object should be created within the fulfillment requirements environment;

implementing the desired fulfillment requirements environment by defining the extended portions in accordance with the at least one creation criterion.

54. The method of claim 53 further including the steps of:

selecting at least one validation criterion for determining whether a selected object within the fulfillment requirements environment is valid;

the step of implementing the desired fulfillment requirements environment further including the step of defining the extended portions in accordance with the selected at least one validation criterion.

55. The method of claim 53 further including the steps of:

selecting at least one printing criterion for printing information pertaining to at least one object within the fulfillment requirements environment;

the step of implementing the desired fulfillment requirements environment further including the step of defining the extended portions in accordance with the selected at least one printing criterion.

56. A program product comprising:

(A) an object oriented framework mechanism for managing fulfillment requirements including at least one entity object that is part of the at least one fulfillment requirements environment and a first set of object methods to perform a plurality of predetermined functions to implement the fulfillment requirements environment, at least one availability object corresponding to the at least one entity object and a second set of object methods to determine the availability of the at least one entity object, at least one relationship object corresponding to a plurality of entity objects and a third set of object methods to determine at least one relationship between the plurality of entity objects, at least one history object corresponding to the at least one entity object and a fourth set of object methods for determining the history of changes made to the at least one entity object, at least one description object corresponding to the at least one entity object and a fifth set of object methods for retrieving a description for the at least one entity object, and at least one rule object corresponding to the at least one entity object and a sixth set of object methods for retrieving at least one rule for the at least one entity object, wherein the object oriented framework mechanism manages fulfillment requirements according to extended portions of the framework mechanism that are customized to provide the desired fulfillment requirements environment; and

(B) signal bearing media bearing the object oriented framework mechanism.

57. The program product of claim 56 wherein the signal bearing media comprises recordable media.

58. The program product of claim 56 wherein the signal bearing media comprises transmission media.

59. The program product of claim 56 wherein the object oriented framework mechanism further comprises:

at least one object that corresponds to an entity offered to a customer;

at least one object that corresponds to an entity that is ordered that corresponds to the entity offered to the customer; and

at least one object that corresponds to an entity that is delivered to the customer that corresponds to the entity offered to the customer and to the entity that is ordered.

60. The program product of claim 56 wherein the at least one entity object and the at least one rule object are defined by extensible classes of the framework mechanism, the implementation of which by a user defines the at least one fulfillment requirements environment.

61. The program product of claim 60 wherein the at least one availability object, the at least one relationship object, the at least one history object, and the at least one description object are defined by core classes of the framework mechanism, the implementation of which cannot be changed by a user.

62. An object oriented framework mechanism that manages fulfillment requirements, the framework mechanism comprising:

at least one core function defined by relationships between a plurality of classes within the framework mechanism, wherein the implementation of the at least one core function is defined by the framework mechanism and cannot be modified by a user of the framework mechanism; and

at least one extensible class wherein the implementation of the at least one extensible class is defined by the user of the framework mechanism, by extending the at least one extensible class, thereby defining at least one fulfillment requirements environment.

63. The object oriented framework mechanism of claim 62 further comprising:

at least one entity object that is part of the at least one fulfillment requirements environment and a first set of object methods to perform a plurality of predetermined functions to implement the fulfillment requirements environment;

at least one availability object corresponding to the at least one entity object and a second set of object methods to determine the availability of the at least one entity object;

at least one relationship object corresponding to a plurality of entity objects and a third set of object methods to determine at least one relationship between the plurality of entity objects;

at least one history object corresponding to the at least one entity object and a fourth set of object methods for determining the history of changes made to the at least one entity object;

at least one description object corresponding to the at least one entity object and a fifth set of object methods for retrieving a description for the at least one entity object; and

at least one rule object corresponding to the at least one entity object and a sixth set of object methods for retrieving at least one rule for the at least one entity object.

64. The object oriented framework mechanism of claim 63 further comprising:

at least one object that corresponds to an entity offered to a customer;

at least one object that corresponds to an entity that is ordered that corresponds to the entity offered to the customer; and

at least one object that corresponds to an entity that is delivered to the customer that corresponds to the entity offered to the customer and to the entity that is ordered.

65. The object oriented framework mechanism of claim 63 wherein the framework mechanism comprises an entity class, an availability class, a relationship class, a history class, a description class, and a rule class, and wherein the entity class has a "contains by value" relationship with each of the availability class, the relationship class, the history class, the description class, and the rule class.

66. A method for managing fulfillment requirements using an apparatus having a processor and a memory, the memory having an application program that provides an object oriented programming environment, the method comprising the steps of:

(A) providing in the program an object oriented framework mechanism that performs the fulfillment requirements according to extended portions of the framework mechanism that are customized to provide a desired fulfillment requirements environment, the framework mechanism including;

a set of core functions wherein the implementation of the core functions is defined by the framework mechanism and cannot be modified by a user of the framework mechanism; and

a set of extensible functions wherein the implementation of the extensible functions is defined by the user of the framework mechanism;

(B) extending the extensible functions in the framework mechanism to define particular classes having predetermined protocols and defining particular object methods that perform the fulfillment requirements, the extensible functions defining the desired fulfillment requirements environment;

(C) generating an executable fulfillment requirements system by integrating together the extensible functions and the core functions; and

(D) executing the executable fulfillment requirements system on the apparatus.

67. The method of claim 66 further including the steps of:

(a) creating a plurality of entity objects;

(b) validating the plurality of entity objects; and

(c) printing the plurality of entity objects.

68. The method of claim 67 further including the steps of:

(d) determining a plurality of relationships between at least two of the plurality of entity objects;

(e) determining availability for at least one of the plurality of entity objects;

(f) determining a name for at least one of the plurality of entity objects;

(g) retrieving attributes for at least one of the plurality of entity objects; and

(h) determining a description for at least one of the plurality of entity objects.

69. The method of claim 67 wherein the step of creating a plurality of entity objects includes the steps of:

(1) creating a first entity object;

(2) the creation of the first entity object causing the creation of a plurality of objects that are contained within the first entity object; and

(3) the creation of a selected one of the plurality of objects causing the creation of any objects contained within the selected object until all of the plurality of entity objects and any objects associated with the plurality of entity objects are created.

70. The method of claim 67 wherein the step of validating the plurality of entity objects includes the steps of:

(1) validating a first entity object;

(2) the validation of the first entity object causing the validation of a plurality of objects that are contained within the first entity object; and

(3) the validation of a selected one of the plurality of objects causing the validation of any objects contained within the selected object until all of the plurality of entity objects and any objects associated with the plurality of entity objects are validated.

71. The method of claim 67 wherein the step of printing the plurality of entity objects includes the steps of:

(1) printing a first entity object;

(2) the printing of the first entity object causing the printing of a plurality of objects that are contained within the first entity object; and

(3) the printing of a selected one of the plurality of objects causing the printing of any objects contained within the selected object until all of the plurality of entity objects and any objects associated with the plurality of entity objects are printed.

72. A program product comprising:

an object oriented framework mechanism for managing fulfillment requirements, the framework mechanism including at least one core function defined by relationships between a plurality of classes within the framework mechanism, wherein the implementation of the at least one core function is defined by the framework mechanism and cannot be modified by a user of the framework mechanism, the framework mechanism further including at least one extensible function defined by at least one extensible class, wherein the implementation of the at least one extensible class is defined by the user of the framework mechanism by extending the at least one extensible class, thereby defining a fulfillment requirements environment that governs the operation of the framework mechanism; and

signal bearing media bearing the object oriented framework mechanism.

73. The program product of claim 72 wherein the signal bearing media comprises recordable media.

74. The program product of claim 72 wherein the signal bearing media comprises transmission media.

75. The program product of claim 72 wherein the framework mechanism comprises:

at least one entity object that is part of the at least one fulfillment requirements environment and a first set of object methods to perform a plurality of predetermined functions to implement the fulfillment requirements environment;

at least one availability object corresponding to the at least one entity object and a second set of object methods to determine the availability of the at least one entity object;

at least one relationship object corresponding to a plurality of entity objects and a third set of object methods to determine at least one relationship between the plurality of entity objects;

at least one history object corresponding to the at least one entity object and a fourth set of object methods for determining the history of changes made to the at least one entity object;

at least one description object corresponding to the at least one entity object and a fifth set of object methods for retrieving a description for the at least one entity object;

at least one rule object corresponding to the at least one entity object and a sixth set of object methods for retrieving at least one rule for the at least one entity object; and

wherein the object oriented framework mechanism performs the fulfillment requirements according to extended portions of the framework mechanism that are customized to provide a desired fulfillment requirements environment.

76. The program product of claim 72 wherein the framework mechanism further comprises:

at least one object that corresponds to an entity offered to a customer;

at least one object that corresponds to an entity that is ordered that corresponds to the entity offered to the customer; and

at least one object that corresponds to an entity that is delivered to the customer that corresponds to the entity offered to the customer and to the entity that is ordered.