Computer-readable data product for managing sales information

0001This application is a Continuation of application Ser. No. 08/926,870, filed Sep. 10, 1997, now issued as U.S. Pat. No. 6,141,658, which application areis incorporated herein by reference.

FIELD OF THE INVENTION

0002The present invention relates to computerized sales systems. More particularly, the present invention relates to computer systems and methods for managing knowledge related to sales.

BACKGROUND OF THE INVENTION

0003In recent years, corporations have made increasing use of computer systems to manage information related to products. For example, corporations that manufacture and sell products use a variety of types of data to manufacture, market, and sell their products. Some types of data used in connection with these processes include, e.g., graphics, technical specifications, pricing information, marketing brochures, financing plans, blueprints, technical schematics, compatibility rules, option lists, competitive information, and sales programs. This product information can be stored, for example, using a computer-accessible database and retrieved using a search engine. The capabilities of modern computer systems have enabled corporations to store vast amounts of product information in a system.

0004Typically, product information is generated and used by a variety of departments of divisions within a corporation rather than by a single entity. This decentralization of data management has created a number of challenges. For example, different departments within a corporation sometimes create redundant or nearly redundant data, resulting in unnecessary use of data storage resources. In addition, the use of redundant data by different departments typically involves global updating of the data when, for example, product specifications change. Failure to update all instances of a particular item of information can have adverse consequences, such as inconsistencies in the information used by the departments. For example, an engineering department might use the most current version of an information item, while a marketing department, unaware of changes in technical specifications, might use an outdated version of the same item.

0005As the size and complexity of a computer database increase, product information becomes more vulnerable to such inconsistencies. Inconsistency of data can result from a number of other sources. For example, a particular product description can be spelled out verbatim by one department, but abbreviated by another. This inconsistency in documentation between departments can cause the corporate identity of this information to be lost or confused.

0006The distributed nature of many corporate databases has resulted in a number of additional difficulties. For example, it is often difficult to manage relationships between data items used by different departments. As a result, many corporate database fail to take full advantage of available computing resources to manage product information effectively. This inefficient use of computing resources leads to increased data maintenance costs in many cases.

0007In order to address the problems associated with distributed corporate databases, some techniques, known as data warehousing, integrate enterprise information into a centralized database known as data warehouse. In data warehousing techniques, information from one source or asset can be reused for multiple purposes of applications. The data warehouse can store a variety of types of information, including, for example, alphanumeric data such as pricing, descriptions, specifications, marketing content, competitive data, performance values, finance factors, and weights. In addition, the data warehouse can also store business rules, e.g., processes, administration directions, workflow guides, and factors, as well as media information, such as product graphics, computer-aided design (CAD) designs, and video and audio files. Documents, such as bulletins, letters, manuals, proposals, and spreadsheets can also be stored in the data warehouse. It should be understood that the data warehouse can store data and information of different types from those described above.

0008Exporting processes are typically used to define and control the manner in which information is reused. Conventional processes of this type typically involve specifying the types of information that are desired for a particular purpose or application through the structure of the data warehouse. The information of the specific types is then extracted and provided to a client. Exporting processes typically do not allow the user to define the purposes for which an individual instance of information can be used or to specify applications to which the instance of information is available. For example, of a data type defined as Price, two instances can be defined as Retail and Cost and can be used to support two different systems. In one system, designed for customers, it might be desirable to grant access to the Retail instance only. By contrast, in the other system, designed for salespersons, access should be granted to both the Retail and Cost instances. Many traditional exporting processes fail to provide sufficient flexibility to define differential access rights to these instances.

0009Some data management tools provide structures for distributed users to enter information into corporate databases. Many such tools, however, only support a small variety of structures and are inadequately adapted to handle varying data models. In addition, while data management tools allow users to define relationships between information, many tools of this type fail to adequately use these relationships within themselves. Consequently, many users find it difficult to organize or view their information based on these relationships. In addition, many data management tools provide system administrators with relatively few options for defining users' access rights to information. For example, some such tools only allow system administrators to define access rights to broad categories of information. The lack of flexibility of many of these tools limits the usefulness of such tools in many applications environments. The usefulness of many data management tools is often also limited by the complicated user interfaces, such as scripts, involved in defining data relationships. Using such complicated interfaces increases the technical skill required to work with databases in many cases.

SUMMARY OF THE INVENTION

0010According to one embodiment, of the present invention is directed to a computer system for managing product knowledge related to products offered for sale by a selling entity. The computer system includes a memory arrangement. At least one processing unit is coupled to the memory arrangement. The computer system also includes means for defining a data model that describes relationships between data categories. A data instance can be input that corresponds to one or more of the data categories. The data instance represents at least part of the product knowledge. The computer system also includes means for creating a user-defined relationship item for the data instance and means for presenting the product knowledge to a user of the system in a manner established by the data model and the user-defined relationship. The product knowledge that is presented includes information corresponding to the data instance.

