Abstract:
A computer-implemented method of creating and editing a document containing one or more terms. A knowledge base containing a set of terms with one or more predefined properties including part-of properties relating terms to each other is provided. The one or more predefined properties associated with a user-selected term are identified. Constraints are imposed on user manipulation of the document with respect to the user-selected term in accordance with the one or more identified predefined properties associated with the user-selected term. In a particular implementation, a method of creating and editing a financial document containing one or more financial terms is described. The tasks of creating and editing documents are simplified by the separation of the presentation of information contained in a document from underlying representation of calculations and interrelationships. A user may readily manipulate the content and appearance of domain-specific (e.g., financial) analyses, without having repeatedly to define and verify calculations. A user may define and customize standard reports with a simple palette of powerful editing tools that implement and maintain the semantics of the items in a document. This frees the user from having to handle the underlying references directly, allowing the user to focus instead upon concepts and contexts contained within the document.

Description:
BACKGROUND 
     The invention relates to creating and editing computer-readable electronic documents, and more particularly to creating and editing domain-specific documents including a report, such as a financial statement. 
     Reports can be used to summarize, organize, calculate, and analyze data. For example, financial data or sales data can be summarized by one or more financial or sales reports that represent different aspects of the condition or operation of a business entity. To create a financial statement or a sales report, it is often useful to calculate totals, subtotals, averages, counts, or other summaries for different aspects of a business (e.g., total sales for each relevant region, or total sales across regions). Electronic reports are particularly useful because they can be automatically updated when new or different information becomes available. For example, a spreadsheet program such as Microsoft® Excel can be used to create a report in the form of an electronic spreadsheet that consists of a matrix of rows and columns for displaying values and text and for calculating values automatically based upon user-defined formulas. An electronic spreadsheet can also be formatted to vary the presentation of information contained within the report. To simplify the creation of an electronic spreadsheet, a spreadsheet program can automatically enter certain information (e.g., the same information, or an incremental series, such as numerals, ordinals, dates, and months) into a range of cells based upon a user&#39;s initial entry of information into one or more cells. A user can also insert a formula into a cell for calculating values on the spreadsheet. Values can be entered directly into a formula, or the values in other cells can be used in a formula by including references to the other cells in the formula. Spreadsheet programs typically include many built-in formulas that can be used alone or in combination with other formulas. 
     SUMMARY 
     In one aspect, the invention features a computer-implemented method of creating and editing a document containing one or more terms, comprising: providing a knowledge base containing a set of terms with one or more predefined properties including part-of properties relating terms to each other; identifying the one or more predefined properties associated with a user-selected term; and imposing constraints on user manipulation of the document with respect to the user-selected term in accordance with the one or more identified predefined properties associated with the user-selected term. 
     The document may be changed in accordance with the one or more properties of the user-selected term in response to a user action calling for a change in the document relating to the user-selected term. A user-selected term from the knowledge base may be inserted into the document. The user-selected term may be a section header, and one or more terms defined by the knowledge base as being part of a section labeled with the section header may be automatically inserted into the document. The user-selected term may be a calculated term, and one or more terms defined by the knowledge base as being needed to derive a value for the calculated term may be automatically inserted into the document. A predefined document comprising one or more sections defined by the knowledge base as being part of the predefined document may be created. The one or more sections may comprise one or more terms defined by the knowledge base as being part of the one or more sections of predefined document. A stored representation of the document may be maintained, including a record of user actions changing one or more properties of terms contained within the document from the definitions of the terms contained in the knowledge base. One or more terms contained within the knowledge base to be selected by a user for entry into the document may be displayed. These terms may include predefined document terms and predefined section terms. The terms that are displayed may be hierarchically arranged wherein, upon selection of a predefined document term, one or more predefined section terms defined by the knowledge base as being part of the predefined document are displayed and, upon selection of a predefined section term, one or more terms defined by the knowledge base as being part of the predefined section are displayed. 
     In another aspect, the invention features a method of creating and editing a financial document containing one or more final terms, comprising: opening an electronic spreadsheet; providing a financial knowledge base containing a set of financial terms with one or more predefined properties including part-of properties relating financial terms to each other; identifying the one or more predefined properties associated with a user-selected financial term; and imposing constraints on user manipulation of the financial document with respect to the user-selected financial term in accordance with the one or more identified predefined properties associated with the user-selected financial term. 
     Embodiments may include one or more of the following features. 
     One or more tools may be provided for manipulating terms contained in the electronic spreadsheet. The consistency of the manipulated terms may be maintained in accordance with the properties associated with the manipulated terms. The financial document may be changed in accordance with the one or more properties of the user-selected financial term in response to a user action calling for a change in the document relating to the user-selected financial term. 
     A user-selected financial term may be inserted from the financial knowledge base into the spreadsheet. One or more financial terms defined by the financial knowledge base as being related to the user-selected financial term may be automatically inserted into the electronic spreadsheet. The user-selected financial term may be a financial section header and the related financial terms may be defined by the financial knowledge base as being part of a financial section labeled with the financial section header. The user-selected financial term may be a calculated term defined by the financial knowledge base as being associated with a value derived from values associated with the related financial terms. The user-selected calculated term may be converted into an input term that is associated with a value obtained from an input sheet. The input term may be re-converted back into the calculated term defined by the financial knowledge base as being associated with a value derived from values associated with the related financial terms. A property associated with the user-selected term may be changed so that the user-selected term is assigned a value of zero. The user-selected financial term may be a total expression and the related financial terms may be defined by the knowledge base as being inputs to a spreadsheet formula associated with the user-selected financial term for deriving a value for the total expression. 
     A user-defined alias may be substituted for a predefined financial term name defined in the financial knowledge base, and alias for the inserted financial term may be recorded in response to user action. The user-selected financial term may be duplicated in response to a user action, wherein a user-defined duplicate financial term is inserted into the spreadsheet and the sum of the duplicated financial term and the user-defined duplicate financial term is substituted in spreadsheet equations where the duplicated financial term appeared before being duplicated. The user-selected financial term may be itemized in response to a user action, wherein the user-selected financial term is converted into a total expression associated with a value derived from one or more user-defined financial terms. The one or more user-defined financial terms from which the value associated with the itemized financial is derived may be inserted into the document. 
     A user may be prevented from deleting certain financial terms from the spreadsheet. A user may be prevented from deleting from the spreadsheet a calculated financial term used in a spreadsheet formula associated with another financial term in the spreadsheet. A user may be prevented from deleting from the spreadsheet an itemized financial term associated with a spreadsheet formula summing together one or more user-defined itemization financial terms in the spreadsheet. 
     A stored representation of the spreadsheet may be maintained, including a record of user actions changing one or more predefined properties of terms inserted into the spreadsheet for the definitions of the terms contained in the knowledge base. The stored representation of the spreadsheet may be updated in response to a user action deleting a term from the spreadsheet. An itemization count associated with an itemized financial term may be updated in response to a deletion of an itemization of the itemized financial term. A duplicate count associated with a duplicated financial term may be updated in response to a deletion of a duplicate of the duplicated financial term. 
     A calculated financial term, which has no direct dependents on the spreadsheet, may be deleted in response to a user action, and financial terms referenced in a spreadsheet formula for the deleted calculated term may be automatically deleted. A calculated term, which has no direct dependents the spreadsheet, may be referenced in the spreadsheet formula for the deleted calculated term, and the referenced calculated term and financial terms referenced in a spreadsheet formula for the referenced calculated term may be automatically deleted from the spreadsheet. 
     A financial term may be characterized as either an input term or a calculated term. A user-requested change in the predefined status property from an input term to a calculated term or from a calculated term to an input term may be recorded. 
     A second electronic spreadsheet may be opened, and all of the financial terms needed to populate the first spreadsheet with values may be automatically inserted into the second spreadsheet. Financial terms not needed to populate the first spreadsheet may be automatically deleted as a result of user changes to the first spreadsheet. The second spreadsheet may be automatically populated with values obtained from a database. 
     The spreadsheet may be populated with formulas for deriving values for financial terms contained in the spreadsheet. Predefined formulas for calculated terms may be obtained from the financial knowledge base. User-defined aliases for one or more terms appearing in the spreadsheet may be substituted into the predefined formulas obtained from the financial knowledge base. The properties associated with one or more terms contained within the electronic spreadsheet may be displayed. 
     In another aspect, the invention features a method of creating and editing a financial document, comprising: opening first and second electronic spreadsheets; inserting into the first spreadsheet one or more financial terms contained in a financial knowledge base defining one or more properties of the financial terms; and inserting into the second spreadsheet all of the financial terms needed to populate the first spreadsheet with values. 
     Financial terms not needed to populate the first spreadsheet may be deleted from the second spreadsheet as a result of user changes to the first spreadsheet. The second spreadsheet may be automatically populated with values obtained from a database. The first spreadsheet may be populated with formulas for deriving values for financial terms contained in the spreadsheet. Predefined formulas for calculated terms appearing in the first spreadsheet may be obtained from the financial knowledge base. 
     In yet another aspect, the invention features a method of creating and editing a financial document, comprising: opening an electronic spreadsheet; defining a terms area of the spreadsheet for displaying financial terms; defining a values area of the spreadsheet for displaying values associated with the financial terms; inserting into the terms area of the spreadsheet one or more financial terms in response to one or more user actions; identifying one or more properties associated with financial terms inserted into the terms area as defined in a financial knowledge base containing predefined relationships between financial terms; and populating the values area of the spreadsheet with values in accordance with the identified properties of the financial terms inserted into the terms area of the spreadsheet. 
     The invention also features a method of creating and editing a financial document, comprising: opening an electronic spreadsheet with an electronic spreadsheet program; providing a financial knowledge base defining relationships between financial terms each having one or more predefined properties; providing a financial document editor comprising an interface between the electronic spreadsheet program and the financial knowledge base; and providing a graphical user interface for receiving user actions and displaying a mockup financial document superimposed on the electronic spreadsheet in response to user actions. 
     The electronic spreadsheet may be opened with a Microsoft® Excel spreadsheet program. Changes made to the mockup financial document may be recorded. The electronic spreadsheet may be closed. A second electronic spreadsheet may be opened. The mockup financial document may be superimposed on the second electronic spreadsheet based upon the record of changes to the mockup financial document. The mockup financial statement superimposed on the second electronic spreadsheet may be changed in accordance with the financial term properties and relationships defined in the financial knowledge base. 
     In another aspect, the invention features a method of creating and editing financial documents, comprising: opening a workbook comprising one or more electronic spreadsheets; providing a financial knowledge base containing financial terms with predefined properties; inserting into the workbook two instances of a financial term from the financial knowledge base; and maintaining semantic consistency of the financial term inserted into the workbook. 
     Semantic consistency may be maintained by creating a reference from one instance of the financial term to the other instance of the financial term. The workbook may comprise a first and a second electronic spreadsheet, and one instance of the financial term may be inserted into the first electronic spreadsheet and the other instance of the financial term may be inserted into any of the electronic spreadsheets of the workbook. A financial term inserted into the first electronic spreadsheet may be duplicated in response to a user action, wherein a user-defined duplicate financial term is inserted into the first electronic spreadsheet. Semantic consistency may be maintained by substituting the sum of the duplicated financial term and the user-defined duplicate financial term in spreadsheet equations where the duplicated financial term appeared on the first and second electronic spreadsheets before being duplicated. A financial term inserted into the first electronic spreadsheet may be itemized in response to a user action and one or more user-defined itemizations of the itemized term may be inserted into the electronic spreadsheet, wherein the user-selected financial term is converted into a total expression with a value derived from the sum of the one or more user-defined itemizations. Semantic consistency may be maintained by substituting the sum of the one or more user-defined itemizations of the itemized term in spreadsheet equations when the itemized financial term appeared on the first and second electronic spreadsheets before being itemized. The first and second electronic spreadsheets may contain a calculated term having a value derived from a formula defined in the financial knowledge base, and semantic consistency is maintained by: inserting into the first electronic spreadsheet the formula for the calculated term to derive the value for the calculated term; and inserting into any of the electronic spreadsheets of the workbook a reference to the value derived for the calculated term on the first electronic spreadsheet. 
     The invention may be implemented as one or more computer programs, program modules, and computer-readable data that are stored on computer-readable media and that have instructions for causing a processor to perform the actions described. 
     Among the advantages of the invention are the following. The tasks of creating and editing documents are simplified by the separation of the presentation of information contained in a document from underlying representation of calculations and interrelationships. A user may readily manipulate the content and appearance of domain-specific (e.g., financial) analyses, without having repeatedly to define and verify calculations. A user may define and customize standard reports with a simple palette of powerful editing tools that implement and maintain the semantics of the items in a document. This frees the user from having to handle the underlying references directly, allowing the user to focus instead upon concepts and contexts contained within the document. For financial reports, a component library of standard financial concepts and definitions--including definitions of financial statements, terms, formulas, and projection operations--allows users to manipulate the content and appearance of financial analyses without repeatedly having to define and verify calculations. An input sheet on which input terms are collected provides a highly-useful perspective from which a user may view the data obtained from a database and perform what-if analyses. The input sheet simplifies creation and maintenance of a report using information from a database. The input sheet also provides a user-friendly interface with one more data warehouses. 
     Other features and advantages will become apparent from the following description, including the claims. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIG. 1 is a block diagram of a system for creating and editing a financial statement. 
     FIG. 2 is a diagrammatic view of a financial statement as displayed to a user. 
     FIG. 2A is a diagrammatic view of an example of a financial workbook, which includes an income statement, a balance sheet statement, a cash flow statement, and a ratio statement. 
     FIG. 2B is a diagrammatic view of an input statement for the financial workbook of FIG. 2A. 
     FIG. 3 is a flow diagram of a method by which a user operates the system of FIG. 1 to create and edit a financial statement. 
     FIG. 3A is a flow diagram of an initialization method used in creating and editing a financial statement. 
     FIG. 3B is a flow diagram of a method of creating a new financial statement. 
     FIG. 3C is a diagrammatic view of a three-pane browser for viewing terms defined in a financial dictionary. 
     FIG. 4 is a diagrammatic view of the section headings and associated terms appearing in an income statement. 
     FIG. 5 is a flow diagram of a method of creating a section in a financial statement. 
     FIG. 6 is a diagrammatic view of a menu of financial statement editing tools. 
     FIG. 7 is a flow diagram of a method of inserting a term into a financial statement. 
     FIG. 8 is a flow diagram of a method of creating an alias for a term appearing in a financial statement. 
     FIG. 9 is a flow diagram of a method of duplicating a row in a financial statement. 
     FIG. 10 is a flow diagram of a method of itemizing a row in a financial statement. 
     FIG. 11 is a flow diagram of a method of deleting a row in a financial statement. 
     FIG. 12 is a diagrammatic view of an input sheet for the income statement of FIG. 4. 
     FIG. 13 is a flow diagram of a method of updating an input statement. 
     FIGS. 13A and 13B are flow diagrams of a method of copying input terms from a financial statement into an input statement. 
     FIGS. 13C and 13D are flow diagrams of a method of defining formulas on a financial statement. 
    
    
     DETAILED DESCRIPTION 
     Referring to FIG. 1, a system 22 for creating and editing a financial statement report is implemented as a group of computer programs, program modules, and computer-readable data that are stored on computer-readable media and that operate to cause a computer to perform the actions described in this specification. System 22 includes a financial statement editor 24 that has a financial knowledge base 23 and editor objects and methods 25. The financial knowledge base 23 includes a financial dictionary of terms representing financial concepts with predefined properties and interrelationships. The editor objects and methods 25 control the operation of an electronic spreadsheet program 26 in response to user actions directed to the editor objects and methods 25 through a user interface 28, such as a graphical user interface operated under control of system 22. Statement editor 24 embodies and manifests a general financial model of possible contexts, parameters and values, as well as hierarchies and rules relating them. A user may provide overrides 29 to change one or more aspects of financial statement editor 24. In operation, system 22 separates the presentation of financial data and analyses from the underlying data and numeric calculations. Using system 22, a user indicates the financial model elements to be contained within a financial statement. In response, system 22 manages the conceptual and numeric relationships among the selected elements, indicates what information is needed to produce the statement--which information may be entered by hand or acquired under program control from computer-readable source such as a financial database 30--and ensures that this information is used and calculated consistently within one or more financial statements. Information in database 30 might be stored in the form of an electronic spreadsheet, a relational database, or some other electronic form. 
     In the particular embodiment being described, system 22 is implemented as a computer program running on a personal computer. Spreadsheet program 26 is the Microsoft® Office 97 version of Excel (&#34;Excel&#34;). Financial statement editor 24 is implemented as an add-in to Excel and includes an object-oriented program module that is written in the Microsoft® Visual Basic® for Applications programming language (version 5.0). In particular, financial statement editor 24 includes a financial knowledge base 23; maintenance routines for verifying and organizing financial knowledge base 23; and editing objects and methods 25. The financial knowledge base 23 includes definitions of financial terms representing financial concepts. Editing objects and methods 25 set up menus and tool bars, open and manipulate a project workbook, provide dialogue sheets, provide a browser for displaying the contents of financial knowledge base 23, represent the contents of one or more financial statements, and carry out editing functions. In this particular implementation, editor objects and methods 25 invoke Excel objects and methods. Editor objects and methods 25 also access financial knowledge base 23 to provide editing menus and editing tools. Editor objects and methods 25 may be invoked when a user applies one of the editing tools, as described below. In this embodiment, financial database 30 is in the form of an electronic Excel spreadsheet. User interface 28 provides an Excel spreadsheet and other user interface elements that are displayed on a computer display device (such as a monitor or liquid crystal display screen). User interface 28 responds to user actions such as typing keys on a computer keyboard, moving a mouse or other pointing device to move a cursor across the computer display, or activating a computer mouse button. System 22 stores in computer memory a project workbook representing a financial project. A project workbook contains one or more financial statements, an input sheet (which is a financial statement spreadsheet used for collect input values), a hidden status spreadsheet, saved objects corresponding to financial statements, and macros for initializing links to spreadsheet program 26 and for saving the financial statement objects when the corresponding Excel spreadsheets are opened and closed. 
     As shown in FIG. 2, user interface 28 displays a mockup financial statement. The financial statement spreadsheet is referred to as a &#34;mockup&#34; because it is being created and edited. The mockup shows the current appearance of the financial statement so that a user can readily see how an editing operation changes the appearance of the financial statement. User interface 28 shows a statement name area 32 that identifies the kind of statement being represented, a project name area 34 that identifies the name of the project in which the financial statement is contained, a time periods area 36 that identifies the time periods covered by the financial statement, a user-modifiable terms area 38 that represents financial concepts contained within the financial statement, and a values area 40 that can be automatically populated with spreadsheet formulas and/or values corresponding to the associated financial terms. The values in values area 40 are copied from an input statement (described below) which obtains values from the user, from database 30, or from both of these sources. Financial statement editor 24 prevents a user from editing cells within values area 40 that are automatically populated with spreadsheet formulas and/or values. A user can, however, create additional rows and columns that can incorporate calculations and data contained within other spreadsheet cells. 
     Referring to FIGS. 2A and 2B, a computer-readable project workbook 42 includes one or more user-specified financial statements, such as an income statement 44, a balance sheet statement 46, a cash flow statement 48, and a ratio statement 50, each representing a different aspect of a financial project over the selected time range. Project workbook 42 may also include a customized financial statement containing one or more user-selected financial sections and terms. After a user has specified the contents of any of the financial statements in workbook 42, system 22 automatically generates an input statement spreadsheet 52 which identifies all of the information (inputs) needed to populate the financial statements with formulas and values. Input statement 52 includes a project name area 54, an area 56 that identifies the statement as an input statement, an area 58 that contains the time periods covered by the financial statements of project workbook 42, a terms area 60, and an inputs (values) area 62. Some of the terms contained in terms area 60 may not be displayed in any of the financial statements but are needed to calculate the values associated with the terms that actually appear on one or more of the financial statements in workbook 42. Input statement 52 contains only those inputs (and associated terms) needed to populate the financial statements of workbook 42; any input that is not needed is automatically removed from input statement 52 when the input statement is updated. Input values appearing on input statement 52 are color-coded to identify the source or other properties of the input values: values copied from database 30 are displayed in blue, user-supplied values that override database values are displayed in magenta, and user-supplied values that do not override database values are displayed in green. 
     Referring to FIG. 3, a user may open a previously-created project workbook that was saved in a computer memory such as a disk (step 64). The user may then edit the one or more statements in the project, as described in detail below (step 66). Alternatively, a user may create a new project (step 68). The user may then create a new statement based upon a financial statement template containing financial concepts arranged in a predefined format, or the user may open an empty statement (step 70). For example, the user may select a template for an income statement, a balance sheet statement, a ratio statement, or a cash flow statement (step 72). After selecting a template, the user may specify the time range and time periods to be displayed in the financial statement (step 74). The time periods of the mockup financial statement are represented as a finTime --  Styles object in financial statement editor 24. The user may then edit the financial statement with one or more financial statement editing tools (step 66). If the user does not select a financial statement template, the user may create a customized financial statement by specifying the time range and time periods to be displayed in the financial statement (step 74) and by creating and editing the financial statement with one or more financial statement editing tools (step 66). The user may insert financial terms in the terms area of the mockup financial statement one at a time, or the user may insert an entire financial section into the mockup financial statement. In order to populate the mockup financial statement with data, the user selects an UPDATE editing tool (described below) or selects the spreadsheet tab which corresponds to the input statement at the bottom of the project workbook interface window (step 67). System 22 creates (or updates) input statement 52 with all of the required input terms, populates input spreadsheet 52 with data from financial database 30 (if supplied), and inserts formulas that refer to this data in the mockup financial statement. 
     Referring to FIG. 3A, in response to a user&#39;s command to create a new financial statement or project (step 68; FIG. 3), system 22 initiates a new project as follows (step 80). System 22 opens a template project workbook that contains one or more Excel spreadsheets (step 82). System 22 renames and saves the workbook in a memory device, such as a computer hard disk (step 84). System 22 opens and verifies the format of financial database 30 (step 86). System 22 sets the globals for the project (step 88). System 22 then creates a new financial statement (step 90). Once the financial statement has been created, system 22 returns control to an event loop and responds to subsequent user actions (step 92). 
     Referring to FIGS. 3B and 3C, after a user has directed system 22 to create a statement, the user is prompted to supply the name of the statement (&#34;STMTNAME&#34;). System 22 then initializes statement globals (step 100). If the requested statement name corresponds to a previously saved statement, system 22 obtains from the project workbook an object (of type finStatement) which contains all of the information needed to reproduce the saved mockup financial statement (spreadsheet) and enable a user to modify the statement with the financial statement editing tools of system 22; otherwise, system 22 creates a new object (of type finStatement) for a new mockup financial statement (step 102). System 22 then opens and clears the mockup financial statement (step 104). If the time periods to be displayed in the financial statement have not been specified (step 106), system 22 invokes a time period wizard to prompt the user to supply the time periods to be displayed in the financial statement (step 108). System 22 enters a header (namely, the statement name and project name) and the specified time periods into the mockup financial statement, as shown in FIG. 2 (step 110). System 22 displays on the computer display device a three-pane financial browser 111 (FIG. 3C). The user can interact with the browser to insert into a mockup financial statement a fill financial statement, a full financial statement section, or an individual financial term. The full financial statement may be selected from a list shown in the left pane of the browser, which list may include an income statement, a balance sheet statement, a cash flow statement, or a ratio statement. A full financial statement section may be selected from a list shown in the center pane of the browser as a type of a selected full statement. An individual financial term may be selected from a list shown in the right pane of the browser as a subtype of a selected section type. A financial term may be, for example, a ratio expression, a total expression, a net expression, another compound expression, or an arithmetic expression of a specified type, such as sales, costs, income, dividends, change in retained earnings, and other types. In effect, financial browser 111 provides a three-pane hierarchical display that shows subtypes and subparts of the conceptual graph of properties stored as a table in a KBProps spreadsheet, which is described later. If the user selects a predefined, full financial statement (step 112), system 22 automatically populates the mockup financial statement with the section headings and financial terms for the selected statement according to its definition (step 114). System 22 displays a palette or menu of spreadsheet editing tools, initializes event handlers, unlocks the first column of the mockup financial statement (corresponding to financial terms area 38 in FIG. 2), and protects the mockup financial statement so that a user cannot directly edit name area 32, project name area 34, time periods area 36, or values area 40 (step 115). These areas may later be edited when the user applies to a selected area one or more of the editing tools described below. System 22 then returns control to the event loop and responds to subsequent user actions (step 92). 
     A financial statement generally has one or more financial sections, each having one or more associated financial terms. For example, income statement 44, shown in FIG. 4, was created based on a predefined income statement template in financial statement editor 24, and includes a sales section 116, a costs section 118, an income section 120, a dividends section 122, and a change in retained earnings section 124. Each of these sections includes one or more financial terms. For example, sales section 116 includes a gross sales term 126, a discounts term 128, an allowances term 130, a returns term 132, and a net sales term 134. Each term is characterized as either an input term or a calculated term. Input terms (e.g., gross sales term 126) have values that are obtained from financial database 30 or are input directly by a user. Calculated terms (e.g., net sales term 134) have values that are derived from spreadsheet formulas. For example, net sales term 134 has a value that is derived from the following spreadsheet formula: 
     
         net sales=gross sales-(discounts+allowances+returns). 
    
     The value associated with net sales term 134 therefore depends upon the values for gross sales term 126, discounts term 128, allowances term 130, and returns term 132, each of which will be referred to as a &#34;direct predecessor&#34; of net sales term 134. Gross profit term 136 has a value that is derived from a spreadsheet formula 135 that includes two direct predecessors which are calculated terms (net sales and cost of sales); the terms from which values are obtained for direct predecessor calculated terms (e.g., net sales and cost of sales) will be referred to simply as &#34;predecessors&#34; of the original calculated term (e.g., gross profit term 136). Thus, net sales term 134 and cost of sales term 137 are direct predecessors of gross profit term 136. Gross sales term 126, discounts term 128, allowances term 130, returns term 134, cost of sales cash term 138 and depreciation &amp; amortization term 140 are predecessors of gross profit term 136. Conversely, net sales term 134 is a &#34;direct dependent&#34; of gross sales term 126, discounts term 128, allowances term 130, and returns term 134. 
     Financial knowledge base 23 is stored as a matrix of terms and associated relations, which define a conceptual graph. This matrix is conveniently stored in an electronic spreadsheet called KBProps (reproduced in the attached Appendix) that is accessed by finObjects modules routines. Each term (referred to as a KBATOM) in financial knowledge base 23 is characterized by the following relations: ISA, PNAME, PARTOF, SUBPARTS, ACTUAL-FORMAT, NAME-FORMAT, LINE-FORMAT, and SECTION-HEADER. For example, net sales term 134 is characterized as follows: 
     
         ______________________________________Definition of Net Sales Term______________________________________KBATOM       Net.sub.-- SalesISA          Net.sub.-- ExpressionPNAME        Net SalesPARTOF       Sales.sub.-- SectionACTUAL-FORMULA        Gross.sub.-- Sales - (Discounts + Allowances +        Returns)NAME-FORMAT  NullLINE-FORMAT  Gray Shade______________________________________ 
    
     Referring to FIG. 5, system 22 automatically populates the mockup financial statement (FIG. 2) with financial terms corresponding to a financial statement heading (called a SecName in KBProps) as follows (step 114). System 22 invokes a lookupKB module to obtain from financial knowledge base 23 a SectionList, which is a list of one or more financial terms to enter into terms column 38 based upon the SecName (step 150). For each term (called an itemname) in the SectionList, system 22 performs the following steps (step 152). System 22 determines the type of the term from the ISA relation for the term (step 154). If the term is a section or a total expression (step 156), system 22 recursively invokes step 114 to create a section or a total expression associated with the term (step 157); otherwise, system 22 adds the term to terms column 38 (SheetFirstColumn) of the mockup financial statement spreadsheet (step 158). If the term was added by the user (step 160), system 22 automatically populates terms section 38 with any calculated terms used by the spreadsheet formula associated with the user-added term (step 162); otherwise, system 22 stores the properties of the term as a finRow object in an electronic spreadsheet that corresponds to a finStatement object (discussed in the following section). The finRow object includes references of direct predecessors and a row name reference (step 164). System 22 sets the format for the cell in which the term was added based on a predefined or default format specified to financial statement editor 24 (step 166). System 22 then returns to step 122 for the next itemname in the SectionList and repeats the above process (step 168). 
     Internal Data Structures 
     As mentioned above, a mockup financial statement is represented to a user as an electronic spreadsheet on a computer display device. System 22 also maintains an internal parallel representation of the financial statement in the form of a finStatement object that includes a finRows object and a finColumns object which respectively correspond to the terms and time periods in the mockup financial statement. A finStatement object has the following properties: 
     
         ______________________________________finStatementProperties Type     Description______________________________________Name       String   Name of spreadsheet where statement               appearsfinRows()  finRownumRows    Integer  Number of rows in this statementfinColumns()      finColumnnumColumns Integer  Number of columns in this statementIsINPUTSheet      Boolean  True if this is the input sheetTimePeriodRange      Range    Row corresponding to the time period               labelsTimeStyleSelected      Integer  Index of selected time style for this______________________________________ 
    
     A finRows object has the following properties: 
     
         ______________________________________finRow Properties        Type    Description______________________________________Name         String  Built-in financial term in                knowledge baseAlias        String  User&#39;s name for this termChangedStyle Boolean User changed the dictionary-defined                formatting style of the name or                the lineDuplicateOf  String  Existing term user duplicated to                create this rowNumDuplicates        Integer Number of duplicates user has                created of this existing termDuplicateCode        Integer Unique identifier for this duplicateItemizationOf        String  User has itemized this existing termItemizationCode        String  Unique identifier for this itemizationNumItemizations        Integer Number of itemizations user has                created of this termHidden       Boolean This row is currently hidden in the                currently displayed statementUserDefinedInput        Boolean User converted this to an input (by                editing mockup financial statement)AssumeZero   Boolean User wants to assume values are zeroDependentMadeInput        Boolean User made parent an input and hid                this predecessorHistDataSource        Integer Source of historical data (e.g., user                database)HeaderOf     String  This row is a header for the indicated                sectionCalculated   Boolean Term is calculated (not an input)                according to dictionary definitionFormat       Integer Current Style of name (e.g., bold,                italic) and line shading, spacingParent       String  finStatement namedirectPredecessors()        String  Terms directly referenced in                this item&#39;s formulasNumDirectPredecessors        Integer Number of direct                predecessorsDirectDependents()        String  Terms using this term in a formulaNumDirectDependents        Integer Number of direct dependentsRefersTo     Variant Entire row in spreadsheet (an Excel                range object)NumSecondaryRefs        Integer Number of times this term has been                clonedSecondaryReferenceOf        Range   Term this is a clone ofUserDefinedRow        Boolean Entire row is set by user (ignored by                financial statement editor)PriorYrHistory        String  Value = X for term having                X.sub.-- Prior in its formulas______________________________________ 
    
     A finRow object for an input statement includes all of the above properties, along with the following additional properties. 
     
         ______________________________________Additional Input finRowProperties   Value   Description______________________________________InputforStmts()        Integer finStatement numbers for which this                row is an inputNumInputStmts        Integer Number of statements for which this                row is an inputExclusivelyOneFstmt        Boolean Row is only an input for the                statement being processed______________________________________ 
    
     A finColumn object has the following properties. 
     
         ______________________________________finColumn Properties       Type     Description______________________________________Name        String   Defined name of the columnTime        Date     Actual date corresponding to label in                spreadsheetParent      String   finStatement nameColumnNumber       Integer  Number of column in spreadsheetLabelCell   Range    Cell corresponding to the time labelPeriodKind  String   Period of Time (e.g., year, month)Refers to   Variant  Entire column in spreadsheet______________________________________ 
    
     A finTime --  Styles object has the following properties. 
     
         ______________________________________finTime.sub.-- Styles Property        Type    Description______________________________________Name         String  Name user has defined for this viewBaseDate     Date    Date to use for &#34;this period&#34;                (generally last year)BeginDate    Date    Beginning date of period (may be                historical)EndDate      Date    Ending date of periodPeriodunit   String  Duration of one period (e.g., year)numPeriods   Integer Number of period labels in the range______________________________________ 
    
     Financial Statement Editing Tools 
     Referring to FIG. 6, system 22 includes a menu 167 of financial statement editing tools which allow the user to edit a mockup financial statement. A user can insert a term from statement editor 24 into the financial statement by selecting an INSERT TERM editing tool 170. A user can create an alias for a term by selecting an ALIAS editing tool 171 to change the displayed name of a term. System 22 maintains the integrity of the financial statement by preserving the original meaning of the term as specified in financial statement editor 24. 
     A user can duplicate a term by selecting a DUPLICATE editing tool 172. This breaks up a single input term into two separate input terms. System 22 maintains the integrity of the financial statement by replacing each instance of the original input term in a spreadsheet formula with the sum of the two new input terms. 
     A user can itemize a term by selecting an ITEMIZE editing tool 173. This breaks up a term into one or more subitems. System 22 inserts into the financial statement a new total term whose value is the sum of the subitems. 
     A user can convert a calculated term into an input term by selecting a CONVERT TO INPUT editing tool 174, which obtains the term&#39;s value from financial database 30 or directly from the user. A user can also can re-convert a converted input term back to a calculated term by selecting a CONVERT TO CALCULATED editing tool 175. A user can direct system 22 to convert a calculated term to an input term and set the term&#39;s value to zero when populating the mockup financial statement with values by selecting an ASSUME ZERO editing tool 176. 
     A user can hide a term by selecting a HIDE TERM editing tool 169. A user can direct system 22 to show hidden terms (e.g., hidden predecessors of a calculated term that are automatically added to the mockup financial statement by system 22) by selecting a SHOW HIDDEN editing tool 177. A user can delete a term by selecting a DELETE TERM editing tool 178. 
     A user can toggle headings so that the user can see the grids and conventional alphanumeric headers for the matrix of rows and columns by selecting a HEADINGS editing tool 179. A user can change the format of the mockup financial statement, for example, by changing the appearance (style) of a row or by moving a row to a different location by selecting one or more FORMATTING TOOLS 180. 
     A user can also direct system 22 to report the properties of a term by selecting an EXPLAIN TERM tool 181. 
     Once a mockup financial statement has been created, a user can direct system 22 to create (or update) an input statement and populate the mockup financial statement with data and spreadsheet equations by selecting an UPDATE editing tool 182. 
     INSERT TERM 
     System 22 allows a user to insert a financial term (which may be an entire financial section) into the mockup financial statement. System 22 maintains the integrity of the financial statement by automatically inserting calculated terms that are predecessors of the inserted term; the automatically inserted terms, however, are hidden in the mockup financial statement. 
     Referring to FIG. 7, a financial term may be inserted into a mockup financial statement as follows (step 183). A user positions the cursor in an open cell of terms column 38 and activates INSERT TERM editing tool 170 from the financial statement editing tools menu. System 22 displays three-pane browser 111 (FIG. 3C) and the user uses it to select the term to be added (e.g., gross profit). System 22 verifies that the term is not already in the mockup statement (step 184). If the selected term is a section (e.g., costs) or a total expression as determined from the ISA relation for the term (step 185), system 22 creates a section for the term in accordance with the definition contained in financial knowledge base 23 (step 114; FIG. 5); otherwise, system 22 inserts the term (e.g., gross profit) in terms section 38 (step 186). System 22 automatically inserts into terms section 38 each of the calculated predecessor terms (e.g., net sales and cost of sales) that appears in the spreadsheet formula associated with the added term, if any (step 188). After the calculated terms are added, system 22 hides them so that they are not displayed on the mockup financial statement. System 22 also sets the DependentTo property of the predecessor terms (step 190). System 22 activates the cell containing the added term and protects the mockup financial statement (step 192). System 22 then returns control to the event loop and responds to subsequent user actions (step 92). 
     ALIAS 
     System 22 allows the user to change the name of a financial term appearing in the mockup financial statement, while maintaining the original meaning of the term as specified in financial statement editor 24. 
     Referring to FIG. 8, an alias for a term may be created as follows (step 200). A user positions a cursor in the cell of the term to receive the alias and selects ALIAS editing tool 171 from the editing tools menu. System 22 highlights the term name and allows the user to replace the term name with an alias (step 204). The user may alternatively type over the displayed name. System 22 records the alias in the alias property section of the associated finRow object (step 206). When the user updates the mockup financial statement, system 22 displays the user-defined alias wherever the original term appears in the mockup financial statement, including the input spreadsheet and the formulas in which the term is a direct predecessor, but not in financial knowledge base 23 in three-pane browser 111 (FIG. 3C). System 22 then returns control to the event loop and responds to subsequent user actions (step 92). 
     DUPLICATE 
     System 22 allows the user to create and rename multiple copies of an input term so that multiple inputs that should be summed together in one or more spreadsheet formulas can be separately displayed in the mockup financial statement. System 22 maintains the integrity of the financial statement by summing the copied terms in the spreadsheet formulas that are dependents of the term that was originally duplicated. 
     Referring to FIG. 9, a user can break up an input term into two separate input terms by duplicating the row containing the term. For example, a user can break up Returns term 132 into &#34;European Returns&#34; and &#34;U.S. Returns&#34; by positioning the cursor in a cell containing the Returns term and selecting DUPLICATE editing tool 172 (step 210). If the term to be duplicated is not an input term (default input or user-defined input) (step 212), system 22 returns control to the event loop and responds to subsequent user actions (step 92)--i.e., system 22 does not allow a user to duplicate a calculated term, an itemized term or an itemization. If the term is an input term and the term is not a duplicate of a another term (step 214), system 22 inserts into the mockup financial statement a row with a label built from the duplicated term and a unique identifier suffix (e.g., &#34;Returns1&#34;) and creates a corresponding finRow object pointing back to the original source term (e.g., the DuplicateOf property is set to Returns) (step 216). System 22 also allows the user to set an alias for the inserted term (e.g., to change &#34;Returns1&#34; to &#34;European Returns&#34;) (step 216). If the user selects for duplication an already duplicated term (e.g., Returns1), system 22 looks up the source term (e.g., Returns) (step 218) and duplicates the source term (step 216). After a duplicate term has been created, system 22 returns control to the event loop and responds to subsequent user actions (step 92). 
     If an input term is duplicated on one statement, wherever that term is referenced in formulas on other statements, the sum of the duplicates (e.g., Returns+Returns1) is used. The references in the other statements become secondary references by virtue of the duplication in the one statement. Thus, a duplicated input term is treated on other statements exactly as it is treated on the statement in which it is duplicated. System 22 does not allow a user to duplicate a secondary reference. 
     ITEMIZE 
     System 22 allows the user to define a term as a sum of one or more user-defined inputs by itemizing the term. A term that is itemized will be referred to as an &#34;itemized term&#34; and the one or more user-defined inputs that are summed to obtain the value of the itemized term will be referred to as &#34;itemizations.&#34; 
     Referring to FIG. 10, a user can itemize an input term to create a total term (e.g., TotalReturns) which represents the sum of two or more user-defined input terms (e.g., European Returns+U.S. Returns) by selecting ITEMIZE editing tool 173 from the financial statement editing tools menu when the cursor is positioned on the term to be itemized (e.g., Returns) (step 220). If the term to be itemized is not an input term (default input or user-defined input) (step 222), system 22 returns control to the event loop and responds to subsequent user actions (step 92)--i.e., system 22 does not allow a user to itemize a calculated term or a duplicated term. If the term is an input and the term is not an itemization of another term (step 224), system 22 inserts into the mockup financial statement a row with the same label as the itemized term with a unique identifier attached (e.g., &#34;Returns1&#34;) and creates a corresponding finRow object pointing back to the original source term (i.e., the ItemizationOf property is set to &#34;Returns&#34;) (step 226). System 22 also allows the user to set an alias of the itemized term (e.g., to change &#34;Returns1&#34; to &#34;European Returns&#34;) (step 226). If the user itemizes an itemized term (e.g., Returns1), system 22 looks up the source term (step 228) and itemizes the source term (step 226). If the source term (e.g., Returns) has not been renamed (step 230), system 22 changes the term&#39;s label by prepending the word &#34;Total&#34; to the original label (e.g., to yield &#34;TotalReturns&#34;) (step 232). System 22 then returns control to the event loop and responds to subsequent user actions (step 92). 
     If an input term (e.g., Returns) is itemized on one financial statement in a project workbook, the total term (e.g., TotalReturns) is referenced wherever the original term (e.g., Returns) is referenced on other financial statements (either as an inserted term or in a formula) in the workbook. Thus, an itemized term is treated on other financial statements exactly as it is treated on the statement in which it is itemized. System 22 does not allow the user to itemize a secondary reference. If an input term that is already duplicated or itemized on one financial statement is inserted into another financial statement, the new insertion is defined as a secondary reference in the associated finRow object and cannot itself be itemized. The original itemization on the one financial statement is defined as a primary reference and its clones on the other financial statements are secondary references to the itemization. If a calculated term on one financial statement is required by a formula on another financial statement, then a reference is made from the second financial statement to the first financial statement (i.e., the original term does not have to be copied into the second financial statement). 
     DELETE TERM 
     Referring to FIG. 11, a user can delete a row so that a term does not appear in the mockup financial statement by selecting DELETE TERM editing tool 178 from the financial statement editing tools menu when the cursor is positioned on the row to be deleted (step 240). If the row is a blank row (step 242), system 22 simply deletes the row (step 244) and returns control to the event loop and responds to subsequent user actions (step 92). If the row contains a calculated term (e.g., gross profit term 136; FIG. 4) that is not defined to be an input term (i.e., the user did not convert a previously calculated term into an input term using CONVERT TO INPUT editing tool 174) and that has direct dependents (e.g., gross profit term 136; FIG. 4) (step 246), system 22 notifies the user that calculated terms with dependents cannot be deleted (step 248) and returns control to the event loop (step 92). If the row contains an itemized term (step 250), system 22 notifies the user that itemized terms cannot be deleted (step 252) and returns control to the event loop (step 92). If the row contains an itemization (step 254), system 22 deletes the row from the mockup financial statement, deletes the corresponding finRow from the finStatement object for the mockup financial statement, reduces by one the NumItemizations property of the source term, and restores the original source name if there are no itemizations for the term (e.g., changes &#34;TotalReturns&#34; to &#34;Returns&#34;) (step 256). System 22 then returns control to the event loop and responds to subsequent user actions (step 92). 
     If the row to be deleted contains a duplicate term (step 258), system 22 deletes the row from the mockup financial statement, deletes the corresponding finRow from the finStatement object for the mockup financial statement, and reduces by one the NumDuplicates property of the source term (step 260). System 22 then returns control to the event loop and responds to subsequent user actions (step 92). If the row to be deleted contains an input term (default input or user-defined input) or a calculated term with no direct dependents (i.e., there is no other term in the mockup financial statement that depends on the term), system 22 deletes the row from the mockup financial statement (step 262). If the term is calculated from input terms, system 22 asks the user whether the input terms should also be deleted (step 268). If the user indicates that the input terms should be deleted, system 22 deletes each of the direct predecessors of the deleted calculated term (step 270). System 22 then returns control to the event loop and responds to subsequent user actions (step 92). 
     The deletion of an input term from one financial statement has no effect on the appearance of that term on other financial statements because deletion of a term from one statement indicates only that the term should not appear on that statement, not that the term is to be ignored in calculations. If the term to be deleted is a primary calculated term, system 22 converts one of the secondary references to be the primary term and all of the other references are modified to point to the converted term. Converting a calculated term to an input term and re-converting an input term back to a calculated does not affect references to the term on other financial statements because all references will still refer to the converted term and use its value. A term that is converted to input can only be hidden, not deleted. 
     HIDE TERMS 
     A user can hide a term appearing in the mockup financial statement by selecting HIDE TERM editing tool 169 when the cursor is positioned in the cell of the term to be hidden. If the cell does not contain a term, system 22 deletes the row containing the cell; otherwise, system 22 sets the Hidden property of the finRow object for the term to True. The row corresponding to this term is then not displayed on the mockup financial statement (or, later, on the completed financial statement report) because spreadsheet program 26 is configured to display only terms with Hidden property values set to False. Hidden terms cannot be duplicates or itemizations. The user may reveal a term by selecting an UNHIDE TERM editing tool, which directs system 22 to set the Hidden property of the finRow object to False. 
     A user can obtain a list of terms that are hidden in the mockup financial statement by selecting SHOW HIDDEN editing tool 177. System 22 responds by displaying a list of the names (aliases, if previously set) of the terms with Hidden properties set to True. If there are no hidden terms in the statement, system 22 displays the message, &#34;There are no hidden items in this statement.&#34; 
     CONVERT TO INPUT ASSUME ZERO, CONVERT TO CALCULATED 
     A user can convert a calculated term into an input term by selecting CONVERT TO INPUT editing tool 174. A user may also convert a calculated term into an input term and have the term&#39;s value set to zero when the financial statement is populated with values by selecting ASSUME ZERO editing tool 176. System 22 responds in either case by setting the UserDefinedInput finRow property for the term to True. A section header cannot be converted to an input. A Total term cannot be assumed to have a value of zero; the user must delete itemizations before the term can be assumed to be zero. A user can change a term from an assumed zero term to a regular input term by selecting CONVERT TO INPUT editing tool 174. 
     The user is given the option of recursively hiding the predecessors (former inputs) of a calculated term that is converted to input or assumed to be zero. If the term converted to input or assumed zero is the only dependent of a predecessor to be hidden, system 22 hides the predecessor and marks the DependentMadeInput and DependentMadeZero properties of the predecessor so that it does not appear in the input statement. 
     A user can reconvert a term converted to input or assumed to be zero back into a calculated term by selecting CONVERT TO CALCULATED editing tool 175. System 22 responds by setting the UserDefinedInput and AssumeZero finRow properties for the term to False. The user is given the option of displaying any hidden predecessors for the term converted back to calculated. In the case of an itemization, system 22 displays each of the itemizations and hides the Total term. In the case of an arbitrary dependent, system 22 recursively displays each of the predecessors and sets the DependentMadeInput and DependentAssumeZero finRow properties of the predecessors to False so that the input statement will contain the proper terms when updated. An itemization and a section header cannot be converted to be calculated terms. 
     EXPLAIN TERM, HEADINGS FORMATTING TOOLS 
     A user can view the properties of a term by selecting the EXPLAIN TERM editing tool 181. System 22 responds by displaying the stored values for each of the finRow properties for the specified term, including the definition of the term contained in financial knowledge base 23 and any user-defined properties. 
     As mentioned above, by selecting HEADINGS editing tool 179, a user can toggle the display of the mockup financial statement formatted as specified in statement editor 24 or formatted with Excel grids and conventional alphanumeric headings for the matrix of rows and columns corresponding to the financial statement. 
     By selecting one or more FORMATTING TOOLS 180, a user may, for example, move a row up, move a row down, and change the appearance of text in the financial statement (e.g., bold, italic, underline, double underline, indent, shading such as gray shading or green shading). The following table summarizes some of the editing options available to a user. 
     
         __________________________________________________________________________Editing OptionsUser Action              System Response__________________________________________________________________________Press Enter (or Return) key when cursor positioned                    Insert a new termon a blank rowType over term name      Create an aliasPress backspace key followed by Enter (or Return)                    Delete a termkeySelect search tool in financial knowledge base                    Display an alphabetical list ofdialogue                 all terms in the financial                    knowledge baseSelect statement name then pull down menu                    Add a blank row above theINSERT/Rows              first termType over statement name (automatically changes                    Replace statement namestatement tab)Use Excel&#39;s formatting tool bar (automatically                    Reformat statement name,displayed when a cell is selected in formattable                    period labels, data, andareas)                   bordersCreate a blank row before and after terms to be                    Create a new sectiongrouped, then type a section header name in the firstblank rowSelect the header for a section, then apply the Move                    Move an entire sectionUp or Move Down editing toolSelect either an Itemization TOTAL or an existing                    Create a new subitemitem, then apply the Itemization editing toolApply the Show Hidden editing tool                    Reveal hidden terms created                    when formulas are generatedType a new number over a calculated value                    Temporarily reveal the effect                    of changing a calculated value;                    the number will revert to its                    calculated value when user                    selects another cellEnter values in the input spreadsheet (user-defined                    Enter or modify input values,values appear in magenta there and in the mockup                    propagate through formulasstatement if they overwrite database values, in greenif user supplies initial values, and in blue if valuescorrespond to database values)Create a new statement or revise an existing full                    Create a statement templatestatement, then save the projectSave a project before closing, then open the saved                    Re-edit a project during a laterproject                  Excel sessionTo clone a term, insert term again on any spreadsheet                    Create a secondary reference__________________________________________________________________________ 
    
     Updating the Input Statement/Populating the Mockup Statement 
     System 22 automatically creates (or updates) the input statement when the user selects UPDATE editing tool 182 from the financial statement editing tools (FIG. 6), or selects the input statement tab located at the bottom of the project workbook window displayed on user interface 28. System 22 creates input statement 52 by collecting all of the inputs needed to populate the mockup financial statement with values. For example, as shown in FIG. 12, an input statement 300 created for income statement 44 (FIG. 4) contains all of the inputs needed to populate income statement 44 with values. The input terms are inserted into terms area 60 and the associated values (obtained from another spreadsheet, an external database, or direct user input) are located in inputs area 62 under time periods area 58. 
     System 22 first establishes a new project spreadsheet labeled &#34;INPUT&#34;, to which financial terms and values will be written. When the input spreadsheet is first created, the time range is displayed based upon the time style defined in the referenced financial statement. System 22 defines a parallel finStatement which contains pointers back to the INPUT spreadsheet and contains all of the information about these rows and columns of the INPUT spreadsheet. The INPUT spreadsheet is fully described by internal objects corresponding to the type data structure of a finStatement with its finRows, finColumns, and finCells. As explained below, once all of the inputs have been added to the INPUT spreadsheet, system 22 sets pointers from the mockup financial statement to the INPUT spreadsheet and sets the formulas for calculated terms. 
     Referring to FIG. 13, a user may update the input statement by selecting UPDATE editing tool 182 (step 308). If there have not been any changes to the mockup financial statement that affect the input statement (step 310), system 22 returns control to the event loop and responds to subsequent user actions (step 92). System 22 verifies that there are calculated terms in the mockup financial statement (step 312). System 22 opens and clears the input statement (step 314). System 22 looks up or adds a finStatement object for the input statement (step 316). System 22 automatically inserts project name 54, input statement identifier 56, and time periods captions 58 into the input statement (step 318). For each finRow associated with the mockup financial statement, system 22 performs the following steps (step 320). If the term is not a header, not a secondary reference, not a term whose dependent was converted to an input or assumed to be zero, and not itemized (step 322), system 22 copies the input term from the mockup financial statement into the input statement (step 324; FIG. 13A). In effect, step 322 screens out headers and calculated terms that are not needed in the input statement. System 22 then repeats step 322 for the next finRow associated with the mockup financial statement (step 326). System 22 deletes terms that are not needed from the input statement (step 328). System 22 inserts formulas on the mockup financial statement (step 330; FIG. 13B). System 22 then relocks the data cells, protects the sheets, displays the statement selected by the user (input statement or mockup financial statement), and displays the financial statement editing tools menu (step 332). System 22 returns control to the event loop and responds to subsequent user actions (step 92). 
     Referring to FIG. 13A, in order to copy the required input terms from the mockup financial statement to the input statement, each finRow of the mockup financial statement is processed as follows (step 324). If the term depends upon a term from a different time period (a &#34;prior expression&#34;) (step 340), system 22 extracts the source term and marks the PriorYrHistory property of the finRow object for the term (step 341). For example, the term change --  in --  deferred --  taxes, which is part of cash flow statement 48 (FIG. 2A), is defined as deferred --  taxes minus deferred --  taxes --  prior; the source term is deferred --  taxes. If the term is a calculated term (step 342), and the term is not a top level term (i.e., the term appears in a spreadsheet formula) (step 344) or a user-defined input term (step 346) and the term is not a prior expression (step 348), system 22 parses the spreadsheet formula for the term and recursively returns to step 324 for each term in the spreadsheet formula (step 349). After each of the term&#39;s inputs has been copied into the input statement, the next finRow object is processed (step 326). If the term is not calculated (step 342) and is not a top level term (step 350), system 22 determines whether the term appears in the mockup financial statement (step 352). If the term appears in the mockup financial statement, system 22 processes the next finRow object (step 326). If the term does not appear in the mockup financial statement (step 352), or if the term is a top level term (i.e, a spreadsheet formula is not currently being analyzed) (step 350), system 22 determines the DuplicateCode and the ItemizationCode properties of the finRow object for the term (step 354); these properties are used for looking up the term in the input statement. If the term is in the input statement (step 356), system 22 marks a reference to the mockup financial statement and sets a &#34;previously in sheet&#34; property for the term (step 358). If the term is not in the input statement (step 356), system 22 creates a finRow object, marks a reference to the mockup financial statement, and copies the PriorHistory property of the term (step 360). If the term is not a top level term (step 362) and is a term that was just added to the input statement in step 360 (step 364), system 22 processes the next finRow object for the mockup financial statement (step 326); if the term was not just added to the input statement in step 360 (step 364), system 22 sets the label using the PNAME relation of the term and defines the row name reference for the term (step 366). 
     Referring to FIG. 13B, if the term is a top level term (step 362, FIG. 13A) and the source term appearing in the mockup financial statement is aliased (step 368), system 22 sets the alias property and label property in the finRow object for the term and defines the row name reference (step 370). If the term appearing in the mockup financial statement is not aliased (step 368), system 22 sets the label property in the finRow object for the term and defines the row name reference (step 372). System 22 sets the AssumeZero and UserDefinedInput properties and copies the UserDefinedInput, DuplicateCode, and ItemizationCode values in the finRow object for the term (step 374). System 22 sets the input values, including the values obtained from financial database 30 (FIG. 1) and the font color values described above (step 376). System 22 then processes the next finRow object for the mockup financial statement (step 326). 
     Referring to FIG. 13C, system 22 inserts formulas into the mockup financial statement as follows (step 330; FIG. 13). For each row in the mockup financial statement, system 22 performs the following steps (step 390). If the row contains a section header term (step 392), system 22 proceeds to the next row (step 390). If the row contains a term that is in the input spreadsheet (step 394), system 22 creates a reference from each column in the mockup financial statement to the corresponding column in the input statement (step 395); system 22 then proceeds to the next row (step 390). If the row contains an itemized term (step 396), system 22 creates an item total spreadsheet formula, copies it into the first column cell of the row, and uses Excel to copy the appropriate formulas into the remaining columns of the mockup financial statement (step 398). If the row contains a calculated term and its dependents are assumed to be zero or its dependents have been converted to inputs (step 400), system 22 proceeds to the next row (step 390). If the row contains a calculated term and all of its predecessors appear in the mockup financial statement and none of the predecessors are prior expressions (step 402), system 22 creates the formula, copies it in the first column cell of the row, and uses Excel to copy the appropriate formulas into the remaining columns of the mockup financial statement (step 404). If the row does not contain a calculated term (step 406), system 22 proceeds to the next row in the mockup financial statement (step 390). If the row contains a calculated term (step 406), system 22 inserts formulas for the calculated term into each column of the mockup financial statement (step 408), then proceeds to the next row in the mockup financial statement (step 390). 
     Referring to FIG. 13D, system 22 defines formulas for a calculated term appearing in a row of the mockup financial statement as follows (step 408). For each column in the mockup financial statement, system 22 performs the following steps (step 410). If the first column is being populated and the term&#39;s formula includes a recursive prior expression (e.g., x=ƒ(x --  prior)) (steps 411 and 412), system 22 creates a reference to the input statement in the first column cell (step 414); if the term&#39;s formula includes a prior expression that is not recursive (e.g., y=ƒ(x --  prior)), system 22 copies a null value into the first column cell (step 418). If the first column cell does not include a prior expression or the first column is not being populated (step 411), system 22 creates the formula for the term, as defined in financial knowledge base 23 and copies it into the cell (step 420). System 22 then proceeds to the next column in the mockup financial statement (step 410). System 22 creates a formula by substituting the PNAME (ALIAS if one is specified by the user) into the actual formula for the term, as it is defined in financial knowledge base 23. If a calculated term has inputs that do not appear in the mockup financial statement or has a formula with a prior expression, system 22 creates in the formula a reference to the statement and column of the cell containing the appropriate input value. 
     System 22 does not insert into the input statement terms that are referenced as secondary references on one or more financial statements. With respect to formula creation, system 22 creates references back to the primary reference. 
     OTHER FEATURES 
     As mentioned above, overwriting a term name assigns an alias to a predefined term contained within financial knowledge base 23. A user may also extend the dictionary of financial terms in financial knowledge base 23 and give formula definitions to new terms by example. For example, a user-defined term and an associated formula may be inserted into a financial section of a mockup financial statement, and system 22 can be directed to add the user-defined formula to financial knowledge base 23. System 22 prompts the user to indicate whether the added term should be added to the dictionary section corresponding to the section in which the term appears in the mockup financial statement. If not, system 22 prompts the user to identify the section to which the term should be added, or whether a new user-defined statement template should be created. A user can also override a predefined formula. The user is prompted to indicate whether the existing term is to be converted into a new term (i.e., the new term will be used only where the user references the term) or whether the built-in term is to be redefined. System 22 shows in blue user-defined terms and terms with redefined formulas. For example, if a user redefined the net revenue term, system 22 displays in blue all cells with values derived from built-in formulas that depend on net revenue. 
     The mockup financial statement shown in FIG. 2 displays financial information as a matrix of rows of financial terms and columns of time periods. Financial reports can be constructed in other ways. In one arrangement, a financial report presents financial information as a matrix of rows of contexts and columns of financial terms; this is useful when there is to be one report for each time period. For example, a financial report for a database of assets can show unit price, number of units, value, change, percentage ownership, and tax liability. In another arrangement, a financial report presents financial information as a matrix of rows of periods and columns of financial terms; this is useful when there is to be one report for each context. For example, a financial report for a projection of liabilities, such as a mortgage payment calculation, can show balance, payment, and interest per period for each of a number of properties. 
     In sum, a novel toolkit for creating and editing reports has been described. The toolkit includes a knowledge base with a dictionary of domain-specific terms, which can be selected by a user to create and edit a report. The toolkit can also assemble predefined reports that can be customized with one or more editing tools. The toolkit can be used to help frame, formulate, and interpret an analysis for common business purposes. In the implementation described, the toolkit manages electronic spreadsheets using a knowledge base that represents how terms in domain-specific reports (i.e., financial statements) are related. This toolkit enhances an Excel spreadsheet by managing information and models and providing an interface between spreadsheets (cell and formulas) and databases (inputs). The toolkit provides a library of reusable components (objects) that contains definitions of numeric calculations in terms of business, organization, product, geographic, and time relations. The toolkit allows a user to easily create a standardized report based upon a predefined template or to create an arbitrary, syntactically and semantically correct report from the terms contained within the built-in dictionary, which may be customized with user synonyms. The toolkit also creates an input spreadsheet that can be used to link all non-calculated cells appearing in a report to a user-supplied database. The input spreadsheet readily allows a user to perform what-if analyses. ##SPC1## 
     The present invention has been described in terms of specific embodiments. The invention, however, is not limited to these specific embodiments, and other embodiments are within the scope of the claims.