Abstract:
A computerized data retrieval system, especially for commodity price information databases, having a windowing system which aids a user in creating and revising formal search language queries, a database searching engine responsive to such queries, means to generate and format results in both textual and graphic reports, and a capacity for echoing a formal search language query to a display in a near-natural language format for easy comprehension by the user as the query is constructed using the windowing system. The system has facilities for including domain knowledge in a query, such as market knowledge of calendar events, national holidays, triple-witching hours, and option contract expiration dates. The system has additional facilities that permit a user to include more fundamental domain knowledge, such as dates of political elections, date of issuance and value of company earning reports, the consumer price index, and so on. The near-natural language format of the query may be created and revised either through the windowing system or with a text editor.

Description:
This application is a continuation-in-part of U.S. Ser. No. 713,359, filed in the U.S. Patent Office on Jun. 11, 1991, now pending. 
    
    
     1. Field of the Invention 
     The present invention relates to automated information search and retrieval systems, and more particularly to systems designed to facilitate research into the fluctuations of commodity markets and the like over time, such as fluctuations in the stock market. 
     2. Background of the Invention 
     Many different database systems exist that can aid one in searching through the history of stock market fluctuations. These systems permit one, for example, to request the value of a particular stock on a particular date. They permit one to ask to have plotted the fluctuations of one or more stocks over a particular range of dates. 
     It is also well known to provide a general purpose database system that includes a query language in which searches can be expressed in the form of a logical expression that utilizes AND and OR logical operators to conjoin various search conditions, several of which may relate to greater than or less than relations between algebraic expressions concerning the data. Examples of such systems are DBase III, Inmagic, SOL and PARADOX. Once a complex query is defined using the query formulation language of one these systems, the system typically provides for the construction of windows that prompt the user for the values needed to facilitate the evaluation of query. But systems designed for stock market research typically do not use windows to prompt the users through the construction of an entire query, particularly any general type of sophisticated query. 
     Using conventional systems and assuming that the necessary data is present within the system&#39;s database, it is always possible for a sophisticated programmer to come in and to design a database structure, a set of queries formulated in a formal language, and a set of reports similarly formulated in a formal manner, that can extract almost any kind of desired report from the data. However, the process of designing a particular query can be time consuming and expensive, since it typically requires programmer assistance. It is not something that can be done quickly and easily by a market trader or an institutional investment manager who is not skilled in programming. 
     Accordingly, a primary object of the present invention is to design a market information machine that permits traders and portfolio managers to pose sophisticated ad hoc queries against an extensive database containing historical stock, commodity, and economic data at a level that was previously not economical nor timely, so that high-level research can be performed quickly in a way that can substantially increase trading profits. 
     SUMMARY OF THE INVENTION 
     The present invention, briefly described, is a computer system that uses templates displayed to a user in a window to prompt a user who is a trader or portfolio manager through the entire process of creating a sophisticated search request. The same windowing system may be used to review and modify the query. The query is also echoed back to the user in the form of a search request formulated in near plain English to aid the user in understanding the query. The user need not understand computer programming. The user may also escape from the windowing point-and-click-mode of a query formulation and revise the near plain English expression of the search query directly with a few keystrokes. 
     In addition, the market information machine enables the user to combine a request for the retrieval of fundamental data relating to the value of a commodity on given dates with search limitations relating to technical trading rules, holidays and historical events, business events, government reports, and even particular days of the week, month, or year, all in the same easy and simple manner. For example, one can easily request a bar chart of U.S. bond prices on all days when the consumer price index report was released by the U.S. Government, when bonds were up on the preceding day, and limited to those occurrences that fall within ten days before or after a prime rate increase. Such a search could be further limited to stipulate that only those occurrences between Memorial Day and Labor Day when the prime rate was over 10% should be displayed. 
     Invention resides in combining stock price information with economic indicator information, market average information, and other forms of market domain knowledge to form a single database (or several databases accessible by the same program) and then providing a English-like query language powerful enough to formulate time and event limited search requests such as the above example that lends itself to search formulation entirely through the use of overlaid window prompts or, alternatively, through the use of a more natural language format within the confines of a single system that can be used by traders and portfolio managers who .are not skilled in programming. 
     Further objects and advantages of the invention are apparent from the detailed description which follows, and the invention is defined with particularity in the claims annexed to and forming a part of this specification. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIG. 1 is a overview block diagram of the system 100 which embodies the invention illustrating the way in which it interacts with the user when installed on a professional workstation; 
     FIG. 2 is a block diagram of a database 114 element of the system 100; 
     FIGS. 3A and 3B are two different embodiments illustrating, in block diagram form, the way in which user queries are represented as a data structure defining overlapping windows, as a near-English command string, and as a data structure suitable for controlling the operation of a search request execution engine; 
     FIG. 4A is a pre-construction window appearing on the initial power-up screen of the market information machine (MIM); 
     FIG. 4B is a pre-compilation window appearing on the initial power-up screen of the MIM; 
     FIG. 4C is a machine command window appearing on the initial power-up screen of the MIM; 
     FIG. 5A is a pre-construction window showing the selection of the January expiration date; 
     FIG. 5B is a pre-compilation window shown with a prompt for the user to complete the attribute wheel; 
     FIG. 5C is a machine command window (the &#34;show attribute) conditions&#34;. A pre-format has been collected from the pre-construction window; 
     FIG. 6A is a pre-construction window showing the selection of the March triple-witching day; 
     FIG. 6B is a pre-compilation window showing a prompt to select from the attribute field; 
     FIG. 6C is a machine command window showing the selection of the attribute field from the pre-format statement; 
     FIG. 7A is a pre-construction window showing the selection of the closing price of the IBM one day ago plus one point as a selection for the attribute field; 
     FIG. 7B is a pre-compilation window showing a prompt for the attribute field; 
     FIG. 7C is a machine command window showing the selection of the attribute field from the pre-format; 
     FIG. 8A is a pre-construction window showing the selection of one point over the previous day for the attribute field; 
     FIG. 8B is a pre-compilation window showing a prompt for an attribute field entry; 
     FIG. 8C is a machine command window showing the selection of an attribute field; 
     FIG. 9A is the first of five bar charts of IBM generated for the query shown in FIGS. 8A, 8B and 8C; FIG. 9B is the second of five bar charts of IBM generated for the query shown in FIGS. 8A, 8B and 8C; FIG. 9C is the third of five bar charts of IBM generated for the query of FIGS. 8A, 8B and 8C; FIG. 9D is the fourth of five bar charts of IBM generated for the query of FIGS. 8A, 8B and 8C; FIG. 9B is the fifth of the five bar charts generated for the query shown in FIGS. 8A, 8B and 8C; 
     FIGS. 10 through 35 represent, in flowchart form, a formal syntax definition of a near-natural retrieval language for use in the preferred embodiment of the present invention; 
     FIG. 36 shows Menu Bars which represent &#34;pull-down&#34; windows; 
     FIG. 37 shows the XMIM mini-keypad; 
     FIG. 38 shows window scroll bars for use when all information in a window is not visible at the same time; 
     FIG. 39 shows sliders bars used in many places throughout the XMIM system for numerical input; 
     FIG. 40 illustrates two types of XMIM buttons: (1) single command Select Buttons and (2) Toggle Buttons; 
     FIG. 41 shows the interval function window in the XMIM system; 
     FIG. 42 is an interval function query example showing the graph of execution corresponding to the query for: &#34;What happens when the US Financial Future hits 95 and then falls off to 94 sometime during the day?&#34;; 
     FIG. 43A is a conditional operator menu illustrating that the XMIM system utilizes concise connectors such as &#34;crosses above&#34; and &#34;crosses below&#34;; 
     FIG. 43B is an example of a query utilizing concise connectors and moving averages showing the query: &#34;the 18 day moving average of the SP&#39;s crosses above the 50 day moving average.&#34;; 
     FIG. 44 shows the Schema window; 
     FIG. 45 shows the Schema &#34;SeriesSearch window&#34; which allows the user to select an existing time series symbol for viewing the series&#39; attributes and the associated data, modifying the series&#39; attributes, or deleting a series; 
     FIG. 46 illustrates the &#34;Series Add Window&#34; for creating new security symbols; 
     FIG. 47 shows the Schema &#34;Modify Facts window&#34;; and 
     FIG. 48 shows a sample Macro window. 
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT 
     a. A Hardware and Software Systems 
     The preferred embodiment of the invention is shown in block diagram form in FIG. 1 of the drawings. The invention is implemented on a professional workstation 102 which, in the preferred embodiment, falls within the Sun Microsystem, SUN3 or SUNSPARC family of workstations, or it may be a Hewlett Packard HP9000 Series 400 or 700 workstation. The operating system used in the preferred embodiment is SUN-OS 4.0.3 or higher, or HPUX 7.0 or higher. In addition, the workstation is equipped with x/MOTIF, the industry standard windowing software designed to work with Unix under X Windows. 
     The invention focuses upon the interaction between a user 105 and a system of programs 100 installed on the workstation 102 which results in the user being able to develop database queries 107 using a windows interface program 104 and to view the queries in a natural English form on the screen (query feedback 109) while preparing and revising the queries using the windows interface program 104 for guidance. 
     The windows interface program 104 provides a vehicle whereby the user may develop a query on the screen of the workstation 102. The windows interface program 104 places in front of the user 105 templates which list the alternative query 105 formulations that the user can select using a mouse pointing device and a typewriter to prepare specific queries. The query windows, illustrated below, correspond to the language options that are set forth in a formal description of the query language that is also presented below, and thus guide the user through all of the possible query formulations that the language is capable of achieving. As the query is developed, it is represented in a tree structure composed of the various overlapping windows that are used by the user to create the query. The query language is basically an English-like language especially tailored to be embedded within a window&#39;s prompting system. But the queries are equally capable of being represented in what appears to be normal English. Accordingly, as the query is developed, a natural English version of the query is developed by the windows interface 104 and is passed to the display manager 106 for presentation as query feedback 109 to the user 105, so that the user can see a natural English language expression of the query or partial query that has been developed. In one embodiment, the user may enter or edit the English language query expression directly, rather than enter or edit the query using the windowing prompts. This facility enables all users to save time, and advanced users may bypass the windowing system on occasion. 
     The query itself is represented internally as a query representation 108 which is, in reality, a database structure that defines the overlapping set of windows which the user uses to define the query. When the user is finished defining the query and calls for the generation of reports based upon the query, the query representation 108 is compressed into a more compact, parsable form from which redundancies have been eliminated and is passed to an execution engine 110 which parses the query and calls upon a database manager 112 to extract the necessary information from a database 114; to search through the data performing the called for logical, mathematical, time range, and numeric computations; and to present the resulting information to a report manager 116 and also to a graphics manager 118 which respectively prepare reports 120 and graphs 122 for display to the user 105. 
     With reference to FIG. 12.2, the database 114, in the preferred embodiment of the invention, contains individual stock price information 202 concerning the price of stock on a daily (and optionally on an hourly) basis over the years. In addition, the database contains market averages information 204, such as the Dow Jones averages each day over extended periods. The database 114 also contains economic indicators information 206, such as the consumer price index, the GNP, automobile production figures, IBM&#39;s sales and profits (for example), and other such indicators, together with the dates upon which this information is released if appropriate. In addition, the database 114 contains market domain knowledge 208 relating to dates that can have an influence upon the market; such dates as holidays, special holidays, triple-witching days, and option contract expiration days, for example. Dividend distribution dates are also included. The user may also add special databases, such as bear or bull market dates, for example. Even the dates of the lunar cycles may be added to the system for use in the market studies. 
     The databases shown in FIG. 2 used in combination with the system 100 shown at FIG. 1 creates the potential for the user to generate reports that are of particular use to market traders and analysts in trying to examine past actions of the market at certain times, such as when dividends are paid or when special market events occur. In addition, the user may add the user&#39;s own market domain knowledge to the market domain knowledge 208 within the database 114 and thereby create a separate body of information for special reports. But to realize the potential of the database, a carefully human-engineered interface between the user 105 and the remaining parts of the system is provided in the form of the queries 107 which are implemented using overlapping windows and which are based upon an English-like search query language. 
     FIGS. 3A and 3B illustrate a way that user queries are processed in two different embodiments of the invention. In FIG. 3A, the user 105 interacts directly with the windows interface 104 to create and later to modify the query. During this interaction, information from the windows interface 104 enables an echo generator 302 to construct a natural language formulation of the query (or partial query) which is displayed on a screen 306 to the user but which is not directly editable by the user. When the query formulation process is completed, the windows data structure 304, created by the windows interface 104, is passed in a simplified form, stripped of redundancies, to an execution engine 110 which parses the data structure and then executes the database retrieval actions for and also causes the necessary reports to be generated, and formatted for printing and display. Note that report definition is inherent in the search query formulation process. 
     A second embodiment of the invention, illustrated in FIG. 3B, also permits the user 105 to interact with the user&#39;s windowface 104 to create a window data structure 306 that embodies the search request. The user 105 may then review and revise the query using the window interface just as in the embodiment of FIG. 3A. In addition, the echo generator 308 is designed to be bi-directional so that the window data structure 306 may be translated into an ASCII command string which is then presented to the user by a command string interface 310. The user may not only review the ASCII command string but may also edit the command string and revise it. Then the command string interface 310 reverses the process and essentially parses the command string back into a windows data structure 306 which may then be presented to the user 105 through the windows interface 104. The user is thus given the choice of entering and revising the query either by writing and revising an ASCII command string or by working through the series of overlaying window queries and prompts. Typically, a beginning user will stick with the windows queries and will only use the ASCII command string to make minor changes, as in the spelling of a particular stock name. Advanced users may then wish to save time by entering the query initially using the command string editing facility and possibly only use the windowing system to check out additional options that the user may have been forgotten. In either case, the final query data structure 306 is passed through a compiler 312 and is compiled into a compact tabular or tree form suitable for guiding the performance of an execution engine 110 through the tasks of retrieving the information, carrying out the relational steps called for by the search query, and generating and formatting the necessary reports. 
     b. The window System That Interacts With The User 
     FIGS. 4A, 4B and 4C represent the windows which appear on the power-up screen of the market information machine (MIM). FIG. 4A is the query construction window. The query construction window is always located in the lower half of the MIM screen. On power-up, this window presents the user with seven query format options 402-414 to be used in the construction of queries to the market information database. Each of the seven query formats provide a unique framework to be used in the construction of a query for searching the database. The query format also defines the sequencing of the later MIM screens and the order in which the query is constructed. This provides autosequencing which walks the user through the query construction, thereby preventing the construction of bad queries. FIG. 4A shows option 402 as being selected because it is illustrated in darker print than the latter six options 404-414. Option format 402 defines a &#34;show attributes when conditions&#34; query format. Option 402 is selected by placing the mouse pointer 418, shown in FIG. 4B on option format 402 with the mouse and clicking-on option 402. 
     Other formats are defined in option 404-414. Option format 404 is the &#34;show count of days when conditions&#34; query format. Option format 406 is the &#34;show percent of days in universe when conditions&#34; query format. Option format 408 is the &#34;first values of attributes when conditions&#34; query format. Option format 410 is the &#34;show last values of attributes when conditions&#34; query format. Option format 412 is the &#34;show maximum values of single attributes when conditions&#34; query format. And, option format 414 is the &#34;show minimum values of single attributes when conditions&#34; query format. 
     Once the user has chosen one of the query formats 402-414, then the user completes the selection by moving the mouse to the COMMIT 416 and clicking. When the user is committed to a particular option 402-414, then the query format is defined. The query format will then appear in the machine command window (FIG. 4C) and its construction will be compiled according to a predetermined autosequencing of window menu selections on the MIM screen display. This construction takes place in the query construction window (FIG. 4A) and the compilation is shown in the query compilation window (FIG. 4B) as the query construction progresses. 
     FIG. 4B is the query compilation window on power-up. The query compilation window is located in the upper left-hand corner of the MIM screen. FIG. 4B is shown with a blank window because no commands have been compiled on power-up. The MIM is idle waiting for commands on power-up. The mouse pointer 418 is used to click on selections with the mouse. 
     FIG. 4C illustrates the machine command window on power-up. The machine command window illustrated in FIG. 4C is located in the upper right-hand corner of the MIM screen display. The window is shown empty on power-up because a query format has not been chosen. The machine command window will show the query format 402-414 which is being operated on by the user. Eight soft key commands are located along the top of the machine command window. QUIT 420 is used to terminate the query the MIM program. RESTART 422 is used to re-initiate a query command process. EXEC 424 is used when a query is completely constructed. Clicking-on EXEC 424 will begin execution of the database search with the query shown in the query compilation window. PLOT 426 will plot the results of a database search. Examples of plots are shown in FIGS. 9A-9E. CONT 428 is used to continue the execution of a command on the MIM when it has been paused. SAVE 430 is used to save the results of a query on the MIM. PRINT 432 is used to print the results of query. FRONT 434 is used to position windows at the front of the MIM screen display. 
     FIG. 5A illustrates a query construction window showing attribute field options 502-520. DATE option 502 allows the user to select a data in field 522 in order to use a specific date as an attribute for determining when to display market information from a particular date. Field 522 is shown with Jun. 6, 1991. Day of the week option 504 uses the day field 524 to select a particular day of the week by clicking on field 524 with the mouse and then typing in the day of the week. Day field 524 is shown having Monday selected as the desired day of the week. Month option 506 is used with field 526 to select a particular month as an attribute. Here, January is the selected month. Year option 508 is used with field 528 to allow the user to type in a particular year. Illustrated here with 1991. HOLIDAYS option 510 is used with field 530 to select predetermined holidays by typing them into field 530. Major holidays such as Christmas and New Years are included. SPECIAL DAYS 512 is used with field 532 to allow the selection of attribute options corresponding to other important days of the year. Shown in field 532 is Martin Luther King&#39;s birthday. Other predetermined special days such as Lincoln&#39;s birthday, Washington&#39;s birthday or President&#39;s Day could also be used in option 512. Option 514 is used for menu selection. This is illustrated by a double-arrow icon 536. Icon 536 is shown having &#34;Expiration in (month)&#34; as being selected from the menu. Field 534 which is used to click on and type in the month of the option expiration date which the user is interested in. Menu selection double-arrow icon 536 is used to present other options to the user. When the user clicks on double-arrow icon 536 with the mouse, the user can select the option expiration date as shown in option 514. However, clicking-on the double-arrow icon 536 will change options to the triple-witching expiration date or the next dividend date for a particular stock. WITHIN OPTION 516 is used with unit field 538 and menu icon 540 to select an attribute of stock performance within a particular time period. Field 538 will select a number of time units of interest and icon 540 will change the units. 
     Icon 540 is used to select from a menu of time units for use in the WITHIN option 516. Other time units which will become available by a clicking on icon 540 are days, weeks, months, and years. FIG. 5A is shown with days selected by icon 540. FROM OPTION 518 is used with field option 544 and field option 542 to select an attribute for determining when to display market information by defining the attribute from a particular date 544 to a latter date 542. Option 518 is shown with the attribute from Dec. 28, 1959 to Jun. 6, 1991. 
     Options 502 through 518 are considered domain knowledge for the MIM, because they contemplate the use of predetermined dates for making database queries. Date, day, month and year information is preprogrammed into the query format structure of the MIM as are certain holidays, such as New Years and Christmas. Special days, such as Martin Luther King&#39;s birthday as illustrated in option 512, Lincoln&#39;s birthday, President&#39;s Day, and so on are preprogrammed. Special market dates are also preprogrammed into the MIM, these include ex-dividend dates for particular stocks, option expiration days in a particular month for a stock, and the triple-witching expiration dates. The domain knowledge offers flexibility in the standard construction of queries for the MIM database. This offers a great deal of flexibility for the user in making ad hoc queries about market conditions and testing the effectiveness of particular market rules for buying or selling stock or options. IN FILE option 520, however, allows the user added flexibility in that custom date attributes may be compiled by the user for the purpose of determining when to plot market information. These special dates, chosen by the user, are entered into a file and the file name is typed into field 546. FIG. 5A shows the date file typed into field 546. These dates may include dates corresponding to bull markets or bear markets, lunar cycles, sun spot cycles or any other dates which the user has an interest in using as an attribute for determining when to compile market information. So, IN FILE option 520 provides the user with added flexibility to make custom queries. Option 514 is shown darker than the other options because the user has clicked-on option 514. An interpretation of option 514, as illustrated in FIG. 5A, is constructed in 552 which reads: &#34;January expiration date.&#34; Once the user has determined that the query construction shown in compilation 552 is as desired, the user can commit to the query construction by moving the mouse to COMMIT 548 and clicking on COMMIT 548. If the user wishes to cancel the query shown in 552, the user may do so by moving the mouse to CANCEL 550 and clicking on CANCEL 550. This enables the user to start over with attribute selection for the purpose of constructing a query. 
     FIG. 5B shows the query compilation window on the MIM screen. The attribute selected in FIG. 5A is prompted in FIG. 5B with the &lt;attr&gt; symbol 554. When the user clicks on COMMIT 548, the attribute symbol 554 will be replaced by the query construction 552 which is &#34;January expiration day&#34;. So the query illustrated in FIG. 5B will read &#34;show the movement over the previous day of the closing price of IBM repeated for the current and next five days when the date is January expiration day.&#34; This then represents an appropriate query compilation. With the query compilation finished in FIG. 5B, the user can proceed to the machine command window, FIG. 5C, to instruct the MIM as to what to do with the query command. Clicking-on EXECUTE 424 will then cause the MIM to execute the query from the query compilation window and display the appropriate values. Clicking on PLOT 426 will command the MIM to plot appropriate marketing information as illustrated in FIGS. 9A-9E. The machine command window, shown in FIG. 5C, also shows the basic structural format of the query illustrated to show the attributes which condition the market information search. Fields 556 through. 568 are used to click on with the mouse in order to flesh out the query format and construct a query for compilation. Attribute field 556 is used as an attribute of the desired market information, for example, what stock is desired or what market index is desired. REPEAT 558 will command the MIM to repeat attributes 556. ATTRIBUTE 560 which is a field for determining when market information defines an attribute 560 should be displayed. OP 562 represents an operating field for operating on attributes under the WHEN condition. Attribute 564 is shown enlarged relative to the other fields because it has been clicked on by the mouse and the field is being operated on in the query construction window as illustrated in FIG. 5A where the January expiration date has been selected. Repeat 566 can be used to repeat WHEN conditions in the query format. CUM-ATTR 568 is used for cumulative attribute conditions for the purposes of determining what market information to be queried from the database. 
     FIG. 6A shows a query construction window which is similar to that described in FIG. 5A except that icon 536 has been clicked on with the mouse and has switched from the &#34;expiration date&#34; to the &#34;triple-witching date.&#34; The March date has been selected in field 534. So in FIG. 6A, the 514 option now represents the &#34;March triple-witching day&#34; as shown in the construction interpretation 552. Clicking-on COMMIT 548 will replace attribute 554 in FIG. 6B with &#34;March triple-witching date&#34;. This completes the query compilation in FIG. 6B. 
     FIG. 6C, illustrating the machine command window with a selected query format, again attribute 564 is shown enlarged because it was clicked on and selected by the mouse. This has been determined in the query construction window to be the March triple-witching date 522. 
     FIG. 7A illustrates a query construction window for determining attributes which determine when to display market information based on stock prices, market indices, such as composite averages for volumes, or other market performance criteria. Command line attribute 702 has been clicked-on by the mouse and is illustrated in darker print than options 704-710. Security field 712 has been filled in with IBM. So the query construction illustrated by 522 is the closing pricing of IBM one day ago plus one point. If this is what the user intended, the user may click-on COMMIT 548 and the construction 522 will be used as the market information attribute 700 as illustrated in the query compilation window of FIG. 7B. 
     Option 704 enables the user to use volume as an attribute. Field 714 is shown with the Dow Jones Industrial Average (DJIA) Market Index as being selected. Option 706 is used when selecting actual values of stock or commodity prices as an attribute for searching marketing information. The open market price has been selected in field 716 and commodity selected in field 718 is the Deutsch mark (DM). Field 720 illustrates a default option of the same day and Field 722 illustrates a default option of no offset in comparison of the actual value attribute 706. 
     Option 708 enables the user to switch from actual values to changing values. Icon 724 causes the user to switch between the previous or the next number of days being defined in field 726 which is shown with one time unit. The units can be switched with icon 728. Icon 728 allows selection of days, weeks, months or years as a time unit. The market change information can be made relative to an economic indicator with field 730. Field 730 is shown with the consumer price index (CPI). The number of days which the user is interested in retrieving is entered in field 732. The time period can be switched with icon 734 and icon 736. Icon 738 will provide offsets. Clicking-on icon 738 will provide either positive, negative or no offset. Icon 783 is shown as having a positive offset and the unit is placed in field 740 shown as being one point. 
     Alternatively, the user may select a constant 710 as a price comparison attribute. Field 742 defines the constant. As illustrated, field 742 is one point. The attribute selected in the query construction window of FIG. 7A will be used in attribute 700 as shown in FIG. 7B. This attribute was selected by the machine command window where attribute 564 is shown enlarged and thus selected in FIG. 7C. 
     FIG. 8A is a query construction window showing the selection of a price attribute defined by attribute 522 as &#34;one point over the previous day.&#34; This is done by selecting the CONSTANT option 802 and filling field 806 with one point. The OVER/PREVIOUS field was selected with icon 810. Limiting it to one day is done by entering one into field 812. The time period is selected with icon 814 as days. Instead of choosing a constant by clicking-on option 802, the user may alternatively choose the PERCENT option 804. The percentage which the user is concerned with is then entered into field 808. When the user clicks-on commit 548, the query shown in FIG. 8B will be completed by replacing attribute 800 with the construction of attribute 522. So the query compilation will read as follows: show the bar chart of IBM repeated for the previous 20 to the next 20 days when the date is in file IBM.DIVS and the closing price of IBM one day ago is down more than one point over the previous day. This particular compilation represents an example of constructing a query to determine what happens to IBM stock when the day before it goes ex-dividend IBM goes down by more than a point. 
     FIG. 8C shows the query construction format and the selection of attribute 564. By clicking on plot 526, the MIM will proceed to plot the results of the query shown in FIG. 5B. A plot of the query compiled in the windows of FIGS. 8A, 8B and 8C is illustrated in FIGS. 9A-9E, which are bar charts of IBM repeated for the previous 20 to the next 20 days. In each case, the date and bar which represents the occurrence of the attribute defined in the query compilation of FIG. 8B is represented by dotted line 902. 
     FIGS. 9A-9E are particularly informative because they illustrate that the price of IBM has decreased in price after the date of interest 902. Thus, the market test defined by the query is in fact a good test for determining when to sell IBM stock or when to short IBM stock. This illustrates the way in which a trader could hypothesize a particular market test for buying or selling stock and then test the hypothesis. Once translated into an ad hoc query by using the query construction tools, in the compilation window, the trader may then proceed to command the MIM to execute the query and plot graphs of the market information. 
     FIGS. 9A-9E illustrate the ease with which a trader can verify the effectiveness of a particular test by easily discerning the trend of the data from the plots. 
     c. The Formal Description of the English-Like Query Language 
     FIGS. 10 through 35 show the syntax charts for the MIMTOOL V.1 language. Turning to FIG. 10, a query 1000 is constructed according to the syntax shown. The query 1000 begins with the command &#34;SHOW&#34; 1002, followed by an attribute to be shown, followed by the command &#34;WHEN&#34; 1004, followed by a condition list. There are five general query constructs, 1006, 1008, 1010, 1012 and 1014. In query construct 1006, an attribute is shown outright when it meets the given conditions. In query construct 1008, the count of days, weeks, months, or years is shown for occurrences according to the given conditions. In query construct 1010 a percent of time or occurrences within a larger &#34;universe&#34; of time or occurrences, defined by a condition list, is shown when the given &#34;WHEN&#34; conditions are met. In query construct 1012, the first or last selected number of values of selected attributes are shown when they meet the given conditions. In query construct 1014, the maximum or minimum selected number of values of a single attribute are shown when they meet the given conditions. 
     In FIG. 11, a cumulative attribute list operator syntax 1100 is shown. A cumulative attribute operator may be selected in query construct 1006. Note that pathway 1102 allows more than one cumulative attribute operator to be selected for a given query construct. 
     FIG. 12 shows the &#34;show attribute&#34; function syntax 1200. Attributes are shown for selection in all five of general query constructs, either as attributes to be displayed, or as ,elements of &#34;WHEN&#34; conditions. Attributes may be shown either directly or as a &#34;study&#34; 1202. In item 1206, the actual series of data defining the attribute is selected, such as a particular stock, the Dow Jones Industrial Average, Standard and Poors Index, the Consumer Price Index, or other series, by way of example. If a selected series 1206 has more than one &#34;column&#34; of data, such as open, high, low, close, and so on, the column is selected in item 1204. A time offset 1208 may also be selected, indicating the data should be extracted from a period different from the time frame of the query construct, such as a certain number of days ago, or a certain number of weeks later, for example. 
     Turning now to FIG. 13, the variety of studies 1202 which may be performed on a given series is shown. Each of the studies requires a time frame over which the study is carried out. This is selected by the &#34;OVER&#34; command 1302. The time frame is defined as the &#34;previous&#34; or &#34;next&#34; certain number of units of time with respect to the time frame of the query construct. 
     In FIG. 14, the columns 1204 of a series of data are shown. For a given series of data, such as for a selected stock, one may thus choose to show the opening, high, low, closing stock price, the volume of the stock traded, or the open interest on the financial instrument, by way of example. 
     In FIG. 15, it is shown that any of a series of data may be selected as an attribute to be shown. These include, but are not limited to, stocks and other traded financial instruments, and important trading indices. Item 1500, shown in a broken line, indicates that the user may add new series of data to the system. As a result, the user has query access to data which may not normally be included in commonly available trading market databases. Such a series might be in the form of periodically released statistics on auto production, crop production, trade figures, reports on particular stocks and companies, and so on, by way of example. 
     In FIG. 16, is shown the format of the time offset 1208. The time offset may be selected to be previous to or later than the time frame of the query construct, indicating the data should be extracted from a period different from the time frame of the query construct, such as a certain number of days ago, or a certain number of weeks later, for example. 
     In FIG. 17, the format 1700 of a selection of units of time is shown. Thus, queries may be constructed to examine series data over periods of time defined by the units days, weeks, months and years. 
     Turning now to FIG. 18, the format of an attribute list is shown. The attribute to be shown is constructed in item 1200, and repeat syntax 1900 may be used to show the attribute or the study of the attribute repeatedly for a number of units of time. The &#34;AND&#34; operator 1802 permits an indefinitely long attribute list to be constructed. 
     Turning now to FIG. 19, the detailed format of the repeat syntax 1900 is shown. Using the repeat syntax, a series or a study of a series may be shown repeatedly for a selected number of consecutive units of time relative to the time frame of the query construct. For example, one may choose to show the movement over the previous day of the closing price of a particular stock repeated for the current and previous four weeks. Alternatively, one may choose to show the movement over the previous day of the closing price of a particular stock repeated for the previous five days to the next five days, by way of example. 
     Turning now to FIG. 20, the format is shown of the condition list 2000 used to condition a series of data or a study of a series of data to be shown. Conditions may be repeated in the repeat format 1900 in much the same way as attributes are repeated. The &#34;AND&#34; operator 2002 permits the user to construct an indefinitely long condition list. 
     In FIG. 21, the format of a single condition 2100 is shown. There are three general types of conditions. In the path which contains the date operator 2106, the data selected to be shown is conditioned by a selection operation based on time. In the path containing the operator 2104, the data, is conditioned by a comparison between a first, or &#34;left&#34;, attribute and a second, or &#34;right&#34;, attribute The right attribute may be as simple as a constant, or as complicated as an entire attribute construct with studies 1202, columns 1204, and arithmetic operations on the data. In the path which contains the &#34;UP&#34; operator 2102, the data selected is conditioned by the progress of an attribute over time. 
     Turning now to FIG. 22, the format is shown of a condition on the progress of an attribute over time, indicated as &#34;up amount&#34; 2200. The progress is defined by a percent change 2202 over a period of time defined by the time units 1700. 
     FIG. 23 shows a comparison operator syntax 2104 for use in a condition 2100. Operator 2104 is used to compare said left and right attributes. 
     In FIG. 24, a data operator 2106 is selected for a condition 2100. 
     FIG. 25 shows that the syntax for defining a left attribute 2500 for a condition 2100 is the same as the syntax for constructing the attributes 1200 to be shown. 
     FIG. 26 shows that a right attribute 2600 for a condition 2100 may be constructed in a fashion identical to the construction of the left attribute 2500, or may be a number 2602, or may be an attribute upon which an arithmetic operation is carried out through the arithmetic operator 2604. 
     In conjunction, then, the syntax for the left attribute 2500, right attribute 2600, and operator 2104 may be used to develop a condition for a query such as: &#34;. . . WHEN the closing price of &lt;a first particular stock&gt; is more than the closing price of &lt;a second particular stock&gt; * 1.5.&#34; 
     In FIG. 27 are shown the four basic operators which may be used as the arithmetical operator 2604. 
     FIG. 28 shows the syntax for the selection of a data choice 2800 to be included in a date condition. The date may be as simple as an outright date 2802, a day of the week 2804, a month of the year 2806, a year 2808, or a particular holiday 2810. Alternatively, the date choice 2800 may be the expiration 2812 of a stock or financial instrument series addressed in the query construct, or may specify the expiration 2812 to occur in a particular month 2814. The date choice 2800 may also be any triple-witching day 2816 or else a triple-witching day 2816 in one of the four periods 2818 signified by either March, June, September or December. The date choice 2800 may be chosen to be within a number of time units 2820 or within a specific time frame, from a certain date 2820 to a certain date 2824. 
     Finally, the date choice 2800 may be found in a file of dates 2826. This last option gives the user the flexibility to add the effects of certain special events to the query, which might not otherwise be included in a typical analysis, because of the difficult of addressing such special events in standard database and economic analyses systems. For example, dates which are not normally available in common stock and financial instrument databases, such as the dates on which certain market-related or market-unrelated reports are released to the public, may be included in the query to observe the effect on the series or study of series to be shown. By allowing access to a file of dates, the system enables the user to customize the query to conditions very specific to the domain knowledge of the user. For example, the dates of the release of auto production figures by the government are not typically found in common financial instrument databases, and are not easily included in standard query systems, yet may show useful correlation to changes in stock prices, which correlation may be easily tested with the system of the present invention. 
     A file of such dates may also include numeric data related to those dates upon which the query may also perform, said numeric data being defined as a series 1206. Thus, to use the aforementioned example, a user could add to the system the dates on which auto production figures are released, and also the figures themselves. 
     In FIG. 29 is shown the syntax for selecting a month name 2806 for a date choice 2800. 
     In FIG. 30 is shown the format for the selection of a month 2818 from the set of March, June, September and December for use in a date choice 2800 based on a triple witching date 2816. 
     FIG. 31 shows that a year syntax 2808 selected for a date choice 2800 is simply a number. 
     FIG. 32 shows the format for a holiday 2810, which may be selected for a date choice 2800. The ability to select holidays adds to the flexibility of the system of the present invention, as such dates may not normally be available for querying in other database systems. 
     Turning now to FIG. 33, the format is shown for a date 2802 for selection as a date choice 2800. The format is a standard date format wherein the numbers 3304 are separated by slashes 3302. In the case that the day, the month, or the year of the date 2802 need not be limited to any particular number, an underscore character 3300 may be selected in place of a number 3304. 
     FIG. 34 shows the syntax for a day of the week 2804 to be used in a date choice 2800. 
     FIG. 35 shows the syntax of the &#34;UP&#34; operator 2102. 
     d. Alternative Embodiment Having Enhanced User Interface and Query Language Features 
     The window system that interacts with the user as described in the previous section represents a basic embodiment of the present invention for facilitating computerized data retrieval with the MIM. Described in this section is an alternative embodiment of the MIM invention having advanced user friendly features including menu bars, slider bars, select buttons, toggle buttons, macro functions, enhanced graphic features, advanced math functions and improvements to the query language. This alternative embodiment of the present invention will hereinafter be referred to as the XMIM. 
     1. Improved User Interface 
     a. Menu Bars 
     As illustrated in FIG. 36, Menu Bars 3600 are a part of each window. Each word in the Menu Bar 3600 represents a &#34;pull-down&#34; window 3602. To access a pull down window 3602, the user uses the mouse to point to the menu desired and clicks on that menu. The desired menu is then displayed on then screen. Then the user may move the pointer to the desired function and click again. The Menu Bar 3600 is the primary way to access XMIM&#39;s functions. Therefore, browsing through the menus and their functions often serves as an excellent overview of XMIM&#39;s features. Occasionally, users will notice a small arrow 3604 pointing right next to the menu label. This is called a Cascade Menu or submenu (not shown). Cascade Menus are used to group similar functions together. Clicking on a cascade menu label will display a submenu list from which to select additional features. 
     b. Arrow Keys 
     Referring now to FIG. 37, the arrow keys 3702 on the XMIM mini-keypad 3700 (to the right of the keyboard) may be used in lieu of the mouse to scroll through and select menu features. The &#34;2&#34; key scrolls down, &#34;4&#34; scrolls left, &#34;6&#34; scrolls right and &#34;8&#34; scrolls up. 
     c. Unselect Menus 
     If the user clicks the mouse on a menu bar 3600 and decides not to select any of the menu options, then the user simply clicks the mouse button again anywhere outside the menu window. The menu window will disappear and no items will have been selected. 
     d. Scroll Bars 
     Referring now to FIG. 38, it is apparent that because of the boundaries of windows, all information in a window may not be visible at the same time. Whenever a list of resources is larger than the list box 3800, XMIM displays scroll bars 3802 along the right (vertical) and bottom (horizontal) edges of the box 3800. A scroll bar 3802 is a control that allows the user to control what portions of a larger object is displayed within the box 3800. They have an arrow at each end and a rectangular slider 3804 in the middle. The slider represents the current relative position in the list. There are two ways to move a slider (1) using arrow keys 3700, and (2) dragging the slider with the mouse. 
     Point to the slider on the scroll bar 3802, press and hold the mouse button to grab the slider, and, still holding the mouse button down, move the slider up and down on the vertical bar or right and left on the horizontal bar. The list will scroll keeping up with the mouse movements. 
     e. Slider Bar 
     Referring now to FIG. 39 note that sliders 3804 are not only found the scroll bar 3802, but many places throughout the XMIM system including the slider bar 3900 which is used for numerical input. By using slider bars 3900 for inputting data, the user no longer has to type in numbers with the keyboard. Rather a sliding number gauge 3902 is provided for indicating to the user whether the input setting of the slider bar 3900 is the input desired by the user. 
     In addition to using the mouse to grab and &#34;drag&#34; the slider bar 3900, the user may also use the arrow keys 3700 located on the mini-keypad 3702. This can be very useful in selecting a precise number on the sliding number gauge 3902 with the slider bar 3900. 
     f. Buttons 
     Another interesting interface associated with the XMIM system is buttons. There are two types of XMIM buttons shown in FIG. 40: (1) single command Select Buttons 4000 and (2) Toggle Buttons 4002. 
     The Select Buttons 4000 are first seen on the main window of the XMIM system. They are represented by command words visible inside of rectangular boxes. Clicking on these buttons will display other windows with additional selection items or will take the action shown by the button (e.g., QUIT). 
     The second type of button used in selecting options in the XMIM system is the toggle (on/off) button 4002. These buttons are represented by a square, which, when selected or highlighted, lightens in color (or darkens on monochrome screens). Click the mouse button on the square to select the option associated with the button. As these are toggle buttons, click the mouse again on the square to unselect the option. 
     g. Editing Features 
     In creating a new query sentence structure, the user may &#34;cut and paste&#34; old query sentence structures. This allows the user to easily modify old queries and experiment with new queries. 
     2. Enhanced Graphics Interface 
     Selecting Graphics from the Options menu brings up the Graphics Defaults menu. This window allows users to customize the graphs generated when Execute-Graph is chosen. By editing the Graphics Defaults menu, users of the XMIM system may change the colors of the graph display. 
     a. Report Title 
     The XMIM system allows the user to type in a title for the graphs generated by the XMIM. The report titles are input in a field found in the options menu. This is a test field, so any of the characters on the keyboard (including spaces) may be used. 
     b. Graphs Per Page 
     This option specifies how many graphs will be displayed on each page of the report. The format is rows x columns, i.e., 4×2=8 graphs per page, 4 graphs across the page and 2 graphs down the page. Any number of these rows x columns pairs may be used. The XMIM system will then pick the most appropriate layout. For example, the system default specifies 1×1, 1×2, 2×2, and 3×2 row and column designations. Depending on the query, the system may pick any one of these four layout pairs. As a general rule, if there are many answers to the query, XMIM may display only 2 graphs per row and column. If it is preferred to have control over the layout of the graphs, the user may enter the number of rows and columns desired to be displayed. As a shortcut, the user does not have to enter the row and column numbers. Instead, the user can simply type an integer specifying the number of graphs desired per page. In other words, typing 4×2, will result in the same graphics layout page as typing the number 8. 
     c. Plot Colors 
     If the user is running XMIM on a color monitor, numerous colors are available for plotting graphs. It is read from left to right, with the left most color associated with the first SHOW-Attribute statement of the query. If the query has more than one SHOW-Attribute statement, the second color in this box will be used to plot the second statement, and so on. To edit this box, simply click the mouse button anywhere in the box. Using the system&#39;s the backspace key erases the color to the left of the insert point (or else press the delete key to erase the color to right of the insert point). To insert a color, type the name of a valid system color at the insert point. The user must make sure the colors are separated by a space, if multiple colors are desired. 
     d. Axis Colors 
     Selection of the Axis Colors box shows a list of colors similar to those in the Plot Colors box. The Axis Colors box, however, lists the colors for the x and y axis of the graph. Because XMIM allows multiple y axes (created with the Show-Attribute statements), the left most color is used to display the first SHOW-Attribute query statement on the left y axis and the second color is used to show the second SHOW-Attribute statement on the right y axis. As in Plot Colors, the system will circle through the colors for each SHOW Attribute statement. 
     To edit this box, click the mouse button anywhere in the box. To delete a color, press the backspace key to erase the color to the left of the insert point (or press the delete key to erase the color to right of the insert point). To insert a color, type the name of a valid system color at the insert point. 
     e. Grid Colors 
     Several colors are available as grid colors as well. Grid colors display the color of the grid lines (dots) behind the plotted answers. Once again, the left most color will show the grid lines associated with the first SHOW-Attribute statement, the second color, with the second SHOW-Attribute statement, etc. To edit, click the mouse button anywhere in the box. 
     To delete a color, press the backspace key to erase the color the left of the insert point (or press the delete key to erase the color to right of the insert point). To insert a color, type the name of a valid system color at the insert point. Make sure the colors are separated by a space. 
     f. Background 
     The Background color is the color of the page on which the graphic are displayed. The user may edit this by clicking the mouse button in the rectangular box, erasing the default color (black), and typing any valid system color. 
     g. Plot By Answer 
     This is another toggle button which, when activated, will produce a different graph for each query answer (plot By Answer). This is best used to display those queries constructed with the repeat option. If this option is not selected (Plot By Show), a different graph will be displayed for each SHOW-Attribute statement. Therefore, it is best used when the solution involves a specific range, such as, a given year. 
     h. Overlay 
     Another toggle button, this option produces different plots for all SHOW-Attribute values on a single graph (i.e., pct. move, average, bar, volume, etc.). When clicked off, each SHOW-Attribute value will be individually displayed in separate graphs. 
     i. Show Date 
     If this toggle button is depressed, the day that satisfies the selection criteria of the query statements is displayed at the top of each graph. The printing of this date can be turned off by clicking the mouse button on this option. 
     j. Report Generator 
     A report generator facility on the XMIM allows the user to customize the output of reports. For example, the report generator facility allows the users to design their own report format and give appropriate labels to the columns of the report. A profit and loss module may be used with the report generator facility to allow the user to track the current status and the profit or loss associated with each trade. Accordingly, these features allow users to create their own customized reports. 
     3. The &#34;Interval&#34; Feature 
     The Interval feature &#34;Interval&#34; is an incredibly powerful feature in that it allows the user to construct queries concerning conditions over time intervals. For example, the user may desire to see all times the Dow Jones Industrial Average (DJIA) went up four out of five days, or perhaps when a security had eight up-ticks out of 10 ticks by 9:15 a.m., etc. The dramatic improvements to the query language are made possible with the interval feature. 
     The Interval feature of the XMIM system is used in conjunction with the Command WHEN 1004 to further restrict the selection criteria of the query. It is located directly to the right of the Condition box under the Command WHEN 1004 category from the XMIM main window. This feature can only be accessed after the WHEN-Condition of the query has been constructed because it restricts the Condition to an interval of time. 
     After constructing the WHEN-Condition of the query (e.g., High of DJIA is exactly Close of DJIA), click the mouse button on the Interval rectangular box. The window shown in FIG. 41 will be displayed. 
     Initially, the user should notice two major columns displayed in this window. If the user wishes to change the default options, she selects one option from each category to apply to the Interval statement: an option from the Time Period Mode, an option from the left column, and an option from the right column. 
     a. Time Period Mode 
     The Mode button 4100 is located in the lower right portion of the Interval window. This is the most important option because it sets the time period mode by which the Condition will be tested. The system default mode is set to Daily. If the user wants to change the default, she clicks the mouse button on the rectangular box to the right of Mode, and select one of the following: 
     - Daily 
     - Weekly 
     - Monthly 
     - Quarterly 
     - Yearly 
     The units of time available for constructing the Interval statement depend on the Mode selected. Changing the Mode unit changes the selections available for some of the other Interval options. The selections are updated as the mode is switched such that only appropriate units of time are available. Others are desensitized. The following chart shows the time period units available for each Mode: 
     
         ______________________________________Daily   Weekly    Monthly   Quarterly                                Yearly______________________________________Units   Units     Units     Units    UnitsMinutes Days      Days      Days     DaysHours             Weeks     Weeks    Weeks                       Months   Months                                Quarters______________________________________ 
    
     There are three procedures for selecting the Interval options: 
     1. Slider Bars 
     Whenever a specific number is requested, click mouse on the slider bar, press and hold down the left button, and drag the mouse to the right. Release the mouse button when the appropriate number is displayed. 
     2. Time Period Box 
     To select the appropriate time period units, click mouse on the selection rectangular box, and click again to highlight the appropriate option. 
     3. Interval Box 
     The user can also select specific interval statements in which to set the time period units. These are accessed from the right column of the window and include: ##STR1## 
     Daily Mode has an added option whereby the user may select a specific time of the day: by ##STR2## Click on the number boxes to increment the time of day. Click the mouse to decrement the time of day. The user may also select am or pm. 
     Weekly Mode also has an added option whereby the user may select a specific day of the week: by ##STR3## 
     The user must select one option from each column on the Interval window. Clicking &#34;OK&#34; applies options to the query. Clicking &#34;Cancel&#34; exits the Interval window without saving any changes. 
     b. Interval Query Examples 
     FIG. 42 shows the graph of execution corresponding to the query for: &#34;What happens when the US Financial Future hits 95 and then falls off to 94 sometime during the day?&#34; This query was constructed as follows: 
     SHOW 
     Bar of US repeated from two days ago to two days later; 
     WHEN 
     High of US is at least 95; 
     AND 
     Low of US is at most 94 once later in the day. 
     This illustrates the use of the interval function by selecting interval to add the statement &#34;Once later in the day&#34; to the command WHEN 1004. It can be seen from the graphs in FIG. 42 that US hitting 95 and then falling off to 94 sometime during the same day has occurred three times in the past, and it will be appreciated that when this event has occurred, the price has tended to rise after hitting 94. Knowing this trend may prove to be particularly helpful to a trader who trades in US Financial Futures. 
     4. XMIM System Improvements to the Query Language 
     The XMIM system has a powerful query language which allows the user to create complex queries. For example, the user may ask a whole host of questions concerning spreads and tick-data. Also, in building query conditions, the user can construct queries having an &#34;OR&#34; condition and also an &#34;AND THEN&#34; condition. The language also supports and &#34;IF THEN ELSE&#34; query condition. A conditional operator menu is shown in FIG. 43A. In FIG. 43A, note that the XMIM system utilizes more concise connectors such as &#34;crosses above&#34; and &#34;crosses below&#34;. The language structures and the date, time and bracketing features described below allows for complex conditional searches with near natural language queries. 
     a. Date and Time Features 
     The XMIM allows easily constructed queries concerning calendar week and calendar quarter. The user may ask a wide variety of time related conditions. For example: &#34;. . . and it was a Republican Administration&#34; or &#34;and it was a fair market.&#34; This is accomplished in the XMIM system by maintaining data libraries which correlate dates to these queries. Accordingly, this allows the user to construct queries on a higher level by allowing the user to think in terms of events rather than dates. The XMIM system also utilizes flexible time condition features. For example, the user may specify that the search be limited to particular hours of the day or even the first or last 10 minutes of the trading dates if so desired. 
     b. Bracket Features 
     The XMIM command language adds brackets for nesting and ordering logical operations. This allows the user to group conditions. For example: &#34;. . . and it was {a Friday or a Monday}.&#34; The brackets may also be used with the graph overlay feature to allow the nesting of graph requests. 
     c. Mathematical Functions 
     The XMIM has advanced math functions for enhancing the graphs generated by the system. These functions include multiple day moving averages for smoothing the output graph and the ability to graph the output on an exponential scale. An example of a query utilizing moving averages is shown in FIG. 43B. The graphs shown were generated by the query: &#34;the 18 day moving average of the SP&#39;s crosses above the 50 day moving average.&#34; The query was constructed as follows: 
     
         ______________________________________SHOW    1: bar of SP    2: 50 day average of close of SP    3: 18 day average of close of SP}    Repeated for the previous 50 to the    next 50 daysWHEN    18 day average of close of SP crosses    above 50 day average of close of SP.______________________________________ 
    
     This query illustrates a number of the aforementioned features in the XMIM query language. The use of brackets, the &#34;crosses above&#34; connector and the moving averages, allows the user to generate this complex query with relative ease. 
     5. Schema 
     The XMIM Schema facility is useful in viewing, modifying, and deleting security data in the XMIM system. In addition, it is also the easiest way to create a new security symbol and load individual ASCII (text) data files into the system. This will define for the user what data is available for a specified security and for what time period. For example, if the user typed in &#34;IBM&#34;, the user might see &#34;from: 1/1/77 2:12/31/91, high, low, close volume.&#34; Schema will also allow the user to add a fact or additional data to the database. Schema allows the construction of the user&#39;s own baskets of securities/indexes. Finally, Schema may provide an input/output scale. For example, if the user thinks in terms of 0.30 instead of 0.0030 for D. Marks, and would like to construct queries using 0.30; Schema will show &#34;input: 0.0030 output: 0.30.&#34; 
     FIG. 44 shows the Schema window. Select the Series option to Search, Add, Modify, or Delete a time series. The Modify and Delete functions allow the user to change or delete an existing series after the series has first been selected through the Search function. 
     In FIG. 45, the Search option allows the user to select an existing time series symbol for viewing the series&#39; attributes and the associated data, modifying the series&#39; attributes, or deleting a series. 
     After the security symbol has been selected, the user can view the associated data, modify any of the series&#39; attributes (i.e., trading times, number of digits displayed to the right and left of the decimal point when the data is executed, etc.), or delete the series. 
     a. Add Function 
     FIG. 46 illustrates the series Add Window. When selected from the Series menu, Add creates a new security symbol under the appropriate hierarchial category in which the security will be accessed from the XMIM system. The following is a brief description of each of the fields in the series add window: 
     1) Symbol 
     Click the mouse button in the rectangular box to the right of the Symbol label. To maintain XMIM&#39;s naming conventions, type the new security&#39;s symbol name in all capital letters and press Return. 
     Note that although an unlimited number of characters may be used to specify the symbol name, it is advisable to keep the symbol name under 10 characters. Numbers and the underscore character ( -- ) are allowed in the name, but the first character of the symbol name must be an alpha character. Spaces are not allowed in the symbol name. 
     2) Options 
     If the data file the user is adding to the system is a futures contract, select the Futures toggle button located to the right of the Options label. 
     3) Name 
     Click the mouse button in the rectangular box to the right of the Name label and type the name of the security. This option does allow spaces. Press Return when complete. 
     4) Trades 
     Click the mouse button in the box to the right of the From label next to Trades and type the time this security begins trading in the day. Press Return. Click the mouse button in the box to the right of the To label, type the hour this security stops trading in the day, and press Return. 
     Note that these fields are mandatory if the data file includes tick data, but are not mandatory for daily data. Also note, the user may enter 12 hour time by typing am or pm immediately after the specified hour (i.e., 8:30 am), or the user can represent the hour in 24 hour format (i.e., 1300). 
     5) Category 
     This option allows the user to specify the hierarchical category under which the new security will be accessed in the XMIM system. If the user wishes to add this security directly to one of the categories listed in the right box (i.e., Indices, Economic Indicators, or Monetary Indicators), he leaves TopLevel highlighted in the left box and simply clicks the mouse button on the appropriate category name in the right box. If the user wishes to add this security to a sub-category listed under Equities or Futures, he clicks on the appropriate category name in the left box, then selects the correct sub-category in which to place this security from the right box. In other words, the right column is always the category under which the security will be stored. 
     Only 10 categories will display at one time in each box. Click on the down arrow in the scroll box to the right of each column to view additional category names. 
     Users may click &#34;Cancel&#34; at any point to remove this window from the screen. The security will not be added. Clicking &#34;OK&#34; adds the new symbol to the system and completes the operations Series Add window. 
     b. Modify Function 
     The Modify option will become active only after an existing security has been selected. This option is useful when users wish to change any of the security&#39;s series attributes displayed below. 
     c. Delete 
     As with Modify, the Delete option will only become active after an existing security has been selected. However, if users wish to delete a particular security from the system, any sub-category listings must be deleted first. For example, users will be unable to delete the MktIndices series under Futures if they do not first delete the SP and YX contracts. Once the subject-categories have been deleted, select this option to remove the series completely from the XMIM system. 
     d. Column 
     The second menu label listed on the menu bar of the Schema window is Column (see FIG. 44). Column represents the columns of numbers read from the data file and are grouped under the Price category (open, high, low, close, cash), the Volume category (volume, open interest), or the Fundamental category (book value, capital spending, dividend yield, gross income, etc.). When the data file is initially read (see Facts below) into the hierarchy of the XMIM system, it inherits the columns already associated with the main group under which the file is loaded (i.e., Futures, Equities, Indices, Economic Indicators, Monetary Indicators). However, users have the flexibility to add a new column, or modify or delete any existing column associated with the security&#39;s data file. 
     e. Facts 
     The third label on the menu bar of the Schema window is Facts (see FIG. 44). This is where the location of the security&#39;s data file is specified for reading the data into XMIM. The user can also view and modify a particular security&#39;s data and delete specific columns of data from the XMIM system. A series must first be selected (either through Series-Add or Series-Search) before the Facts options will become active. 
     f. Modify 
     The Modify option provides two useful functions; viewing a particular security&#39;s data file and modifying the data. It also allows the user to change the format of how the data and trading dates are viewed in the XMIM system. Note, the format of the dates in the actual data file will not be affected. After selecting a security (see Series-Search above), click on Facts-Modify. The window shown in FIG. 47 will appear. 
     1) Columns 
     Click on the left Column box to highlight the column data label which desired to be viewed or modified. Notice the right Column box is automatically updated. The user may select any number of labels, in any order desired. Clicking &#34;OK&#34; when complete allows the user to view the data. Depending on the amount of data in the file, it may take a few minutes for the data to be searched and displayed. 
     Please note, if users want to modify the data for a specific year, for example, it is much quicker to display the data by typing the year of interest in the From/To boxes. 
     At this point, the user may click Cancel to exit the Edit Facts window, or may choose to modify any of the data in the file. Simply click the mouse button to the right of the number or date to edit it, backspace over the current numbers, and type the new numbers. When complete, clicking &#34;OK&#34; saves the changes. The user may need to use the down scroll arrow located to the right of the window to see additional information. 
     2) Date 
     Users may wish to change the format of the date column. This option affects how the date is displayed in the XMIM system only and will not affect the actual date format of the data file. Click the mouse in the rectangular box to the right of the Date label and select any of the following formats: 
     10/15/67 
     10/15/1967 
     671015 
     19671015 
     Oct. 15, 1967 
     October 15, 1967 
     15-Oct-67 
     15-Oct-1967 
     15-October-1967 
     Click &#34;OK&#34; when complete to save the changes. 
     3) From/To 
     To change the default beginning and ending dates used to display the security&#39;s data in the XMIM system, click the mouse in the &#34;From&#34; and &#34;To&#34; rectangular boxes. Backspace over the current dates, and type the new dates. Typing in a specific year for the column desired to be modified, for example, greatly speeds up the process of displaying the data. Press Return when complete. Clicking &#34;OK&#34; saves the changes. 
     6. Macros 
     A Macro allows the user to store commonly used studies or technical indicators for subsequent use in queries. A sample Macro window is shown in FIG. 48. Macros may have arguments such that the macro can be applied to different securities, for different time periods, etc. Macros also allow the user to build their own technical indicators, define them, use them, and save them for future use. 
     XMIM supports three types of macros: 
     (1) ATTR (Attribute macros accessed from any Attribute window under the Computed Time Series label). 
     (2) COLUMN (Column macros accessed form any Attribute window under the Technical Ind label). 
     (3) COND (Condition macros accessed from the Condition window). 
     Macros can be created, modified, viewed or encrypted (for security purposes) by selecting the Macros menu from the main XMIM window. 
     Macro editing is accomplished with the XMIM&#39;s edit menu which allows the user to cut, copy, paste or replace text in their macro file. Text must first be highlighted before the edit options can be applied. To highlight text, point and click the mouse at the beginning (or end) of the text to be edited. Hold down the mouse button and drag the mouse over the last character of text desired to be edited. Described below are the edit menu options: 
     a. Cut 
     Cut deletes the highlighted text and copies the text to an XMIM buffer. The user can then use the Paste option (see below) to reinsert the contents of this buffer anywhere in this or any other macro file. The selected text remains in the buffer until users Cut or Copy (see below) again. 
     b. Copy 
     The Copy option is used to copy the highlighted text to an XMIM buffer. The text is not deleted from the file. The user can then use the Paste option to reinsert the contents of the buffer anywhere in this or any other macro, file. The copied text remains in the buffer until another Cut or Copy option is applied. 
     c. Paste 
     The Paste option inserts text from the XMIM buffer (created by selecting text with the Copy or Cut options) at the insertion point in the current or any other macro file. To paste text, click the mouse at the starting point at which it is desired to place the text. Select Edit-Paste. The contents of the XMIM buffer will be inserted from the point where the mouse was clicked. 
     d. Replace 
     The Search and Replace window will appear when Edit-Replace is selected from the Macro-Editor window. This window allows users to search for any character strings in the file and replace it with a different character string (e.g., search for High and replace with Low). This action will affect all occurrences of the character string within the file. 
     While there has been described the preferred embodiments of the invention, numerous modifications and changes will occur to those skilled in the art. It is therefore intended by the appended claims to define all such modifications and changes as fall within the true spirit and scope of the invention.