0011According to another embodiment of the present invention, a computer system implemented method is used in managing product knowledge. The product knowledge comprises data items related to products offered for sale by a selling entity. The computer system includes a memory arrangement and at least one processing unit. The method comprises defining a data model of data categories. The data model establishingestablishes relationships between data categories. A particular data item is received in the computer system that corresponds to one or more of the data categories. User-defined relationship information is received for the particular data item. The relationship information relates the particular data item to one or more other data items. The product knowledge, which includes information about the particular data item, is presentpresented to a user of the system. The manner in which the product knowledge is presented is established by the data model and the user-defined relationship.

0012The above summary of the invention is not intended to describe each disclosed embodiment of the present invention. This is the purpose of the figures and of the detailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS

0013Other aspects and advantages of the present invention will become apparent upon reading the following detailed description and upon reference to the drawings in which:

0014<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an example system for managing enterprise information, according to an embodiment of the present invention;

0015<figref idref="DRAWINGS">FIG. 2</figref> illustrates an example menu bar that can be used to implement part of the system of <figref idref="DRAWINGS">FIG. 1</figref>, according to an embodiment of the present invention;

0016<figref idref="DRAWINGS">FIG. 3</figref> illustrates an example dialog box for use in connection with the example menu bar of <figref idref="DRAWINGS">FIG. 2</figref>, according to an embodiment of the present invention;

0017<figref idref="DRAWINGS">FIG. 4</figref> illustrates an example graphic user interface (GUI) for use in connection with the system of <figref idref="DRAWINGS">FIG. 1</figref>, according to an embodiment of the present invention;

0018<figref idref="DRAWINGS">FIG. 5</figref> illustrates an example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 4</figref>, according to an embodiment of the present invention;

0019<figref idref="DRAWINGS">FIG. 6</figref> illustrates another example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 4</figref>, according to an embodiment of the present invention;

0020<figref idref="DRAWINGS">FIG. 7</figref> illustrates another example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 4</figref>, according to an embodiment of the present invention;

0021<figref idref="DRAWINGS">FIG. 8</figref> illustrates another example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 4</figref>, according to an embodiment of the present invention;

0022<figref idref="DRAWINGS">FIG. 9</figref> illustrates another example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 4</figref>, according to an embodiment of the present invention;

0023<figref idref="DRAWINGS">FIG. 10</figref> illustrates another example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 4</figref>, according to an embodiment of the present invention;

0024<figref idref="DRAWINGS">FIG. 11</figref> illustrates another example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 4</figref>, according to an embodiment of the present invention;

0025<figref idref="DRAWINGS">FIG. 12</figref> illustrates another example graphic user interface (GUI) for use in connection with the system of <figref idref="DRAWINGS">FIG. 1</figref>, according to an embodiment of the present invention;

0026<figref idref="DRAWINGS">FIG. 13</figref> illustrates an example GUI for use in viewing and modifying the individual attributes of an instance, according to an embodiment of the present invention;

0027<figref idref="DRAWINGS">FIG. 14</figref> illustrates an example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 13</figref>, according to an embodiment of the present invention;

0028<figref idref="DRAWINGS">FIG. 15</figref> illustrates an example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 13</figref>, according to an embodiment of the present invention;

0029<figref idref="DRAWINGS">FIG. 16</figref> illustrates an example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 13</figref>, according to an embodiment of the present invention;

0030<figref idref="DRAWINGS">FIG. 17</figref> illustrates an example dialog box for use in connection with the GUI of <figref idref="DRAWINGS">FIG. 13</figref>, according to an embodiment of the present invention; and

0031<figref idref="DRAWINGS">FIG. 18</figref> illustrates an example hierarchy of data instances.

0032While the invention is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the invention to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

0033The present invention is believed to be applicable to a variety of systems and arrangements that manage sales information. The invention has been found to be particularly advantageous in environments characterized by distributed computing resources, such as many corporations that have several departments. An appreciation of various aspects of the invention is best gained through a discussion of various application examples operating in such environments.

0034According to the present invention, an integrated, powerful, and user-friendly knowledge management tool is provided for managing data stored in a data warehouse in a relational manner with a focus on customer solutions. Using this tool, users of a data warehouse can control access rights of various information producers and consumers in the system and can distribute content and control of individual instances of the information to other users. Moreover, the data in the data warehouse can be shared with a variety of other products and consumers of information, such as legacy systems or Internet sites. Distribution and management rights to the data can also be controlled on a detailed level.

0035Users can also define and understand relationships between information in the data warehouse. For example, users can define hierarchical relationships between information, behaviors associated with particular types of information, and rules governing the information. A data modeler creates and uses a data-driven data model to organize the items of information and the relationships between them as data objects. This type of data model allows the relationships between the information to be used to govern navigation in a graphic user interface (GUI) and the display and organization of information in the data warehouse. Some elements of the GUI are used to facilitate the definition of relationships between information. With a user-friendly GUI, the level of technical skill required to define relationships between information is reduced.

