Method and computer system for providing input, analysis, and output capability for multidimensional information

• US 6,684,216 B1
• Filed: 09/25/2000
• Issued: 01/27/2004
• Est. Priority Date: 09/29/1999
• Status: Expired due to Fees

• Current Assignee: Katherine Duliba
• Original Assignee: Katherine A. Duliba
• Inventors: Dorsey, Paul R., Duliba, Katherine A.
• Primary Examiner(s): Amsbury, Wayne
• Assistant Examiner(s): GODDARD, BRIAN D
• Application Number:
  US09/668,136
• Time in Patent Office: 1,219 Days
• Field of Search: 707/102, 707/104.1
• US Class Current: 707/694
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: Y10S 707/954 Relational
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A method includes creating and storing in various relational database tables: a biz metrix, by articulating variables that will appear on the metrix; biz metrix components; structure or relationships of the biz metrix; data elements that will appear on the metrix, including a text field storing a rule; defining the rule; creating and storing the metrix itself; metrix details; and potential types of subjects of the biz metrix.

Claims

1. A method of database design comprising:

defining and storing in a first relational database table a domain of information by specifying a name of the domain, a data type, a description, a default, a SQL statement, a valid rule, a minimum, a maximum, a precision, and a length;

defining and storing in a second relational database table a list of valid values for the domain, by specifying one of;

a numeric value, a text value, and a date value;

defining and storing in a third relational database table virtual tables by specifying a name of the virtual table, a SQL select clause, a SQL from clause, a SQL where clause, a description, and an owner;

defining, in a COB_Table_Dtl relational database table, details of the third relational database table, by specifying as attributes a first group of tables that have a higher level of interaction with he other tables in the database, as compared to a second group of tables;

defining and storing in a fourth relational database table, virtual attributes, by specifying a code of the virtual attribute, and a data type;

defining and storing in a fifth relational database table, a value of a particular virtual attribute, by specifying one of;

a numeric value, a text value, and a date value;

defining and storing in a sixth relational database table, rules associated with customization and extension of the database, by specifying at least one party associated with at least one specific object;

defining and storing in a seventh relational database table, details of the rules, by specifying at least one party is associated with at least one virtual attribute, a valid variable rule, and a minimum and maximum number of times each of the details of the rules can appear; and

defining and storing in an eighth relational database table, a function, by specifying a name of the function, its syntax, and a description.

2. A method comprising:

defining and storing in a first relational database table a domain of information;

defining and storing in a second relational database table a list of valid values for the domain;

defining and storing in a third relational database table virtual tables;

defining, in a fourth relational database table, details of the third relational database table;

defining and storing in a fifth relational database table, virtual attributes;

defining and storing in a sixth relational database table, a value of a particular virtual attribute;

defining and storing in a seventh relational database table, rules associated with customization and extension of a database;

defining and storing in an eighth relational database table, details of the rules; and

defining and storing in a ninth relational database table, a function.

3. A method as in claim 2 wherein the defining and storing in the first relational database table comprises:

specifying at least one of a name of the domain, a data type, a description, a default, a SQL statement, a valid rule, a minimum, a maximum, a precision, and a length.

4. A method as in claim 2 wherein the defining and storing in the second relational database table comprises:

specifying one of;

a numeric value, a text value, and a date value.

5. A method as in claim 2 wherein the defining and storing in the third relational database table comprises:

specifying at least one of a name of the virtual table, a SQL select clause, a SQL from clause, a SQL where clause, a description, and an owner.

6. A method as in claim 2 wherein the defining and storing in the fourth relational database table comprises:

specifying as attributes a first group of tables that have a higher level of interaction with other tables in the database, as compared to a second group of tables.

7. A method as in claim 2 wherein the defining and storing in the fifth relational database table comprises:

specifying a code of the virtual attribute, and a data type.

8. A method as in claim 2 wherein the defining and storing in the sixth relational database table comprises:

specifying one of;

a numeric value, a text value, and a date value.

9. A method as in claim 2 wherein the defining and storing in the seventh relational database table comprises:

specifying at least one party is associated with at least one specific object.

10. A method as in claim 2 wherein the defining and storing in the eighth relational database table comprises:

specifying at least one party is associated with at least one virtual attribute, a valid variable rule, and a minimum and maximum number of times each of the details of the rules can appear.

11. A method as in claim 2 wherein the defining and storing in the ninth relational database table comprises:

specifying a name of the function, its syntax, and a description.

12. A method for defining, generating, storing and displaying complex information comprising:

creating and storing in a first relational database table a biz metrix by first articulating variables that will appear on the biz metrix, by specifying the variables'"'"' names, data types, descriptions, domains, and SQL queries appropriate to selecting valid values for the variables;

creating and storing in a second relational database table the biz metrix components, by specifying their types, frequencies, names, and descriptions;

defining and storing in a third relational database table the structure or relationships of the biz metrix, by specifying the names of one or more subordinate biz metrix structure, and the maximum and minimum number of child metrix objects;

defining and storing in a fourth relational database table data elements that will appear on a metrix, by specifying a particular biz metrix and biz metrix variable, and biz metrix details'"'"' types, label, default value, a Boolean value for whether or not the data element is required, and a text field storing a rule;

defining the rule, by specifying whether it is an arithmetic or string or time/date or conversion or custom function, and by specifying the operator, as appropriate to the type of rule;

creating and storing in a fifth relational database table the metrix, by specifying that it is to be an instantiation of a particular biz metrix, a superordinate or parent metrix, a COB table and COB link ID or CD, and the metrix, frequencies, statuses, document dates, calculation dates, observation start dates, the observation end dates, and a description;

defining and storing in a sixth relational database table the metrix details, by specifying the particular metrix, the particular biz metrix variable, the type of metrix detail, the text value or numeric value or date value of the metrix detail, a Boolean value for whether or not the metrix detail is required, and a label for the metrix detail; and

defining and storing in a seventh relational database table potential types of parties of the biz metrix, by specifying the names of biz metrix subjects.

13. A method for entering, storing, processing, and displaying information about a party, the method comprising:

defining information about the party by specifying the name of the party, a value indicating whether or not the party is a person, a start date of the party, and an end date of the party;

storing the information about the party in a first relational database table;

defining different roles or relationships among the parties, by specifying additional information including a type of party role, a type of relationship, a name of a superordinate party, and a start date and end date of these associations;

storing the additional information about the party in a second relational database table; and

defining and storing, in a third relational database table, rules that govern the parties'"'"' roles and relationships, by specifying the superordinate party, a subordinate party, types of the parties'"'"' relationships, and a start date and end date of these relationships.