Patent Publication Number: US-7720886-B2

Title: System for generating an information catalog

Description:
This application is a continuation application claiming priority to Ser. No. 10/806,964, filed Mar. 23, 2004 now U.S. Pat. No. 7,359,909. 
    
    
     BACKGROUND OF THE INVENTION 
     1. Technical Field 
     The present invention relates to a method, computer system, computer program product and graphical interface for generating and displaying an information catalog based on combining technical metadata, business metadata, and presentation metadata. 
     2. Related Art 
     A decision support system exists to provide the tools and facilities to manage and deliver complete, timely, accurate, and understandable business information to authorized individuals for effective business decision making. 
     Data is reaching an all time high in being a critical asset for a business and within a decision support system. The data is distributed throughout multiple systems on multiple platforms and environments. In today&#39;s complex, distributed computer systems, data abounds but is often hard to come by. The data is scattered, protected with different levels of granularity by its owners, and the access capabilities, if available, differ from system to system. Data in one system often has no consistency with data on another in definition, format, and/or timeliness. This makes it difficult to combine or compare data from heterogeneous sources. In many cases, the same data exists in different data stores across multiple applications. This leads to even more problems because the question of which system has the “real” data for a piece of business information cannot be easily answered. 
     Data warehouses in the form of relational database systems address these problems and gather, enrich, and cleanses all this disparate data into a single, consistent source to maximize the value of a company&#39;s data assets. These analytically oriented systems can potentially improve a company&#39;s ability to rediscover and utilize information they already own and derive insight from the wealth of data available, delivering information that&#39;s conclusive, fact-based, and actionable. 
     Unfortunately, current decision support systems for understanding business issues and making business decisions are not adequately supported by existing data warehouses for several reasons. One reason is that the data warehouses do not include information as to how the data is used in computer applications (i.e., software) which support business processes. Another reason is that the data in a complex relational database system having a large number of relational tables is not conveniently accessible to the business-oriented end user (e.g., business manager). The data warehouse may have a system catalog containing metadata that provides information about the data in the data warehouse at a granular level. However, using the system catalog is cumbersome and difficult, since the system catalog is not intended for the business-oriented end user, but rather is intended for the system administrator. 
     Accordingly, there is need for a method, computer system, computer program product and graphical interface which enable business-oriented end users to more readily utilize available data in decision support systems. 
     SUMMARY OF THE INVENTION 
     The present invention provides a method for generating an information catalog relating to a business model, comprising the steps of: 
     accessing technical metadata from a data warehouse, said technical metadata being associated with data used by computer applications, said computer applications supporting business processes of the business model; 
     accessing business metadata from a first source outside of the data warehouse, said business metadata comprising relationships between the business processes and the computer applications, said business metadata further comprising relationships between the computer applications and the technical metadata; 
     accessing presentation metadata from a second source outside of the data warehouse, said second source being independent of the first source, said presentation metadata specifying a presentation format of the technical metadata and business metadata; and 
     applying the presentation metadata to the technical metadata and the business metadata to generate the information catalog, said information catalog comprising the technical metadata and the business metadata in accordance with the presentation format specified by the presentation metadata. 
     The present invention provides a computer system comprising a processor and a computer readable memory unit coupled to the processor, said memory unit including an information catalog compiler that when executed by the processor implements a method for generating an information catalog relating to a business model, said method comprising the computer implemented steps of: 
     accessing technical metadata from a data warehouse, said technical metadata being associated with data used by computer applications, said computer applications supporting business processes of the business model; 
     accessing business metadata from a first source outside of the data warehouse, said business metadata comprising relationships between the business processes and the computer applications, said business metadata further comprising relationships between the computer applications and the technical metadata; 
     accessing presentation metadata from a second source outside of the data warehouse, said second source being independent of the first source, said presentation metadata specifying a presentation format of the technical metadata and business metadata; and 
     applying the presentation metadata to the technical metadata and the business metadata to generate the information catalog, said information catalog comprising the technical metadata and the business metadata in accordance with the presentation format specified by the presentation metadata. 
     The present invention provides a computer program product, comprising a computer usable medium having a computer readable program code embodied therein, said computer readable program code comprising an algorithm adapted to implement a method for generating an information catalog relating to a business model, said method comprising the steps of: 
     accessing technical metadata from a data warehouse, said technical metadata being associated with data used by computer applications, said computer applications supporting business processes of the business model; 
     accessing business metadata from a first source outside of the data warehouse, said business metadata comprising relationships between the business processes and the computer applications, said business metadata further comprising relationships between the computer applications and the technical metadata; 
     accessing presentation metadata from a second source outside of the data warehouse, said second source being independent of the first source, said presentation metadata specifying a presentation format of the technical metadata and business metadata; and 
     applying the presentation metadata to the technical metadata and the business metadata to generate the information catalog, said information catalog comprising the technical metadata and the business metadata in accordance with the presentation format specified by the presentation metadata. 
     The present invention provides a graphical interface of a computer system, comprising package list frame, an object list frame driven by the package list frame, and a detail frame driven by the object list frame, 
     said computer system comprising a processor and a computer readable memory unit coupled to the processor, 
     said memory unit including an information catalog compiler that when executed by the processor implements a method for generating an information catalog relating to a business model, 
     said graphical interface adapted to being navigated by an end user of the method, 
     said method comprising generating the information catalog by applying presentation metadata to technical metadata and business metadata such that the information catalog comprises the technical metadata and the business metadata in accordance with a presentation format specified by the presentation metadata, 
     said technical metadata being associated with data used by computer applications supporting business processes of the business model, 
     said package list frame including selectable applications of said computer applications and selectable associated table creators of tables relating to the technical metadata, 
     said object list frame being adapted to include selectable tables driven by a computer application and associated table creator selected from the package list frame, 
     said detail frame being adapted to include table information relating to a table selected from the object list frame. 
     The present invention advantageously provides a method, computer system, computer program product and graphical interface which enable business-oriented end users to more readily utilize available technical data in decision support systems. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIGS. 1A and 1B  present an illustration of interrelated business processes in support of contract fulfillment, in accordance with embodiments of the present invention. 
         FIG. 2A  depicts a business model showing logical relationships between business processes, computer application supporting the business processes, and tables utilized by the computer applications, in accordance with embodiments of the present invention. 
         FIG. 2B  depicts a physical database schema of the tables utilized by the computer applications, in accordance with embodiments of the present invention. 
         FIG. 3  depicts an overview of generation of an information catalog by an information catalog compiler, in accordance with embodiments of the present invention. 
         FIG. 4  depicts generation of the information catalog by the information catalog compiler, in greater detail than is shown in  FIG. 3 , in accordance with embodiments of the present invention. 
         FIG. 5  depicts a sample eXtensible Markup Language (XML) document or file showing a root element and its attributes, in accordance with embodiments of the present invention. 
         FIG. 6  depicts defined elements in a XML document or file, in accordance with embodiments of the present invention. 
         FIG. 7  depicts XML code that describes the business model of  FIG. 2 , in accordance with embodiments of the present invention. 
         FIG. 8  depicts sample code from the first few significant lines of a eXtensible Stylesheet Language (XSL) file, in accordance with embodiments of the present invention. 
         FIGS. 9A and 9B  provide explanations of numbered lines of  FIG. 8 , in accordance with embodiments of the present invention. 
         FIG. 10  depicts a structured list of XSL stylesheets used for specifying a presentation format for the information catalog, in accordance with embodiments of the present invention. 
         FIG. 11  depicts a sample XSL transformation template relating to rendering Hypertext Markup Language (HTML) tag containing attributes and text, such as the table (&lt;table&gt;) tag, from the XML sources, in accordance with embodiments of the present invention. 
         FIG. 12  depicts a structured list of result files of the information catalog associated with the business model of  FIG. 2A  and database model of  FIG. 2B , in accordance with embodiments of the present invention. 
         FIG. 13  depicts a graphical interface showing the generated information catalog representation that would first appear to an end user for the business model of  FIG. 2A  and database model of  FIG. 2B , in accordance with embodiments of the present invention. 
         FIG. 14  describes the package list frame for the business model of  FIG. 2A  and database model of  FIG. 2B , in accordance with embodiments of the present invention. 
         FIG. 15  describes the object list frame for the business model of  FIG. 2A  and database model of  FIG. 2B , in accordance with embodiments of the present invention. 
         FIG. 16  shows a navigation bar, in accordance with embodiments of the present invention. 
         FIG. 17  shows the form of a glossary term, in accordance with embodiments of the present invention. 
         FIG. 18  depicts links contained in the overview summary page, in accordance with embodiments of the present invention. 
         FIG. 19  depicts the overview summary for the business model of  FIG. 2A , in accordance with embodiments of the present invention. 
         FIG. 20  depicts links contained in the application summary page, in accordance with embodiments of the present invention. 
         FIG. 21  depicts an application summary frame, in accordance with embodiments of the present invention. 
         FIG. 22  depicts the format for table attributes, in accordance with embodiments of the present invention. 
         FIG. 23  is a table describing table attributes, in accordance with embodiments of the present invention. 
         FIG. 24  contains a column summary, in accordance with embodiments of the present invention. 
         FIG. 25  depicts the format of column schema, in accordance with embodiments of the present invention. 
         FIG. 26  is a table describing column attributes, in accordance with embodiments of the present invention. 
         FIG. 27  depicts table index information, in accordance with embodiments of the present invention. 
         FIGS. 28A-28B  are tables describing indices attributes, in accordance with embodiments of the present invention. 
         FIG. 29  depicts relationship format, in accordance with embodiments of the present invention. 
         FIG. 30  is a table describing relationship attributes, in accordance with embodiments of the present invention. 
         FIG. 31  illustrates deprecated tables, in accordance with embodiments of the present invention. 
         FIG. 32  depicts an index page, in accordance with embodiments of the present invention. 
         FIG. 33  illustrates a computer system used for generating an information catalog relating to a business model, in accordance with embodiments of the present invention. 
     
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     The detailed description of the present invention is divided into the following for sections: General Description, eXtensible Markup Language (XML) Processing, eXtensible Stylesheet Language (XSL) Processing, and Information Catalog Output. 
     General Description 
     A decision support system made available to a population of analysts and information gatherers is generally accompanied by numerous predefined reports. However, when an anomaly is identified or a trend needs analysis, the analyst is required to dive into the detailed data behind the reported numbers in an ad-hoc fashion. It is this ad-hoc analysis that makes up the majority of work within the decision support environment, and provides the most business value. However, analysts need some kind of catalog or directory about what data is available to them, what the data means within a given business context, and how a specific piece of data interrelates with other data within the environment. Without this information, the analyst is unaware of the breath and depth of the information available and how to properly use it. Without this information, the analyst cannot find the information needed to answer the business questions and/or may pull the wrong information, resulting in business decisions being driven by invalid information. 
     Accordingly, the present invention provides an information catalog, which is a catalog into the data warehouse. The present invention automates the building of the information catalog, using technical metadata, business metadata, and presentation metadata from independent sources, as will be described infra in conjunction with  FIG. 3 . 
       FIGS. 1A and 1B  (collectively, “FIG.  1 ”) present an illustration of interrelated business processes in support of contract fulfillment, in accordance with embodiments of the present invention.  FIG. 1A  shows relationships between business processes and business applications having supporting technical data and metadata in a data warehouse. A “computer application” (hereinafter, “application”) is defined herein and in the claims as executable computer software such as, inter alia, a program code, program module, etc. intended to be utilized by an end user for performing a function that the end user requires (e.g., a business function relating to business analysis). An application may be a stand-alone computer program or a program module within an application software system. 
     In  FIG. 1A , each box (e.g., “Engagement Management”, “Contract Management”, etc.) represents a business process. The business process ERP in  FIG. 1A  stands for Enterprise Resource Planning. Each business process in  FIG. 1A  has one-to-many computer applications supporting it. See, for example,  FIG. 1B  illustrating that the Engagement Management process is supported by one computer application, namely “app 1”, whereas the Contract Management process is supported by two computer applications, namely “app 2” and “appl 3”. Multiple computer applications may exist for a business process due to computer applications with distinct, complimentary functionality or differing by geographic, business unit, or other boundary. 
     The operational applications (and their data) are those applications that manage the operation of a company&#39;s business. They may be high-volume transaction applications, where fast response time and practically full-time availability are essential, and where, consequently, some frequently used data elements tend to be replicated across applications. Applications that control this data may be too vital and too busy, keeping the business moving, to be interrupted by queries from information gatherers. These applications may be distributed among multiple computers and computer platforms. Thus, the operational data is consolidated into a data warehouse for decision support utilization. 
       FIG. 2A  depicts a business model  10  showing logical relationships between business processes (or subject area), computer application supporting the business processes, and tables utilized by the computer applications, in accordance with embodiments of the present invention.  FIG. 2B  depicts a physical database schema of the tables utilized by the computer applications, in accordance with embodiments of the present invention. There are 3 business processes, 5 computer applications and 9 tables in the business model  10  of  FIGS. 2A and 2B . The 3 business processes are Business Process  1 , Business Process  2 , and Business Process  3 . Business process  1  is supported by computer application  1 , and computer application  1  utilizes Table C1.T1. Business process  2  is supported by computer application  2 , and computer application  2  utilizes Table C2.T1. Business Process  1  is supported by computer applications  3 ,  4 , and  5 . Computer application  3  utilizes Tables C1.T2, C1.T3, and C1.T4. Computer application  4  utilizes Tables C2.T2, C2.T3, and C2.T4. Computer application  4  utilizes Table C2.T5. 
     In  FIGS. 2A and 2B , the tables are represented in the form Cx.Ty and pertain to technical data tables in the data warehouse.  FIG. 2B  shows metadata associated with the technical data for each table, wherein the metadata exists in the system catalog of the data warehouse. The tables Cx.Ty follow a schema/creator-name.table-name nomenclature, and columns (i.e, attributes) are represented as attr_z. Note that all of this information and more (e.g. business definitions within the comments of tables and columns, cardinality of table, cardinality of columns, index detail) is inherently contained within the system catalog of the relational database management system (RDBMS). Cardinality of table pertains to the number of rows the table contains. Cardinality of columns pertains to the number of columns within tables. The symbol represented by reference numeral  12  denotes that the corresponding attribute is a primary key of the table. The text “FK” indicates that the associated attribute is a foreign key of the parent table. The business model example of  FIG. 2  will be utilized in the discussion infra of various aspects of the present invention. 
     The symbol  13  (terminator of line between related tables) between tables in  FIG. 2B  denotes a one-to-many relationship with respect to rows of the related tables. For example, for each row in Table C1.T1 there are one or more corresponding rows in table C1.T2. To illustrate, if a column of Table C1.T1 is for contract number for a contract for the sale of parts, and if Table C1.T2 has both the contract number column and a part number column, then each contract for multiple parts necessitates said one-to-many relationship with respect to the rows of Tables C1.T1 and C1.T2. 
     The tables Cx.Ty relate to data tables in the data warehouse.  FIG. 2B  shows technical metadata associated with the data for each table, and the technical metadata exists in the system catalog of the data warehouse. 
       FIG. 3  depicts an overview of generation of an information catalog  30  by an information catalog compiler  20 , in accordance with embodiments of the present invention. In  FIG. 3 , the information catalog compiler  20 , which is the software that overseers and controls the entire process of generation the information catalog  30 , receives three inputs, namely: technical metadata  21  from a data warehouse embodied in RDBMS  22 , business metadata  24  from an eXtensible Markup Language (XML) file  25 , and presentation metadata  26  from an eXtensible Stylesheet Language (XSL) file  27 . 
     The source of the technical metadata  21  in the RDBMS  22  is the system catalog  23  of the RDBMS  22 . The technical metadata  21  being accessed by the information catalog compiler  20  may be a XML stream in a XML format, as will be discussed infra in conjunction with  FIG. 4 . 
     The business metadata  24  in the XML file  25  is “supplemental information” and is configured to describe a business model such as the business model  10  of  FIG. 2 . The XML file  25  may have other supplemental information such as, inter alia, additional technical metadata to supplement the technical metadata in the system catalog  23  of the RDBMS  22 . 
     The presentation metadata  26  in the XSL stylesheets of the XSL file  27  is configured to specify the presentation format of the technical metadata  21  and of the business metadata  24  in the information catalog  30 . The separation and independence of the presentation metadata  26  from the content (i.e., technical metadata  21  and the business metadata  24 ) allows the content to be flexibly presented in any desired presentation format(s) in the information catalog  30 . 
     The information catalog  30  comprises at least one result file drawn from an Hypertext Markup Language (HTML) file(s)  31 , a PDF file(s)  32 , and a ZIP file(s)  33 , wherein the HTML, PDF, and ZIP formats are non-limiting examples of presentation formats that may be specified in the XSL stylesheets of the XSL file  27 . A PDF file has a Portable Document Format file format that displays or prints as an electronic image as intended and is portable across computer platforms. A ZIP file is one or more files in a compressed form according to a particular format, called a ZIP format. 
     The XML parser  34  and the eXtensible Stylesheet Language Transformations (XSTL) processor  36  are each called by the information catalog compiler  20  as will be explained infra in conjunction with  FIG. 4 . 
       FIG. 4  depicts generation of the information catalog  30  by the information catalog compiler  20 , in greater detail than is shown in  FIG. 3 , in accordance with embodiments of the present invention. The information catalog compiler  20  (see  FIG. 3 ) is a Java-based tool that automates the tedious process of compiling and publishing the information catalog  30 . The compiler  20  performs a catalog crawler step  37  which “crawls” through the system catalog (see system catalog  23  of  FIG. 3 ) of the RDBMS  22 , using Java Database Connection (JDBC) drivers, and produces a XML stream  21  marked up using XML. JDBC is specific to the DB2® relational database system and would be replaced by analogous drivers if another relational database system (e.g., ORACLE®) were utilized. The information in XML stream  21  is then augmented with as much supplemental information in the XML document(s)  25  and XSL stylesheets  27  as is needed to produce a meaningful information catalog  30 . The supplemental information can be in either text or HTML format and is wrapped in part or whole with a robust set of pre or user defined XML tags. Note that the solution relies on open-source XML parsers and thus any imbedded HTML must be “well formed” (e.g. end tags must be explicit, tags must be properly nested, attributes must be quoted). 
     The information catalog compiler  20  exclusively uses open-source tools. It relies on a key feature of XML of describing content and not presentation (like HTML or word processors). By applying different XSL stylesheets  27  to the same XML document  25 , the XML document  25  can be rendered in different presentation formats. With the present information, the information is in the XML document  25 , while the rendering instructions for prescribing presentation format are elsewhere (i.e., in the XSL stylesheets  27 ). In other words, content and presentation are separate. 
     The XML parser  34  parses the source information (i.e., technical metadata in the XML stream  21  and business metadata  24  in the XML document or file  25 ) and generates a source tree  38  from the parsed source information. The source tree  38  represents a structured form of the parsed source information stored in computer memory or storage, wherein the parsed technical metadata  21  and the parsed business metadata  24  are logically linked to each other in the source tree  38 . The XML parser  34  also generates a rules base  40  of rules (i.e., “templates”) derived from the presentation metadata  28  in the XSL stylesheets  27 . 
     In step  42 , the information catalog compiler  20  calls the XSTL processor  36  to apply the templates of the rules base  40  to the source tree  38  to generate a result tree  44 . The XSTL processor  36  traverses the source tree  38  in a recursive descent algorithm, which start at the root node and goes through the source tree  38  until a leaf node is reached, and then comes back through the source tree  38  to the root node. By traversing the entire source tree  38 , the XSTL processor  36  generates the result tree  44 . The XSTL processor  36  determines whether there is a rule in the rules base  40  for each element in the source tree  38 . If there is no rule for the element, then the element is written out as text. If there is more than one rule for the element, then the XSLT processor  36  applies one or more of such rules in accordance with a rule hierarchical scheme. 
     The information catalog compiler  20  uses XML with the XSLT processor to render the information catalog  30  into the various formats. The eXtensible Stylesheet Language (XSL) is used to drive the XSLT processor. XSL is a style sheet language for documents marked up using XML and is used to describe, utilizing the XSL formatting vocabulary, how an XML source document is transformed into another document (e.g. HTML, PDF, ZIP files). The result tree  44  is a precursor to the information catalog  30  and is stored in computer memory or storage. 
     Details relating to various aspects of  FIG. 4  will next be discussed. 
     XML Processing 
       FIG. 5  depicts a sample XML document or file showing a root element ‘info-catalog’ and its attributes, in accordance with embodiments of the present invention. For example, the attribute ‘rootname’ has the value “ICCExample”. Generally, the components of a XML document comprise: tags, elements, and attributes. A tag is the text between the left angle bracket (&lt;) and the right angle bracket (&gt;). There are starting tags (such as &lt;info-catalog&gt;) and ending tags (such as &lt;/info-catalog &gt;). An element is the starting tag, the ending tag, and everything in between. An attribute is a name-value pair inside the starting tag of an element. In the example, of  FIG. 5 , ‘rootname’ is an attribute of the &lt;info-catalog&gt; element. Any embodiment of the invention may choose to use different attributes and or input flags. An existing embodiment of the invention has 36 distinct attributes for the &lt;info-catalog&gt; XML element. The 36 attributes are used to control what gets produced, look and feel characteristics, and common headers and footers. The bolded attributes in  FIG. 5  (e.g., ‘rootname’) can be changed from a default value, whereas the unbolded attributes (e.g. ‘xmlns:xsi’) cannot be changed. 
     The attribute ‘rootname’ specifies the directory to write the rendered output to. 
     The attribute ‘documenttitle’ specifies the title to be placed near the top of the overview summary file. The XSL Stylesheet decides the placement of the title. Currently the title is placed as a centered, level-one heading directly beneath the upper navigation bar. The title may contain HTML tags and white space, though if it does, it must be entered as a unique XML element or entered through the command line, enclosed in quotes (quotes are optional if supplied in the initialization file). Any internal quotation marks within title will have to be escaped (e.g. \”). 
     The attribute ‘header’ denotes header text to be used at the top of each document. This is intended for information such as the version number or generation date. 
     The attribute ‘contact’ denotes an Email contact address. By including this attribute, the XSL Stylesheets will generate a contact link at the bottom of each HTML detail page. If this attribute is omitted, then the contact link will not be generated. 
     The attribute ‘columnXRef’ denotes that for each column output as part of each table detail page, a cross reference can be generated to show and link every place where this column name is used within the data warehouse. Similar to the ‘contact’ attribute, omitting the ‘columnXRef’ attribute will produce output that does not cross reference at the column level. 
     The attribute ‘sortByColumnName’ allows a user to specify that columns within tables should be sorted alphabetically instead of as they appear within the physical table structure. 
     All &lt;info-catalog&gt; XML element attributes can alternatively be specified in the command line or within a process initialization file. This is a convenience function to allow overriding values for specific runs without having to edit the XML. The order of precedence is: 1) command line; 2) initialization file; and 3)&lt;info-catalog&gt; XML element attribute. 
     Along with &lt;info-catalog&gt; XML element attributes, there are a few XML elements that are also defined and illustrated in the XML document or file of  FIG. 6 , in accordance with embodiments of the present invention. The defined elements in  FIG. 6  include: &lt;creators&gt;, &lt;abstract&gt;, &lt;description&gt;, &lt;footer&gt;, and &lt;bottom&gt;. These are examples of elements that control the content (e.g. the &lt;creator&gt; element limits the tables that will be included based on the table&#39;s creator name) and “look &amp; feel” of the resulting Information Catalog (e.g. the &lt;footer&gt; element causes a standard footer be placed at the bottom of all generated output pages). 
     The &lt;creators&gt; element specifies the list of table creators that the information catalog should be generated for. If the &lt;creators&gt; element is omitted, then the compiler pulls all tables within the DB2® subsystem with the exception of the system catalog tables themselves. If the &lt;creators&gt; element is entered through the command line, then this list should be comma separated and enclosed in double quotes. 
     The &lt;abstract&gt; element is a brief abstract describing the data warehouse layer the information catalog was generated for. The XSL Stylesheet decides the placement of the text of the abstract. Currently the abstract is placed under the title on the overview summary page of the detail frame (see infra  FIG. 13  and description thereof). In the example described herein, the &lt;abstract&gt; element was omitted; thus the information catalog compiler generated a default abstract based on the document title. 
     The &lt;description&gt; element may contain a description of the data warehouse&#39;s overall functionality. Any standard, well-formed HTML may be contained within the &lt;description&gt; element, including lists, tables, images, links, or multimedia objects. 
     The &lt;footer&gt; element specifies the footer text to be placed at the bottom of each output file. The XSL stylesheet decides the placement of the footer text. The footer text may be placed under the lower navigation bar. The footer may include HTML tags and white space. If entered through the command line, the footer must be enclosed in quotes. However, quotes are optional if supplied in the initialization file. Any internal quotation marks within the footer will have to be escaped (e.g. \”). 
     The &lt;bottom&gt; element denotes optional text to follow the footer. The &lt;bottom&gt; element, used in conjunction with the XSL Stylesheets, allows flexibility ending pages of the information catalog. This flexibility is useful for disclaimers, company logos, copyright information, etc. Business process and application XML elements may exists in the same XML document as the root or one or more distinct XML documents. This helps enable organizations, which may already have business processes and application descriptions documented in HTML (“well-formed” HTML tags will validly parse through an XML parser) or other electronically readable format, reuse existing content. 
     Note that if multiple XML documents are used, each must be contained in a single element. That single element is called the root element of the document, and it contains all the text and any other elements in the document. For each of the subsequent documents, the name of the root element is unimportant. The root element ‘info-catalog’ was illustrated supra in conjunction with  FIG. 5 . 
     The XML specification requires a parser to reject any XML document that doesn&#39;t follow the basic rules. Most HTML parsers will accept sloppy markup, marking a guess as to what the author of the document intended. To avoid ambiguity, the creators of XML decided to enforce document structure from the beginning. Therefore, HTML embedded within XML elements used by the information catalog compiler must follow XML “well-formed” rules, including: 1) XML elements cannot overlap; 2) end tags are required; 3) XML elements are case sensitive; and 4) attributes must have quoted values. These well-formed rules will one next explained. 
     A first well-formed rule is that XML elements cannot overlap. For example, the following XML code Table 1 is invalid. 
                             TABLE 1                          &lt;p&gt;                         &lt;b&gt;XML is a &lt;i&gt;really&lt;/b&gt; useful technology &lt;/j&gt;                         &lt;/p&gt;                        
That is, if a &lt;j&gt; element begins inside a &lt;b&gt; element, then the &lt;j&gt; element must end inside the &lt;b&gt; element. In contrast, the following XML code in Table 2 is valid.
 
     
       
         
           
               
               
             
               
                   
                 TABLE 2 
               
               
                   
                   
               
             
            
               
                   
                 &lt;p&gt; 
               
            
           
           
               
               
            
               
                   
                 &lt;b&gt;XML is a &lt;i&gt;really&lt;/j&gt; useful 
               
               
                   
                 technology.&lt;/b&gt; 
               
            
           
           
               
               
            
               
                   
                 &lt;/p&gt; 
               
               
                   
                   
               
            
           
         
       
     
     An XML parser will accept only the preceding markup; the HTML parsers in Web browsers will accept both. 
     A second well-formed rule is that end tags are required. For example, the following XML code in Table 3 is invalid. 
                             TABLE 3                          &lt;p&gt;my first paragraph...           &lt;p&gt;my second paragraph...                        
The markup is not legal because there are no end paragraph (&lt;/p&gt;) tags. While this is acceptable in HTML (and, in some cases, SGML), an XML parser will reject it. If an element contains no markup at all it is called an empty element; the HTML break (&lt;br&gt;) and image (&lt;img&gt;) elements are two examples. In empty elements in XML documents, you can put the closing slash in the start tag. The two break elements and the two image elements below mean the same thing to an XML parser. In contrast, the following XML code in Table 4 is valid:
 
     
       
         
           
               
               
             
               
                   
                 TABLE 4 
               
               
                   
                   
               
             
            
               
                   
                 p&gt;my first paragraph...&lt;/p&gt; 
               
               
                   
                 &lt;p&gt;my second paragraph...&lt;/p&gt; 
               
               
                   
                 &lt;br/&gt; 
               
               
                   
                 &lt;br&gt;&lt;/br&gt; 
               
               
                   
                 &lt;img src=“../img/c.gif”/&gt; 
               
               
                   
                 &lt;img src=“../img/c.gif”&gt;&lt;/img&gt; 
               
               
                   
                   
               
            
           
         
       
     
     A third well-formed rule is that XML elements are case sensitive. In HTML, &lt;h1&gt; and &lt;H1&gt; are the same; in XML, they are not. If one attempts to end an &lt;h1&gt; element with a &lt;/H1&gt; tag, the XML parser will return an error. 
     A fourth well-formed rule is that attributes must have quoted values. There are two rules for attributes in XML documents, namely: 1) attributes must have values; and 2) the attribute values must be enclosed within quotation marks. Comparing the invalid and valid code in the examples below, the markup at the top is legal in HTML, but not in XML. To do the equivalent in XML, the attribute is given a value and the value is enclosed in quotes. The invalid XML code in Table 5 is: 
     
       
         
           
               
               
             
               
                   
                 TABLE 5 
               
               
                   
                   
               
             
            
               
                   
                 &lt;!−− NOT legal XML markup −−&gt; 
               
               
                   
                 &lt;ol compact&gt; 
               
               
                   
                   
               
            
           
         
       
     
     The valid XML code in Table 6 is: 
                             TABLE 6                          &lt;!−− legal XML markup −−&gt;           &lt;ol compact=“yes”&gt;                        