0036<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an example system <b>100</b> for managing enterprise information according to an embodiment of the present invention. The system <b>100</b> includes a data importer <b>102</b> that receives information from a data source <b>104</b>. The data source <b>104</b> can be, for example, a legacy system. It should be understood that, while <figref idref="DRAWINGS">FIG. 1</figref> illustrates a single data source <b>104</b>, the system <b>100</b> can include a plurality of data sources <b>104</b>. The data importer <b>102</b> converts the information from the data source <b>104</b> into a format compatible with the data warehouse.

0037An editor <b>106</b> is used for interactively editing data for insertion into the data warehouse. A user can employ a user system <b>108</b> to control the editor <b>106</b>. The user system <b>108</b> is implemented using one or more processors and can operate under any of a variety of operating systems that support Java, including, but not limited to, UNIX, Macintosh, and Microsoft Windows. It should be understood that the system <b>100</b> can include a plurality of user systems <b>108</b>. For example, each department in a corporation can have one or more user systems <b>108</b> communicatively coupled to the editor <b>106</b>. The editor <b>106</b> receives input from the user system <b>108</b> and manipulates data according to the received input. The manipulated data is exchanged with a data model <b>110</b> and is stored in a memory by the editor <b>106</b>. It should be understood that the memory can be implemented using any of a variety of data storage device types, including, but not limited to, semiconductor devices and magnetic and/or optical storage devices. In addition, the memory can incorporate more than one type of data storage device. Furthermore, the data can be stored using any of a variety of paradigms, such as data objects and relational databases.

0038The data model <b>110</b> creates and uses an object-oriented programming (OOP) environment to facilitate manipulation of the data by the editor <b>106</b>. In such an environment, hierarchical relationships between objects can be represented using pointers. Furthermore, objects can be defined as instances of object types. <figref idref="DRAWINGS">FIG. 18</figref> conceptually illustrates an example hierarchy <b>1800</b> of objects. The arrows represent pointers connecting related objects. For example, the top or root level in the example hierarchy of <figref idref="DRAWINGS">FIG. 18</figref> is occupied by an object <b>1802</b> representing the system model. The object <b>1802</b> is connected by pointers to its components, which include object <b>1804</b> representing customer information, product information, and configuration information. The object <b>1804</b> that represents configuration information is in turn connected by pointers to various instance <b>1806</b> of configuration information, e.g., Buick, Cadillac, and Chevrolet car information. It should be understood that the hierarchy can contain additional objects other than those illustrated. For example, the objects <b>1804</b> that represent customer and product information can themselves have various instances that are omitted from <figref idref="DRAWINGS">FIG. 18</figref> for purposes of clarity.

0039The instancesinstance <b>1806</b> representing Chevrolet cars has a number of instances of its own, which are represented by instance <b>1808</b> connected to the instance <b>1806</b>. The instance <b>1808</b> can represent, for example, particular models of Chevrolet cars. Submodels of cars can in turn be represented using instances <b>1810</b>, which are connected to the corresponding instance <b>1808</b>.

0040Objects can also be used to represent components of other objects. For example, the engine of a Chevrolet Cavalier coupe can be represented by an object <b>1812</b> that is linked to the object <b>1810</b> representing a Chevrolet Cavalier coupe. In addition, objects can represent attributes of other objects. In <figref idref="DRAWINGS">FIG. 18</figref>, objects <b>1814</b> represent various attributes of the engine in a Chevrolet Cavalier coupe, such as horsepower, RPM, and torque.

0041Referring again to <figref idref="DRAWINGS">FIG. 1</figref>, the editor <b>106</b> uses rules governing the objects, such as the relationships and other rules governing the objects, to construct a GUI for presenting the information to a user. For example, hierarchical relationships can be represented using levels in a tree-like structure. Instances of an object type can be illustrated similarly using the tree-like structure. It should be understood that other types of rules can be used to construct the GUI. For example, business rules, such as rules describing the compatibility between types of components, can be used to determine the placement of instances within the tree-like structure . The editor also defines a variety of active screen regions, such as dialog boxes, for use in defining relationships between information. These screen regions can include, for example, check boxes, buttons, slide controls, scroll bars, tabs, and other on-screen devices.

0042Data exporters <b>112</b> provide the information, or portions thereof, to a variety of users. The data exporters <b>112</b> can vary considerably in the types of information they present. For example, one type of data exporter <b>112</b> can be configured and arranged to provide information using the Internet, while another can be designed to generate printed materials, such as catalogues and the like. Still another type of data exporter <b>112</b> can use, for example, a technology enabled sales (TES) system to provide information to salespersons. In addition to these types, other types of data exporters <b>112</b> can be used to present selected information to a variety of audiences.

