Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1998-12-11
2002-01-08
Amsbury, Wayne (Department: 2171)
Data processing: database and file management or data structures
Database design
Data structure types
Reexamination Certificate
active
06338069
ABSTRACT:
CROSS-REFERENCE TO RELATED APPLICATIONS
Not Applicable.
BACKGROUND OF THE INVENTION
1. Field of the Invention
The invention relates to the field of computer systems. More specifically, the invention relates to function management.
2. Background Information
Most corporate systems built to support certain business practices involve writing application logic within the application. The creator of the application writes the necessary programs in a language of personal desire and adds business specific rules for the application as a part of the module that contains the application. Thus, the business rules of an enterprise have been and are added overtime by different programmers; at different times; using different programming languages; for different applications of an enterprise; etc. This type of application development does not lend itself to maintainable components. Any updates to a business rule might impact the overall application. The application logic is not reusable for other enterprise wide applications, as it is contained within each application. This results in rewriting the same logic for different applications.
Certain other application programmers write the logic specific for the business as a separate module and link to it the other components of the application during execution or during compilation. Even though this allows for reuse of code, the corporations have to maintain a repository of these modules. There is rarely any documentation, much less transfer of knowledge to other departments regarding a module developed in a given department. However, an application developer must know the existence of the modules housing the business rules, as well as how to link them into the application. In addition, the functions in these modules have to be called explicitly. This type of application development does not lend itself to support “call on need” type of functions.
Other applications require the functions representing business rules to match a specified prototype. These functions are accessible through a data structure such as a hash structure (e.g., table, tree, graph, etc.) that contains function pointers. The dynamic selection of functions is supported through the use of a hash function that indexes into the hash structure. There are numerous search types (e.g., search by name, search by type) possible based on the native and complex data structures. This approach has several limitations. For example, additional data structures are required to support each search type. Also, it is difficult to maintain multiple data structures and keep them in sync for any updates/changes. In addition, this approach does not remove the need for extensive documentation and transfer of knowledge for the modules to be re-used.
Furthermore, there is no reasonable mechanism to search a business rule on the basis of its' output. Particularly, each business rule requires inputs and outputs. Before executing a given business rule, a programmer must provide the inputs for that business rule. It can be the case that one or more inputs of a given business rule is an output of a different business rule. Thus, in collecting the inputs for a given business rule, a user may be required to manually identify the collection of business rules whose outputs will provide the inputs for that given business rule. Particularly, a string of business rules, each of whose input is the output of another, may need to be executed to acquire the input needed for the business rule of interest. However, as these business rules are being added to the system, there is no good mechanism or infrastructure to track the input/output relationships between these business rules.
The lack of ability to track the input/output relationships between these business rules makes them difficult, if not impossible, to maintain and/or reuse. Thus, there is no reasonable mechanism by which a user can locate, much less execute, the business rules across the enterprise required to provide the inputs for a given business rule of interest. For example, a user interested in a particular input that is provided by a business rule would need know of that business rule, be able to locate that business rule, and know the format to call that business rule.
Additionally, since the business rules interface with the integration sources and/or other business rules of the enterprise, changing a given integration source and/or business rule can affect any number of other integration sources and/or business rules. However, it often cannot be determined what business rules and/or other integration sources will be affected by such changes. For example, although input/output relationships exists between the business rules, there is no mechanism for readily exposing these relationships. As a result, programmers are reluctant to make any changes, but instead attempt to extend integration sources and/or write new business rules.
BRIEF SUMMARY OF THE INVENTION
A method and apparatus for managing functions (e.g., that express business rules) to allow calling functions, maintaining functions, and providing of an execution framework for functions is described. According to one embodiment of the invention, a machine readable medium is provided having stored thereon a function, a first object, a second object, and an action unit. The function requires a set of one or more input parameters. The first object includes a structure storing a key for each of the input parameters to the function. In addition, the first object includes an action method, which when applied by a processor, causes that processor to invoke the action unit. The second object includes: 1) a first structure to store data for identifying, for one or more of the input parameters, the corresponding key and a value for that input parameter; and 2) a second structure identifying the first object. In addition, the second object includes an execute method, which when applied by a processor, causes that processor to apply the action method. The action unit includes instructions, which when executed by a processor, cause that processor to, access the values in the second object and invoke the function using those values as input parameters.
REFERENCES:
patent: 5481718 (1996-01-01), Ryu et al.
patent: 5497491 (1996-03-01), Mitchell et al.
patent: 5668958 (1997-09-01), Bendert et al.
patent: 5717925 (1998-02-01), Harper et al.
patent: 5721911 (1998-02-01), Ha et al.
patent: 5761678 (1998-06-01), Bendert et al.
patent: 5991768 (1999-11-01), Sun et al.
patent: 6128621 (2000-10-01), Weisz
patent: 6134559 (2000-10-01), Brumme et al.
patent: 6195662 (2001-02-01), Ellis et al.
patent: 6226628 (2001-05-01), Forbes
patent: 6226788 (2001-05-01), Schoening et al.
patent: 6253239 (2001-06-01), Shklar et al.
patent: 6263313 (2001-07-01), Milsted et al.
Integration Solutions for the Real-Time Enterprise: EIT-Enterprise Integration Template, Template Software (Table of Contents: 1 pg.; Contents: 3-28; Appendix I: 29-30; Appendix II: 31-32).
Object Technology, A Manager's Guide, Second Edition by David A. Taylor, Ph.D., 2/98 (Contents:v-vii; Acknowledgements: ix-x; Introduction: xi-xii; How to Read the Book; xiii-xvi; Chapter 1-9; 1-158; Appendix: 159-175; Suggested Reading: 177-182; Glossary: 183-198; Index: 199-205.
Upstream, A White Paper, Business Process Engines, A New Catagory of Server Software, Will Burst the Barriers in Distributed Application Performance by John Rymer, Upstream Consulting (pp. 1-16; Appendix: 16-19).
ADT Mar. 1997—Viewed as an effective new way to identify core business requirements, business rule thinking A/D is taking shape, Software Engineering (http://ww.adtmag.com/pub/mar97/softeng. (15 pgs.).
Amsbury Wayne
Blakely , Sokoloff, Taylor & Zafman LLP
Daman, Inc.
LandOfFree
Method and apparatus for managing functions does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method and apparatus for managing functions, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and apparatus for managing functions will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2843977