Either single or double quotes may be used, so long as said use of single or double quotes is consistent. If the value of the attribute contains a single or double quote, then the other kind of quote may surround the value (as in name=“Doug&#39;s car”), or one may use the entities “&amp;quot;” for a double quote and “&amp;apos;” for a single quote.
 
     An entity is a symbol (e.g., “&amp;quot;”) that the XML parser replaces with other text, such as replacing “quot;” with”. The XML specification defines five standard entities that can be used in place of various special characters. These five standard entities are: &amp;lt; (for the less-than sign); &amp;gt; (for the greater-than sign); &amp;quot; (for a double-quote); &amp;apos (for a single quote or apostrophe); and &amp;amp (for an ampersand.). 
     Along with the aforementioned five standard entities, the information catalog compiler has defined a number of additional entities. Anywhere the XML processor finds one of these additional entities, the information catalog compiler replaces the additional entity with defined text. The additional entities include: &amp;title; &amp;version; &amp;sysdate; and &amp;systime. 
     The &amp;title; entity inserts, in-line, the information catalog&#39;s title as passed to the compiler through the XML or command line. 
     The &amp;version; entity inserts, in-line, the information catalog&#39;s version/release number as passed to the compiler through the XML or command line. The text has no special internal structure. 
     The &amp;sysdate; entity inserts, in-line, the system date when the compiler was run. The date is in the format identified by the locale that runs the compiler. 
     The &amp;systime; entity inserts, in-line, the system date and time when the compiler was run. The date and time is in the format identified by the locale that runs the compiler. 
       FIG. 7  depicts XML code that describes the business model discussed supra in conjunction with  FIG. 2 , namely Business Process  3  and associated computer applications  3 - 5 , in accordance with embodiments of the present invention. The XML document illustrated by  FIG. 7  can contain multiple &lt;subjectarea&gt; elements and each subject area can contain multiple &lt;application&gt;s. 
       FIG. 7  illustrates two alternative mechanisms for associating tables of the data warehouse with computer applications. A first mechanism is via the &lt;label&gt; element, which tells the information catalog compiler that the table to application relationship exists within the &lt;label&gt; attribute in the system catalog; i.e., the system catalog recognizes &lt;label&gt;. The &lt;label&gt; element in  FIG. 7  links to all tables known by the system catalog to have a label of APP-1. A second mechanism is that tables can be associated with an application using the &lt;tablelist&gt; element, which specifies explicit table names of tables in the data warehouse. For example, the &lt;tablelist&gt;element in  FIG. 7  establishes an application called “Operational Application 4” associated with three tables named T2, T3, and T4, each table having &lt;creator&gt;C2. 
     The XML code in  FIG. 7  comprises the following nodal structure. The element “subject area” has value of “Business Process/Subject Area”. The “subject area” element has a child node, called “application”. The “application” node has 4 nodes: name (has value “Operational Application 1”), abbr (has value “APPL-1”), label (has value “APPL-1”), and desc (has no value). The node “desc” has a paragraph (&lt;p&gt;) child node under it. 
     The nodal structure of the XML code of the XML file(s)  25  is transformed by the XML parser  34  into the source tree  38  (see  FIG. 4 , described infra). The information catalog compiler  20  calls the XML parser  34 , and the XML parser  34  builds the source tree  38  in the computer&#39;s logical memory. 
     XSL Processing 
     Once the technical metadata and business metadata is collected as described supra, XSL (eXtensible Style Language) is used to render the collected technical metadata and business metadata into multiple formats. XSL itself is a transformation language and a formatting language used to automate the conversion of one XML document into another XML document. The transformation language provides elements that define rules for transforming the source XML document. The formatting language provides elements that define formatting objects used to build the target XML document. 
     XSTL is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSTL, XSL includes an XML vocabulary for specifying formatting. XSL specifies the styling of an XML document by using XSTL to describe how the document is transformed into another XML document that uses the formatting vocabulary. 
     XSTL Stylesheets are XML documents. The XSTL namespace has the URI http://www.w3.org/1999/XSL/Transform and is used to identify semantically significant elements. 
     The XSTL Stylesheets used by the invention render the information by having a master stylesheet, InfoCatalog.xsl, “call” other stylesheets to render the particular artifact. Applying the root element, &lt;info-catalog&gt;, with different “modes” performs the “call”. For example, to build table summary pages for each table within the data warehouse layer the following XSL is specified in the InfoCatalog.xsl file: &lt;xsl:apply-template select=“info-catalog” mode=“build-table-summary”/&gt;. By convention, the template that matches this mode is contained within the XSL file build-table-summary.xsl. To illustrate how the output is rendered, the  FIG. 8  depicts sample XSL code from the first few significant lines of the build-table-summary.xsl file, in accordance with embodiments of the present invention.  FIGS. 9A and 9B  (collectively, “FIG.  9 ”) provide explanations of numbered lines  1 - 19  of  FIG. 8 , in accordance with embodiments of the present invention. 
     The master stylesheet, InfoCatalog.xsl, includes other XSLT stylesheets using the xsl:include element. The following two xsl:include elements in Table 7 have an href attribute whose value is a URI reference identifying the stylesheet to be included. 
     
       
         
           
               
               
             
               
                   
                 TABLE 7 
               
               
                   
                   
               
             
            
               
                   
                 &lt;xsl:include href=“icc-variables.xsl”/&gt; 
               
               
                   
                 &lt;xsl:include href=“build-overview-summary.xsl”/&gt; 
               
               
                   
                   
               
            
           
         
       
     
     A structured list of XSL stylesheets for the example described herein are shown in  FIG. 10 , in accordance with embodiments of the present invention. Whereas some XSL stylesheets listed in  FIG. 10  exist to render specific artifacts, such as the overview summary HTML page, other stylesheets are generic rendering instructions that are and can be used by all XSL Stylesheets, namely the stylesheets of html-xml-trans.xsl, icc-styles.xsl, icc-variables.xsl, xml-fo-trans.xsl, and xslt-utilities. 
     The html-xml-trans.xsl stylesheet describes a set of transformations that writes out HTML tags embedded within XML elements. 
     The icc-styles.xsl stylesheet contains common styles such as the common navigator bar, table layouts, header and footer styles, etc. 
     The icc-variables.xsl stylesheet contains variables used by the different stylesheets. These variables can be used to set company or organization names, copyright text, etc. 
     The xml-fo-trans.xsl stylesheet describes a set of transformations that convert HTML tags to their corresponding Format Object tags to be rendered into PDF documents. 
     The xslt-utilities stylesheet XSLT utilize convenience utilities to perform functions such as substring. Other convenience functions are likewise delivered in Java classes. These function include copying files, getting the platform specific file separator, and retrieving formatted dates. 
     Examples of the transformations of the html-xml-trans.xsl stylesheet are shown infra. Consider an HTML tag that does not contain attributes, such as the paragraph (&lt;p&gt;) tag. The transformation may be as simple as the lines of code in Table 8. 
     
       
         
           
               
               
             
               
                   
                 TABLE 8 
               
               
                   
                   
               
             
            
               
                   
                 &lt;!−− 
               
            
           
           
               
               
            
               
                   
                 ******************************************************* 
               
               
                   
                 template to process p (paragraph) element 
               
               
                   
                 *******************************************************−−&gt; 
               
               
                   
                 &lt;xsl:template match=“p”&gt; 
               
               
                   
                 &lt;p&gt; &lt;xsl:apply-templates select=“*|text( )”/&gt; &lt;/p&gt; 
               
               
                   
                 &lt;/xsl:template&gt; 
               
               
                   
                   
               
            
           
         
       
     
     When an XML element, including the root element, contains a &lt;p&gt; element, the above template is matched which: 1) renders the opening &lt;p&gt; tag; 2) applies template for ALL (*) XML elements or text that are embedded in the &lt;p&gt; element; and renders the closing &lt;/p&gt; tag.  FIG. 11  depicts a transformation template relating to an HTML tag containing attributes, such as the table (&lt;table&gt;) tag. When an XML element, including the root element, contains a &lt;table&gt; element, the transformation template in  FIG. 11  is matched which: 
     1) renders the opening &lt;table&gt; tag; 
     2) sets up a loop to process each attribute of the &lt;table&gt; element (line  3 : &lt;xsl:for-each select=“@*”&gt;, XSL shorthand for an attribute is the @ sign); 
     3) for each attribute the xsl:attribute element is used to add the attribute to the result elements; 
     4) sets up a loop to process each &lt;table-row&gt; or &lt;tr&gt; element (line  8 ); 
     5) renders the opening &lt;tr&gt; tag (line  9 ); 
     6) sets up a loop to process each attribute of the &lt;table-row&gt; or &lt;tr&gt; element (line  10 - 14 ); 
     7) sets up a loop to process each &lt;table-cell&gt; or &lt;td&gt; element (line  16 ); 
     8) renders the opening &lt;td&gt; tag (line  17 ); 
     9) sets up a loop to process each attribute of the &lt;table-cell&gt; or &lt;td&gt; element (line  18 - 22 ); 
     10) applies template for ALL (*) XML elements or text that are embedded in the &lt;table-cell&gt; or &lt;td&gt; element (line  24 ); 
     11) renders all end tags and closes all xsl:for-each tags; and 
     12) closes the xsl:template tag. 
     Information Catalog Output 
     The information catalog  30  of  FIG. 4  is a set of result files.  FIG. 12  depicts a structured list of result files of the information catalog associated with the business model  10  of  FIG. 2A  and database model of  FIG. 2B , in accordance with embodiments of the present invention. The result files of  FIG. 12  are structured in accordance with the 5 computer applications (APPL-1, APPL-2, APPL-3, APPL-4, APPL-5) and 10 associated tables (C1,T1, C1.T2, C1.T3, C1.T4, C2.T1, C2.T2, C2.T3, C2.T4, C2.T5) of the business model  10 . 
     The XSL stylesheets listed in  FIG. 10  are used to generate the results files of the information catalog in  FIG. 12 . For example, the “build-overview-summary.xsl” stylesheet in  FIG. 10  is used to generate the “overview-summary.html” result file in  FIG. 12 . As another example, the “build-package-list.xsl” stylesheet in  FIG. 10  is used to generate the “package-frame.html”result file in  FIG. 12 . 
     The end user enjoys the benefit of a graphical interface, which may be interactively navigated to display characteristics of the business model of interest, such as the business model  10  of  FIG. 2 . Such interactive navigation by the end user involves execution of the result files of the information catalog as will be next explained. 
     The graphical interface navigated by the end user is an integrated group of frames in accordance with the following schematic representation. 
     
       
         
         
             
             
         
       
     
     As the illustration above shows, there are three primary frames: package list frame, an object list frame, and a detail frame. 
     The package list frame is used to update the object list frame with tables or computer applications. Thus the package list frame drives the object list frame as indicated by the down arrow pointing from the package list frame to the object list frame. 
     The object list frame is used to update the detail frame with a table or application, depending on whether tables or applications are selected by the end user in the package list frame. Thus the object list frame drives the detail frame as indicated by the right arrow pointing from the object list frame to the detail frame. 
     The detail frame contains the detailed pages associated with the selected table, the selected application, or other detailed information. The alternative detailed displayable information in the detail frame includes content as shown in Table 9. 
     
       
         
           
               
             
               
                 TABLE 9 
               
               
                   
               
             
            
               
                 1) An overview summary page, which is the default page for the 
               
               
                 detail frame of the information catalog. The overview summary page can 
               
               
                 also always be displayed by selecting overview from any navigation bar. 
               
               
                 2) Application summary pages, which contain source application 
               
               
                 specific detail. 
               
               
                 3) Table summary pages, which contain table specific details. 
               
               
                 4) A Deprecated Table page that lists tables within the data warehouse 
               
               
                 that are not recommended for use, due to improvements, and a 
               
               
                 replacement table is usually given. Deprecated tables may be removed in 
               
               
                 future implementations of the data warehouse layer. The Deprecated Table 
               
               
                 page can be displayed by selecting Deprecated from any detail 
               
               
                 page&#39;s navigation bar. 
               
               
                 5) An Index page which contains an alphabetic list of all tables, 
               
               
                 columns, indices, 7 etc. This page can be displayed by selecting Index 
               
               
                 from any navigation bar. 
               
               
                 6) A Help page which displayable by selecting Help from any navigation 
               
               
                 bar. 
               
               
                   
               
            
           
         
       
     
     1) An overview summary page, which is the default page for the detail frame of the information catalog. The overview summary page can also always be displayed by selecting overview from any navigation bar. 
     2) Application summary pages which contain source application specific detail. 
     3) Table summary pages, which contain table specific details. 
     4) A Deprecated Table page that lists tables within the data warehouse that are not recommended for use, due to improvements, and a replacement table is usually given. Deprecated tables may be removed in future implementations of the data warehouse layer. The Deprecated Table page can be displayed by selecting Deprecated from any detail page&#39;s navigation bar. 
     5) An Index page which contains an alphabetic list of all tables, columns, indices, etc. This page can be displayed by selecting Index from any navigation bar. 
     6) A Help page which can be displayed by selecting Help from any navigation bar. 
       FIG. 13  depicts a graphical interface showing the generated information catalog representation that would first appear to an end user for the business model  10  of  FIG. 2 , in accordance with embodiments of the present invention. The information catalog representation of  FIG. 13  depicts the package list frame  51 , the object list frame  52 , and the detail frame  53 . Note that  FIG. 13  does not literally show the information catalog, but rather a representation thereof. The actual information catalog is the set of result files listed in  FIG. 12 . The representation of  FIG. 13  is generated by executing the result files of  FIG. 12 . For example, execution of the overview-summary.html file of  FIG. 12  results in the overview summary view in the detail frame  53  of  FIG. 13 . 
     In  FIG. 13 , the package list frame  51  is used to update the object list frame  52  with tables or computer applications. The end user selects either tables or applications. For selection of tables, the tables include: all tables within the data warehouse layer that the information catalog has been generated for, only tables populated from a specific source application, only tables with a specific creator name, or all source applications that feed the data warehouse layer. The package list frame itself contains: catalog title, link to all tables, link to all source applications, link to source application specific tables, by application abbreviation, link to tables with specific creator name.  FIG. 14  describes the package list frame  51  for the business model  10  of  FIG. 2 , in accordance with embodiments of the present invention. 
     In  FIG. 13 , the object list frame  52  is used to list all source application that feed the data warehouse layer, all tables names within data warehouse layer, all data warehouse layer tables that are fed from a specific computer application, or all data warehouse layer tables with a specific table creator name. Selections within the object list frame  52  are used to update the detail frame with the selected table or application detail page. Note that information will not wrap in this frame; instead, horizontal scroll bars are used.  FIG. 15  describes the object list frame  52  for the business model  10  of  FIG. 2A  and database model of  FIG. 2B , in accordance with embodiments of the present invention. 
     In  FIG. 13 , the detail frame  53  contains the detailed pages associated with the selected table, the selected application, or other detailed information. Before looking at each one of the detail frame pages, the top and bottom navigation bars will be examined. These are common for all detail pages, only varying by enabled options or semantically based on the type of detailed page being displayed. 
       FIG. 16  shows a navigation bar, in accordance with embodiments of the present invention. As with all rendered output, the “look and feel” of the navigator bar can be changed to meet individual needs and/or organizational design standards by changes to either the HTML Cascading Stylesheet(s) and/or the XSL Stylesheets used to render the HTML. 
     Attributes of XML element &lt;info-catalog&gt;, or command line input, can used to include or exclude either the navigation bar or components of the bar (e.g. Deprecations, index, help). Components of the navigation bar include: Tables (or Applications), Deprecated, Index, Help, Prev/Next (table or application or index letter), and Frames/No Frames. 
     The Overview page selectable from the navigation bar is the front page of this information Catalog document and provides a list of all source applications that feed the data warehouse layer that the information catalog was generated for, with a summary for each. The end user can subsequently drill into each application to get additional information and a listing of the tables that are associated with each application. 
     The Tables (or Applications) page selectable from the navigation bar includes two distinct types of documents, namely Application Summary documents and Tables Summary documents. In the Application Summary document, each source application has a page that contains descriptive information on the application and a list of table it feeds the data warehouse layer. In the Table Summary document, each table has a page that contains a list of its table attributes, column descriptions, column schema, indices, relationships, and notes on query construction using this table. 
     The Deprecated Table page lists all of the Data Warehouse Layer&#39;s tables that have been deprecated. A deprecated table is not recommended for use, generally due to improvements, and a replacement table is usually given. Deprecated tables may be removed in future implementations of the data warehouse layer. 
     The Index page(s) contains an alphabetic list of all tables, columns, indices, etc. 
     The Help page(s) contain help for the generated information catalog. The compiler will generate a default help page; however, help can be overridden or omitted. 
     The Prev/Next (table or application or index letter) links transition the end user to the next or previous table or application summary page or index page. 
     The Frame/No Frame links show and hide the HTML frames. All pages are available with or without frames. 
     A pop-up glossary is common for all detail pages. Within detail pages, an attribute column name may be followed with a superscript question mark (?). This indicates that a definition for this attribute exists and can be displayed in a pop-up HTML window by selecting the question mark. The Glossary definitions are stored in the “glossary” sub directory under the root directory and display the information in a window that looks at the picture below. As with all rendered output, the “look and feel” of the popup glossary definitions can be changed to meet individual needs and/or organizational design standards by changes to either the HTML Cascading Stylesheet(s) and/or the XSL Stylesheets used to render the HTML.  FIG. 17  shows the form of a glossary term, in accordance with embodiments of the present invention. 
     The default page for the generated information catalog detail frame is the Overview Summary page, which contains: 1) a title; 2) a description of the data warehouse layer overall function for the data warehouse layer that the information catalog was generated for; 3) Source Application Hierarchy; and 4) Repeating table for each functional area, containing: (a) the source application&#39;s abbreviation, (b) the source application&#39;s name, and a detailed business description of the functionality provided by the source application.  FIG. 18  depicts links contained in the overview summary page, in accordance with embodiments of the present invention. 
     The “look and feel” of the Overview Summary can be changed to meet individual needs and/or organizational design standards by changes to either the HTML Cascading Stylesheet(s) and/or the XSL Stylesheets used to render the HTML.  FIG. 19  depicts the Overview Summary for the business model  10  of  FIG. 2A  and database model of  FIG. 2B , in accordance with embodiments of the present invention. 
     For each source application that feeds the data warehouse layer that the information catalog was generated for, an Application Detail page will be generated. The Application Detail page includes information as shown in Table 10. 
     
       
         
           
               
             
               
                 TABLE 10 
               
               
                   
               
             
            
               
                 1. The business process/functional area the source application support. 
               
               
                 2. The Application abbreviation and name. 
               
               
                 3. Application attributes, including: 
               
            
           
           
               
               
            
               
                   
                 (1) Update frequency for the data from the source application into the 
               
               
                   
                  data warehouse layer. 
               
               
                   
                 (2) Transformation rule applied to data from the source application 
               
               
                   
                  into the Data Warehouse Layer. 
               
               
                   
                 (3) Extract method used to pull the data from the source application. 
               
               
                   
                 (4) Population method used to populate the data warehouse layer. 
               
            
           
           
               
            
               
                 4. A detailed business description of functionality provided by source 
               
               
                 application. 
               
               
                 5. A table listing each table in the data warehouse layer populated from 
               
               
                 the source application. This table contains: 
               
            
           
           
               
               
            
               
                   
                 (1) The table&#39;s creator and table name. 
               
               
                   
                 (2) A detailed business description of the content and purpose of 
               
               
                   
                 the table within the source application and/or data warehouse layer. 
               
               
                   
                   
               
            
           
         
       
     
       FIG. 20  depicts links contained in the application summary page, in accordance with embodiments of the present invention. 
     The “look and feel” of the Application Summary can be changed to meet individual needs and/or organizational design standards by changes to either the HTML Cascading Stylesheet(s) and/or the XSL Stylesheets used to render the HTML.  FIG. 21  depicts an Application Summary frame, in accordance with embodiments of the present invention. 
     For each table contained in the data warehouse layer that the information catalog was generated for, a Table Detail page will be generated. The Table Detail page includes content as shown in Table 11. 
     
       
         
           
               
               
             
               
                 TABLE 11 
               
               
                   
               
             
            
               
                 1. 
                 The Table Name 
               
               
                 2. 
                 Business description of the table 
               
               
                 3. 
                 Table attributes 
               
               
                   
                 (1) Cardinality (number of rows) 
               
               
                   
                 (2) Number of columns 
               
               
                   
                 (3) Number of key columns 
               
               
                   
                 (4) Number of pages 
               
               
                   
                 (5) Percent of pages 
               
               
                   
                 (6) Number of parent relationships table participates in. 
               
               
                   
                 (7) Number of children tables 
               
               
                   
                 (8) Database name 
               
               
                   
                 (9) Tablespace name 
               
               
                   
                 (10) Created time-stamp 
               
               
                   
                 (11) Last altered time-stamp 
               
               
                   
                 (12) Time-stamp when statistics were last run for the table. 
               
               
                 4. 
                 Links to each section of the page 
               
               
                 5. 
                 Column List with business description of each column 
               
               
                   
                 and a cross reference to other data warehouse tables where 
               
               
                   
                 the column is also used. 
               
               
                 6. 
                 Column schema 
               
               
                 7. 
                 Indices 
               
               
                 8. 
                 Relationships 
               
               
                 9. 
                 Notes 
               
               
                   
               
            
           
         
       
     
     The top of every Table Summary page contains the name of the table, in the format of “Table-Creator.Table-Name”. Following the table name is the business description of the table. This description begins with what is in the DB2® system catalog followed by any additional information that may have been provided by the user that generated the Information Catalog. If the table has been deprecated, this will also be noted along with the name and link to any replacement table(s). A deprecated table is identified within a &lt;deprecated-list&gt; XML element. 
     Table attributes are collected based on statistics gathered by the DB2® system related to the table itself.  FIG. 22  depicts the format for table attributes, in accordance with embodiments of the present invention. The table attributes also include the information shown in Table 23, in accordance with embodiments of the present invention. Following the table attributes section are a series of links to the different areas of the Table Detail page. 
     Following the links section, a table is displayed with each column contained in the table along with the business description of the column. By default the columns are displayed in the physical order they appear in the table. By setting the sortByColum-nName attribute to “yes” in the info-catalog XML element or the input parameter (-sortByColumnName) the columns will be displayed in alphabetical order. 
     Additionally, cross-reference information can be included. This cross-reference is a list of all tables within the data warehouse layer that contains a column with the same name. Each cross-reference table is linked to the Table Detail page for the particular table. By default this cross-reference information is included; however it can be omitted setting the columnXRef attribute of the info-catalog XML element to “no” or specifying the input parameter, -nocolumnXRef.  FIG. 24  contains a Column Summary, in accordance with embodiments of the present invention. 
     The next section contains the table column schema information. Like the column list section, this section, by default, displays the columns in the physical order they appear in the table. By setting the sortByColumnName attribute to “yes” in the info-catalog XML element or the input parameter (-sortByColumnName) the columns will be displayed in alphabetical order.  FIG. 25  depicts the format of column schema and  FIG. 26  depicts column schema, in accordance with embodiments of the present invention. 
       FIG. 27  depicts table index information and  FIGS. 28A-28B  depict indices attributes, in accordance with embodiments of the present invention. 
     The relationship section contains information pertaining to how a table inter relates with other tables within the data warehouse layer. Relationships provide users of the information catalog vital insight on how to write join operations. These relationships may be explicit, defined in the DB2® system catalog, or implicit, provided to the information catalog compiler at run time, using XML elements.  FIG. 29  depicts relationship format and  FIG. 30  depicts relationship attributes, in accordance with embodiments of the present invention. 
     The notes section contains any processing notes or points of interest entered as XML elements in regards to the specific table. 
     The deprecated table page provides a list of all tables that are deprecated, the business description for each table, and a cross-referenced of all tables within the data warehouse layer that should be used instead of the deprecated table. Each cross-reference table is linked to the Table Detail page for the particular table. A deprecated table is not recommended for use, generally due to improvements, and a replacement table is usually given. Deprecated tables may be removed in future implementations of the Data Warehouse layer. This page can be displayed by selecting Deprecated from any detail page&#39;s navigation bar.  FIG. 31  illustrates deprecated tables, in accordance with embodiments of the present invention. 
     An Index page contains an alphabetic list of all source applications, tables, columns, and indices. All index information can be contained in a single page, split to multiple pages based on letter, or omitted, based on options used when the compiler is invoked. Setting the splitindex attribute of the info-catalog XML element to “yes” or specifying the “-splitindex” input parameter splits the index file into multiple files, alphabetically, one file per letter, plus a file for any index entries that start with non-alphabetical characters. Note that if the entire index is placed in a single file a navigation tag of TOP is added next to each letter&#39;s title to take the user back to the top of the index page. The index attribute of the info-catalog XML set to “no” or the “-noindex” input parameter omits the INDEX link in the navigation bars at the top and bottom of each page of output and does not generate index documents. This page can be displayed by selecting Index from any detail page&#39;s navigation bar.  FIG. 32  depicts an index page, in accordance with embodiments of the present invention. 
     The open source XSL Formatting Objects (XSL-FO) specification, a W3C recommendation, is used to generate high-quality printable versions of the information catalog in portable document format (PDF) format. The compiler produces versions in both A4 (21×29.7 cm) and Letter (8.5×11 in) formats. XSL Stylesheets are used containing elements that: 
     1. Define page sizes, fonts, and margins 
     2. HTML to PDF conversions 
     3. Table of contents 
     4. Information Catalog specific pages (e.g. Overview summary, table details) 
     The present invention uses Apache XML Project&#39;s FOP (Formatting Objects to PDF) translator and a series of XSL Stylesheets to render the PDF documents. 
       FIG. 33  illustrates a computer system  90  used for generating an information catalog relating to a business model, in accordance with embodiments of the present invention. The computer system  90  comprises a processor  91 , an input device  92  coupled to the processor  91 , an output device  93  coupled to the processor  91 , and memory devices  94  and  95  each coupled to the processor  91 . The memory devices  94  and  95  are computer readable. The input device  92  may be, inter alia, a keyboard, a mouse, etc. The output device  93  may be, inter alia, a printer, a plotter, a computer screen, a magnetic tape, a removable hard disk, a floppy disk, etc. The memory devices  94  and  95  may be, inter alia, a hard disk, a floppy disk, a magnetic tape, an optical storage such as a compact disc (CD) or a digital video disc (DVD), a dynamic random access memory (DRAM), a read-only memory (ROM), etc. The memory device  95  includes a computer code  97 . The computer code  97  includes algorithm(s) or other computer readable program code (e.g., information catalog compiler) for generating an information catalog relating to a business model. The processor  91  executes the computer code  97 . The memory device  94  includes input data  96 . The memory device  94  includes or is coupled to a data warehouse  98  which may be embodied in the RDBMS  22  of  FIGS. 3 and 4 . The input data  96  includes input required by the computer code  97 . The output device  93  displays output from the computer code  97  (e.g., the graphical interface of  FIG. 13 ). Either or both memory devices  94  and  95  (or one or more additional memory devices not shown in  FIG. 33 ) may be used as a computer usable medium (or a computer readable medium or a program storage device) having a computer readable program code embodied therein and/or having other data stored therein, wherein the computer readable program code comprises the computer code  97 . Generally, a computer program product (or, alternatively, an article of manufacture) of the computer system  90  may comprise said computer usable medium (or said program storage device). 
     While  FIG. 33  shows the computer system  90  as a particular configuration of hardware and software, any configuration of hardware and software, as would be known to a person of ordinary skill in the art, may be utilized for the purposes stated supra in conjunction with the particular computer system  90  of  FIG. 33 . For example, the memory devices  94  and  95  may be portions of a single memory device rather than separate memory devices. 
     While embodiments of the present invention have been described herein for purposes of illustration, many modifications and changes will become apparent to those skilled in the art. Accordingly, the appended claims are intended to encompass all such modifications and changes as fall within the true spirit and scope of this invention.