0043<figref idref="DRAWINGS">FIG. 2</figref> illustrates an example menu bar <b>200</b> that can be used to implement part of the system of <figref idref="DRAWINGS">FIG. 1</figref> according to an embodiment of the present invention. The menu bar <b>200</b> includes a number of active screen regions that, when activated by, for example, a mouse or other pointing device, cause pull-down menus to be displayed. A file menu activator <b>202</b>, when activated, provides access to a variety of file control operations, including, operating and closing of databases, file conversion, and exiting from the system. For example, when the user selects an “Open Database” option, a dialog box is displayed. An example dialog box <b>300</b> for use in opening a database is illustrated in <figref idref="DRAWINGS">FIG. 3</figref>. In the dialog box <b>300</b> of <figref idref="DRAWINGS">FIG. 3</figref>, a column <b>302</b> lists the names of the available databases, and a column <b>304</b> indicates the date on which each database was last updated. An indicator column <b>306</b> uses an icon to indicate the database that is currently open. The user can open a database by, for example, double-clicking on the name of the desired database or by highlighting the name and clicking on an “Open” button <b>308</b>. By checking a check box <b>310</b>, the user can specify that the currently open database should be opened as a default database whenever a particular user enters the editor.

0044Referring again to <figref idref="DRAWINGS">FIG. 2</figref>, a command menu activator <b>204</b> allows users to display the hierarchy of instances of data objects in the data model using a cascading popup menu. In addition, users with sufficient access rights can, for example, remove locks left in the database by abnormal exiting of the system.

0045By using a reports menu activator <b>206</b>, a user can generate reports using one or more formats for summarizing the contents of the database and logging database activity. A variety of formats are available. For example, in one format, the report lists the names of each object in the database, the parent object corresponding to each object, and the number of attributes in each object. In another format, the reported lists of all the attributes of all of the objects, as well as the properties of each object. In still another format, the contents of every instance of every object in the database are displayed. Using the reports menu activator <b>206</b>, the user can also search the database for all instances that contain, for example, a specified code.

0046The menu bar <b>200</b> can include a number of additional menu activators. For example, the menu bar <b>200</b> illustrated in <figref idref="DRAWINGS">FIG. 2</figref> includes a language menu activator <b>208</b> that allows the user to select a language for interfacing with the database. A help menu activator <b>210</b> provides access to a searchable help file.

0047<figref idref="DRAWINGS">FIG. 4</figref> illustrates an example GUI <b>400</b> for use in connection with the editor <b>106</b> of <figref idref="DRAWINGS">FIG. 1</figref>. The GUI <b>400</b> enables the user to select from a variety of formats known as structures or views for viewing and organizing data in the database by using a cascading popup format selector <b>402</b>. These structures or views are based on a data-driven data model and are derived from the hierarchy of data instances within the data model and from the relationships between the instances. Selecting an item in the cascading popup format selector <b>402</b> repopulates the hierarchy based on a starting point, such as the first item in the hieararchyhierarchy, in the data model.

0048In the example GUI <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref>, the user has selected a view that allows viewing of the entire hierarchy. With this view selected, the user can traverse through a tree-like structure <b>404</b> that represents the hierarchy. If submodels of the data model exist, the cascading popup format selector <b>402</b> displays an additional cascaded level to enable the user to view individual submodels.

0049Using a mouse or other pointing device, the user can view different levels of the hierarchy by using a collapse button <b>406</b> and/or an expansion button <b>408</b>. For example, actuating the collapse button <b>406</b> causes the objects uderunder, for example, the “System Model” object to be hidden. Conversely, actuating the expansion button <b>408</b> reveals any instances of the selected object, e.g., the “Quote” object. Any such instances can be displayed as lower levels in the hierarchy. The manner in which objects and instances are presented in the GUI <b>400</b> is determined by the relationships between the instances of the data objects. It should be understood that alternative views can be selected, such as a view that displays classes of objects.

0050The user can highlight an object in the tree-like structure <b>404</b> to flag it as a selected object <b>410</b> for in-depth viewing and editing. In the example GUI <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref>, the user has selected the “System Model” object. A navigational grid <b>412</b> is repopulated with the children objects or instances of the selected object <b>410</b>, allowing the user to edit the contents of the selected object <b>410</b>. In the navigational grid <b>412</b>, a name column <b>414</b> displays the names of the instances. A description column <b>416</b> displays the descriptions of the instances, as contained, for example, in a “Use a Description” attribute of the instances. If an instance has pointers, but has no attributes flagged as a description or name, the description column <b>416</b> displays the first attribute in the instance as the description of the instance. An instance type column <b>418</b> displays the types of the instances as assigned by the data modeler. If an instance has children objects of its own, an indicator column <b>420</b> displays an active icon that allows the user to view them.

0051By highlighting an instance in the navigational grid <b>412</b> and activating a secondary function of the pointing device, e.g., “right-checkingright clicking” on a selected instance, the user can invoke a popup menu (not shown). This popup menu provides access to various operations for manipulating instances. Such operations include, for example, deleting objects, sorting objects, and filtering objects.

