Abstract: A method and system for enabling an automatic determination and allocation of product support resources. The automated process allocates support resources based on a combination of product and market requirements and historical data on resources used by similar products in similar markets. Projects requiring a support infrastructure are algorithmically classified by a combination of product complexity metrics and target market maturity metrics. Then, support infrastructure requirements are calculated based on the combined classification along with historical usage records for similarly classified products. The classification and allocation process is automated so that a product (or multiple products competing for available resources) can self-provision/request its resource requirement as a part of the product development and go-to-market process.

Abstract: A system for generating and retrieving relevant electronic information required by a user initiating an electronic search on the system. The system comprise a user-interactive search engine and a knowledge database, which stores knowledge information that is formatted. Additionally, the system includes a plurality of functional software modules that enables a user to complete an interactive search and find a solution to a task based on entered context information and keywords. A list of keywords are displayed to the user and the user selects those keywords that are relevant to the solution desired. The search engine looks for the articles containing the identified keywords. If no article is found with the search terms, the search is expanded to the Internet. The user may then modify the information returned from the Internet, format the information and save the information as a new recipe.

Abstract: A method for real-time automated maintenance of an electronic database. A value parameter is associated with each data component. The use history of each of the individual data components is tracked using the value parameter. A set number of points is assigned to each data component each time the component is retrieved in response to a user-entered search request. The set number of points is added to the value parameter. A minimum threshold value is established and at pre-determine time intervals a check is made to determine if any data component within the database fails to accumulate at least a minimum threshold number of points. Data components that have not accumulated the minimum number of points are removed from the database. When a new data component is added to the database, a default point value is assigned to the value parameter of the new component.

Abstract: A method and computer program product for enabling users of a search engine to utilize and create recipes for a knowledge database by tracking user responses. The user-entered query (goal or objective) is parsed and intelligent search techniques are utilized to provide a list of items, which are saved as the result set. If no hits occur, articles are returned from an external database, and the user is prompted to create a recipe from the returned articles. The created recipe becomes the user's solution to the problem. The user-created recipe is saved and fed back to the database where an administrator eventually approves it if it provides a viable solution to the task. The user is then provided a reward for providing the recipe. In this manner, database updates are driven by what the user's actually want and not what the system administrator thinks the users want.

Abstract: A system for generating and retrieving relevant electronic information required by a user initiating an electronic search on the system. The system comprise a user-interactive search engine and a knowledge database, which stores knowledge information that is formatted. Additionally, the system includes a plurality of functional software modules that enables a user to complete an interactive search and find a solution to a task based on entered context information and keywords. A list of keywords are displayed to the user and the user selects those keywords that are relevant to the solution desired. The search engine looks for the articles containing the identified keywords. If no article is found with the search terms, the search is expanded to the Internet. The user may then modify the information returned from the Internet, format the information and save the information as a new recipe.

Abstract: A method for real-time automated maintenance of an electronic database. A value parameter is associated with each data component. The use history of each of the individual data components is tracked using the value parameter. A set number of points is assigned to each data component each time the component is retrieved in response to a user-entered search request. The set number of points is added to the value parameter. A minimum threshold value is established and at pre-determine time intervals a check is made to determine if any data component within the database fails to accumulate at least a minimum threshold number of points. Data components that have not accumulated the minimum number of points are removed from the database. When a new data component is added to the database, a default point value is assigned to the value parameter of the new component.

Abstract: A framework for use with object-oriented programming systems provides a case-based reasoning (CBR) system shell that permits a framework user to develop a case base having case histories and generates a case-based reasoning system that receives user requests for query solutions and produces a query solution that can be incorporated into the case base. The framework includes a Session component that controls processing of the CBR system, a Control Flow component that manages the extension of the categories and classes of the OO framework, a Data Store component that stores persistent case structure definitions, case instances, and a change log, a Presentation component that manages the user interface to the CBR system user, and a Query Engine that evaluates a received query against the case base. The case definitions and case base descriptions comprise a set of object oriented classes that are organized into an inheritance hierarchy.

Abstract: An object oriented framework mechanism provides a straightforward and convenient way to implement an electronic catalog by providing an infrastructure that embodies the steps necessary for a framework consumer to define an electronic catalog by extending the framework to fit a particular electronic catalog environment. The electronic catalog framework includes core classes and extensible classes that allow a framework consumer to implement a desired electronic catalog. The core classes and class relationships define the core function of the framework mechanism. Extensible classes include a catalog class, a content page class, a table of contents page class, an index page class, a content list page class, a cover class, and a jacket class. These extensible classes are extended by a framework consumer to implement a desired electronic catalog environment.

Abstract: A framework for use with object-oriented programming systems provides a case-based reasoning (CBR) system shell that permits a framework user to develop a case base having case histories and generates a case-based reasoning system that receives user requests for query solutions and produces a query solution that can be incorporated into the case base. The framework includes a Session component that controls processing of the CBR system, a Control Flow component that manages the extension of the categories and classes of the OO framework, a Data Store component that stores persistent case structure definitions, case instances, and a change log, a Presentation component that manages the user interface to the CBR system user, and a Query Engine that evaluates a received query against the case base. The case definitions and case base descriptions comprise a set of object oriented classes that are organized into an inheritance hierarchy.

Abstract: The control data locking protocol allows a concurrency control manager and data store to permit concurrent dynamic access between those creating or modifying control data and those using the data in their execution sessions. The invention applies to the use of production rules in inferencing sessions or to the use of ordered processing of flow rules by a workflow manager. The invention grants inference locks, read locks and write locks. Pre-lock notification with negotiation is implemented. Post-lock notification is also implemented. Those who are using the rules and those who are modifying them can specify whether changes should be incorporated immediately. In case two requested locks conflict, users resolve the conflict before both are granted. Controlled invocation of conversion processing converts session data as necessary to allow changes in control data to be made while the control data is being used in existing execution sessions.