0052Other operations can be accessed using the popup menu. For example, the user can invoke a dialog box <b>500</b> of <figref idref="DRAWINGS">FIG. 5</figref> to add new instances. The dialog box <b>500</b> contains a text entry field <b>502</b> for entering the name of a new instance. The user can then select the type of the new object using an instance type list box <b>504</b>. After entering the name and type of the new object, the user can actuate a button <b>506</b> to add the object and exit the dialog box <b>500</b>.

0053The user can also use the popup menu to invoke a dialog box <b>600</b> of <figref idref="DRAWINGS">FIG. 6</figref> to attach an existing instance to the selected instance. An instance type list box <b>602</b> allows the user to select the type of the existing object to be attached. Upon selection of a type, an available instances list box <b>604</b> lists the objects of the selected type. A name column <b>606</b> displays the names of the objects of the selected type, and a description column <b>608</b> displays their descriptions. The user can then use check boxes <b>610</b> to select one or more objects of the selected type to attach to the selected instance.

0054The popup menu can also be used to invoke a dialog box <b>700</b> of <figref idref="DRAWINGS">FIG. 7</figref> for duplicating instances. A tree-like structure <b>702</b> displays the hierarchy of instances of data objects. Expansion buttons <b>704</b> and collapse buttons <b>706</b> respectively allow the user to expand and collapse levels in the tree-like structure <b>702</b>. By highlighting an object, the user marks it as a selected object <b>708</b>. The selected object <b>708</b> can then be duplicated in whole or in part. The amount of the selected object <b>708</b> to be duplicated can be controlled using radio buttons <b>710</b>. For example, by selecting one radio button <b>710</b>a, the user can choose to duplicate all attributes of the selected object <b>708</b>. By selecting another radio button <b>710</b>b, the user can duplicate all links of the selected object <b>708</b>. Still another radio button <b>710</b>c allows the user to duplicate both attributes and links of the selected object <b>708</b>. Yet another radio button <b>710</b>d allows the user to duplicate only the selected object <b>708</b> itself. By actuating a button <b>712</b>, the user causes the system to create an instance that is identical to the selected object <b>708</b>. The pointers of the duplicate object point to the same instances as the pointers of the selected object <b>708</b>.

0055The user can also use the popup menu to invoke a dialog box <b>800</b> of <figref idref="DRAWINGS">FIG. 8</figref> to attach an instance to, for example, predefined groups or markets. An instance type list box <b>802</b> allows the user to select the type of the instance to be attached. Upon selection of a type, an available group list box <b>804</b> lists the groups to which the instance type can be attached. A name column <b>806</b>, a description column <b>808</b>, and an instance type column <b>810</b> respectively display the names, descriptions, and types of the available groups. The user can then use check boxes <b>812</b> to select one or more groups to which the selected instance is to be attached. By actuating a button <b>814</b>, the user can attach the selected instance to the selected group or groups and exit the dialog box <b>800</b>.

0056The popup menu can also access a dialog box <b>900</b> of <figref idref="DRAWINGS">FIG. 9</figref> for use in searching for an instance. A text entry field <b>902</b> allows the user to enter target next to be located. A pull-down menu <b>904</b> allows the user to specify the areas to be searched for the target text, and radio buttons <b>906</b> can be used to specify whether the search is to cover all fields or the current field only. Radio buttons <b>908</b> are used to specify the direction (i.e., up or down) of the search. Check boxes <b>910</b> and <b>912</b> respectively allow the user to specify whether the search is to be case-sensitive and/or formatting-sensitive. A button <b>914</b> allows the user to search for the first occurrence of the target text. Subsequent occurrences can be found using a button <b>916</b>.

0057A dialog box <b>1000</b> of <figref idref="DRAWINGS">FIG. 10</figref> provides access to replace functions. Text entry fields <b>1002</b> and <b>1004</b> respectively allow the user to enter target text to be found and replacement text for substitution in place of the target text. Radio buttons <b>1006</b> allows the user to confine the search to the current field, or to specify that the search is to cover all fields. Check boxes <b>1008</b> and <b>1010</b> are respectively used to specify whether the search is to be case-sensitive and/or formatting sensitive. The user can actuate buttons <b>1012</b> and <b>1014</b> to find the first and subsequent occurrences of the target text, respectively. Actuating a button <b>1016</b> causes the target text to be replaced by the replacement text for the selected occurrence, and actuating a button <b>1018</b> causes all occurrences of the target text to be replaced by the replacement text.

0058The popup menu can also be used to invoke a dialog box <b>1100</b> of <figref idref="DRAWINGS">FIG. 11</figref> for filtering instances by class. An available class column <b>1102</b> displays the classes of instances that are available for display. Using check boxes <b>1104</b>, the user can select which classes are visible. A check box <b>1106</b> allows the user to specify that all classes should be visible. By actuating a button <b>1108</b>, the user confirms his or her selection.

0059<figref idref="DRAWINGS">FIG. 12</figref> illustrates another example GUI <b>1200</b> for use in connection with the editor <b>106</b> of <figref idref="DRAWINGS">FIG. 1</figref>. The GUI <b>1200</b> can be invoked, for example, by double-clicking on a selected instance in the GUI <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref>. The GUI <b>1200</b> allows the user to view information that is related to the instance selected using the GUI <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref>.

0060The GUI <b>1200</b> can be conceptually divided into a number of screen regions. A navigational path list <b>1202</b> and a navigational grid <b>1204</b> are used to navigate through the hierarchy of instances of data objects based on a user-selected view. In the navigational path list <b>1202</b>, selecting an instance of the hierarchy by, for example, double-clicking, causes the navigational grid <b>1204</b> to display instances related to the selected instance. Selecting an instance also caused subordinate instances to be hidden on the navigational path list <b>1202</b>. Accordingly, the selected instance appears at the bottom of the navigational path list <b>1202</b>, and its related instances appear in the navigational grid <b>1204</b>.

0061In the navigational grid <b>1204</b>, the user can select or edit an instance by, for example, single- or double-clicking on the instance. A related instances folder list <b>1206</b> displays instances related to the selected instance as active tabs <b>1208</b>. By selecting an active tab <b>1208</b>, the user causes the corresponding instance and its attributes to be displayed in a grid <b>1210</b>. Other information is optionally displayed in the grid <b>1210</b>, such as information regarding activity related to the selected instance. In addition, check boxes <b>1212</b> allow the user to define the exportability of the related instances. For example, the user can specify whether the related instances can be exported over the Internet, computerized sales systems, kiosks, and the like. The contents of the folder list <b>1206</b> and the grid <b>1210</b> change in response to changes in the selection of an instance.

0062The user can also access a popup menu (not shown) by, for example, right-clicking on an instance in the navigational grid <b>1204</b> or the grid <b>1210</b>. This popup menu is similar in structure and functionality to the popup menu invoked in connection with the GUI <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref> and is used to invoke dialog boxes similar to those illustrated in <figref idref="DRAWINGS">FIGS. 5-11</figref>. Accordingly, discussion of the popup menu invoked in connection with the navigational grid <b>1204</b> and the grid <b>1210</b> is omitted in the interest of brevity.

0063<figref idref="DRAWINGS">FIG. 13</figref> illustrates an example GUI <b>1300</b> for use in viewing and modifying the individual attributes of an instance. The functions that can be accessed using the GUI <b>1300</b> are similar to those made available for editing instances by the GUI <b>400</b> of <figref idref="DRAWINGS">FIG. 4</figref>. In addition, the user can use the GUI <b>1300</b> to edit individual attributes of a selected instance. The GUI <b>1300</b> also provides access to dialog boxes such as those illustrated in <figref idref="DRAWINGS">FIGS. 14-17</figref> to facilitate entry of certain types of attributes and definition of rules governing instances. Furthermore, the GUI <b>1300</b> provides shortcuts into commonly used functions.

0064A pull-down menu <b>1302</b> allows the user to display and navigate between the current instance and its siblings. The contents of the menu <b>1302</b> reflect the contents of the navigational grid <b>412</b> of <figref idref="DRAWINGS">FIG. 4</figref>. The list of sibling instances can be navigated using buttons <b>1304</b>. Instances associated with the selected instance are organized as folders <b>1306</b> in a folder list <b>1308</b>. The user can select an instance to view and edit by clicking on a folder <b>1306</b>. A grid <b>1310</b> display attributes of the current instance selected in the menu <b>1302</b>. The grid <b>1310</b> also displays attributes of associated instances sorted by class. In addition, check boxes <b>1312</b> can be used to control the exportability of the selected instance to a variety of exporters.

0065The grid <b>1310</b> can also be used to access a popup menu (not shown) by, for example, right clicking on an instance. This popup menu can be used to manipulate the selected instance in a variety of ways. For example, the instance can be cut or copied to a clipboard or deleted. Instances can also be pasted from the clipboard using the popup menu. In addition, the popup menu can be used to add a new instance of the class selected in the folder list <b>1308</b>.

0066An attributes grid <b>1314</b> allows the user to display and edit the attributes of an instance. Columns <b>1316</b> and <b>1318</b> respectively display names and associated values of the attributes. A set of buttons <b>1320</b> are used to access dialog boxes to facilitate data entry. The buttons <b>1320</b> can access, for example, the dialog boxes shown in <figref idref="DRAWINGS">FIGS. 14-17</figref>. Right-clicking on an attribute within the attributes grid <b>1314</b> invokes a popup menu that can be used to manipulate the attribute in a variety of ways. For example, the value of the attribute can be cut or copied to the clipboard or cleared. In addition, a value stored on the clipboard can be pasted to the attribute. Moreover, the dialog boxes shown in <figref idref="DRAWINGS">FIGS. 14-17</figref> can be accessed using the popup menu.

0067Function buttons <b>1322</b> provide shortcuts into commonly used functions. For example, a function button <b>1322</b>a allows the user to create a new instance of the class selected in the folder list <b>1308</b>. Another function button <b>1322</b>b provides the ability to copy the current instance, while still another function button <b>1322</b>c allows the user to delete the current instance. Yet another function button <b>1322</b>d invokes the dialog box <b>800</b> of <figref idref="DRAWINGS">FIG. 8</figref> for use in attaching the current instance to a group or groups. It should be understood that the GUI <b>1300</b> can incorporate function buttons <b>1322</b> of other types.

0068<figref idref="DRAWINGS">FIG. 14</figref> illustrates an example dialog box <b>1400</b> for entering dates into the database. The user can enter dates using a text entry field <b>1402</b>. Alternatively, the user can use a calendar <b>1404</b>. The calendar includes month scroll buttons <b>1406</b> and <b>1408</b> for scrolling backward and forward through a list of months. Year scroll buttons <b>1410</b> and <b>1412</b> allows the user to scroll backward and forward through a range of years. The calendar <b>1404</b> displays the days of the month selected using the scroll buttons <b>1406</b>, <b>1408</b>, <b>1410</b>, and <b>1412</b>. The user can then select a particular date within the month by highlighting it.

0069<figref idref="DRAWINGS">FIG. 15</figref> illustrates an example of dialog box <b>1500</b> for selecting file types associated with an instance. The dialog box <b>1500</b> includes a column <b>1502</b> that displays available file types, e.g., audio, bitmap, document, text, and video. Check boxes <b>1504</b> are used to select one or more file types to associate with the instance.

0070<figref idref="DRAWINGS">FIG. 16</figref> illustrates an example dialog box <b>1600</b> for use in associating attribute values with descriptors. A text entry field <b>1602</b> allows the user to enter a text description of an attribute. The dialog box <b>1600</b> also includes a set of tabs <b>1604</b> and <b>1606</b> that respectively allow the user to associate values and descriptors and to select languages for the descriptions. Using the tab <b>1606</b>, the user can enter a plurality of descriptions in different languages for a single attribute.

0071The tab <b>1604</b> contains a grid <b>1608</b> of descriptors and values. An identifier column <b>1610</b> lists the descriptors that are associated with attribute values. An attributes column <b>1612</b> lists the attribute type of each descriptor, and an item column <b>1614</b> further describes the associated value, e.g., “Governed RPM.” The associated values are displayed in a value column <b>1616</b>, and conditions or rules under which the associated values apply are displayed in a condition column <b>1618</b>. The values, descriptors, and conditions can be edited by clicking on cells in the grid <b>1608</b>. A menu <b>1620</b> allows the user to select types of descriptors, e.g., technical descriptors, to be displayed.

0072Function buttons <b>1622</b> provide shortcuts into commonly used functions. For example, a function button <b>1622</b>a allows the user to create a new descriptor and associated value. Another function button <b>1622</b>b provides the ability to copy the current descriptor and associated value, while still another function button <b>1622</b>c allows the user to delete the current descriptor and associated value. Yet another function button <b>1622</b>d invokes the dialog box <b>800</b> of <figref idref="DRAWINGS">FIG. 8</figref> for use in attaching the current descriptor and associated value to a group or groups. It should be understood that the dialog box <b>1600</b> can incorporate function buttons <b>1622</b> of other types.

0073<figref idref="DRAWINGS">FIG. 17</figref> illustrates an example dialog box <b>1700</b> for use in defining rules that describe relationships between information. For example, using the dialog box <b>1700</b>, the user can define a relationship between one type of data object representing product lines and another representing technical specifications. The relationships between instances of data objects, in combination with the instances themselves, are used in defining the hierarchy of instances of data objects. A text entry box <b>1702</b> allows the user to enter rules in textual form. Alternatively, the user can use a variety of active screen regions to reduce the number of keystrokes involved in defining a rule. For example, a tree-like structure <b>1704</b> representing the hierarchy of instances can be used to select objects that are to be inserted in the rule definition. Clicking on an expansion button <b>1706</b> expands a level of the hierarchy. Instances associated with a selected object <b>1708</b> are displayed in an associated instances grid <b>1710</b>. The associated instances and their attributes can also be inserted in the rule definition.

0074The dialog box <b>1700</b> also includes a variety of buttons that can be used in place of keystrokes in defining rules. A set of arithmetic operator buttons <b>1712</b> allow the user to insert arithmetic operators into the rule definition. Similarly, an address-of (&amp;) operator button <b>1714</b> allows the user to insert an address-of operator, which returns the address of its operand, into the rule definition. Comparison operator buttons <b>1716</b> provide access to operations that compare objects. A set of logical operator buttons <b>1718</b> allow the user to insert logical operations into the rule definition. Precedential operator buttons <b>1720</b> allow the user to define the order in which operations are performed in the rule definition. A paste button <b>1722</b> enables the user to paste text from the clipboard to the rule definition. This button is particularly useful for defining rules that are similar.

0075In accordance with another aspect of the present invention, the system can assign access rights to various users of the system. The system recognizes several types of users with differentiated access rights. Examples of types of users include, but are not limited to, system administrationadministrators, database administrators, data model owners, product managers, product experts, and data entry clerks. Each type of user is responsible for certain goals of the system. For example, the system administrator is responsible for system management, while the data entry clerk is responsible for data management. Some users, such as the database administrator, can be responsible for both system and data management.

0076One type of user recognized by the system is the system administrator. The system administrator is responsible for both user and database administration. To assist the system administrator in user administration, the system provides a number of functions to the system administrator. For example, the system administrator can define access rights on an instance basis. Accordingly, the system administrator can grant a particular user rights to access and manipulate one instance of an object that represents a particular product line, while withholding access rights to another instance of the same object that represents a different product line. This ability to grant differentiated access rights to instances of a single object type is particularly advantageous, for example, in environments in which employees work only on selected product lines. It should be understood that granting rights to access a particular instance of a data object typically, but not necessarily, impliedly grants rights to access subordinate instances in the hierarchy. In addition, the system administrator can add, delete, and edit users. Certain functions, such as searching for users, are implied by these abilities. The system also allows the system administrator to perform certain database administration functions, such as backing up the database.

0077Another type of user recognized by the system is the database administrator, who is responsible for database administration. Like the system administrator, the database administrator can backup the database. Moreover, the database administrator has access to a variety of additional database administration functions. For example, the system allows the database administrator to create new databases and to edit or delete existing databases. Furthermore, the database administrator can duplicate existing databases. The system also enables the database administrator to recover a database from a backup. The database administrator also has access to certain functions that facilitate maintaining database security. For example, the database administrator can use, display and clear an activity log known as an audit trail to monitor accesses to the database and operations performed on the database.

0078The system also recognizes a data model owner, who assumes some responsibility for managing the data in the database. To facilitate the fulfillment of this responsibility, the system allows the data model owner to generate reports that list the objects in the database and their attributes, as well as the data continued in a selected object. In addition, the data model owner can view all of the data in the database. The data can be viewed either by class or by instances of a class. The instances can be searched, replaced, sorted, edited, or moved between classes. When the user moves an instance between classes, the system attempts to insert instance data into shared attributes. If the destination class is a child of the source class, any additional attributes in the destination class are left empty. If, on the other hand, the destination class is a parent of the source class, any additional attributes in the source class are deleted. If the destination and source classes are unrelated, certain attributes may be either left empty or deleted. The system attempts type coercion to make data fit into the attributes of the destination class.

0079Instances that use a selected instance or that are used by the selected instance can also be displayed. In addition, the pointers that point to an instance can be viewed. The data model owner can also modify the data model by adding, deleting, or editing classes and instances. In addition, the data model owner can define relationships between the objects, such as hierarchical and inheritance relationships. Other types of relationships include, for example, constraints on the number of instances of a particular object type that can be associated with a given instance of another object type. For example, the data model owner can specify that only one instance of an Engine object can be associated with a given instance of a Car object. Furthermore, the data model owner can define access rights to the data, view the data, and export the data to other users.

0080The product manager also assumes some responsibility for managing the data in the database. Accordingly, the product manager can generate reports that summarize the data in the database and view the data contained in a selected object or all of the data in the database. In addition, the product manager can import data from various sources and export data to various destinations.

0081The product expert also assumes some responsibility for managing the data. Accordingly, the product expert can generate reports that summarize the contents of the database and that list all occurrences of an instance in the database. The product expert can also import data from various sources and view the data contained in a selected object. Alternatively, the product expert can view all of the data in the database. In addition, the product expert can modify the data, for example, to keep the data up to date. For example, the product expert can add, delete, or edit pointers and rules that represent relationship between the data. The system also recognizes a data entry clerk, who can also view and modify the data. Both the product expert and the data entry clerk can modify data of many types, including, e.g., floats, double-precision values, short and long integers, text, descriptions, real values, and Boolean values. In addition, the product expert can modify string expressions and calculations attributes.

0082By recognizing different types of users with different access rights defined on an instance basis, the system can ensure that each type of user can perform the tasks assigned to him or her, while maintaining database security. The risk of compromising the integrity of a centralized database is thereby reduced. Appendix A contains a listing of various example objects that can be used to implement the present invention. The various embodiments described above are provided by way of illustration only and should not be construed to limit the invention. For example, the particular user interfaces described above and depicted in the figures are not intended to limit the scope of the present invention. Those skilled in the art will readily recognize various modifications and changes that may be made to the present invention without strictly following the example embodiments and applications illustrated and described herein, and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.