Abstract:
A method for data quality management may include collecting data related to a project. The method may also include generating a predetermined representation of the data and implementing or performing an improvement related to the project in response to the representation of the data indicating a trend toward not meeting a predefined project goal. The method may further include defining a control plan in response to the data indicating a trend toward meeting the predefined project goal.

Description:
COPYRIGHT NOTICE 
     A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document, or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. 
     BACKGROUND OF INVENTION 
     The present invention relates to managing data, information or the like and more particularly to a method and system for data quality management. 
     Easy access to accurate, reliable data can be critical in decision making and the operation of a business. Data may be collected to analyze and evaluate trends to provide better or improved products and services to customers both within an organization and external to an organization. Data may also be collected to detect problems and to permit analysis for developing plans to improve operations and for other purposes. Automated and standardized data quality metrics, collection, management and presentation can significantly improve the accuracy and reliability of the data in making business decisions and operating a business. 
     BRIEF SUMMARY OF INVENTION 
     In accordance with an embodiment of the present invention, a method for data quality management may include collecting data related to a project. The method may also include generating a predetermined representation of the data and implementing or performing an improvement related to the project in response to the representation of the data indicating a trend toward not meeting a predefined project goal. The method may further include defining a control plan in response to the data indicating a trend toward meeting the predefined project goal. 
     In accordance with another embodiment of the present invention, a method for data quality management may include sending a query to a source database to collect data associated with a key characteristic of an element associated with a project. The method may also include comparing the collected data to a predefined project goal and generating a run chart based on comparing the collected trend data to the predefined project goal. The method may further include implementing an improvement related to the project in response to the run chart indicating a trend toward not meeting the predefined project goal. A control plan may be defined in response to a control chart indicating a trend being out of control. 
     In accordance with another embodiment of the present invention, a system for data quality management may include a data structure operable on a processor to collect data related to a project. The system may also include a data structure to generate a predetermined representation of the data. Means may be included to implement an improvement related to the project in response to the representation of the data indicating a trend toward not meeting a predefined project goal. The system may further include means to define a control plan in response to the data indicating a trend being out of control. 
     In accordance with another embodiment of the present invention, a computer program product for data quality management may include a computer readable medium having computer readable program code embodied therein. The computer readable medium may include computer readable program code configured to collect data associated with each key characteristic of an element associated with a project. The computer readable medium may also include computer readable program code configured to generate a predetermined representation of the data. The computer readable medium may further include computer readable program code configured to generate an alert in response to any key characteristic being out of control. 
    
    
     
       BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS 
         FIGS. 1A and 1B  (collectively  FIG. 1 ) are an example of a method for data quality management in accordance with an embodiment of the present invention. 
         FIG. 2  is an example of a run chart and associated table that may be presented to a user in accordance with an embodiment of the present invention. 
         FIG. 3  is a block diagram of an exemplary system for data quality management in accordance with an embodiment of the present invention. 
         FIG. 4  is a block diagram of another exemplary server that may be used in a system for data quality management in accordance with an embodiment of the present invention. 
         FIG. 5  is an example of a web page, GUI or the like to access a data quality management system in accordance with an embodiment of the present invention. 
         FIG. 6  is an example of a web page, GUI or the like for entering or editing user profile information in a data quality management system in accordance with an embodiment of the present invention. 
         FIG. 7  is an example of a web page, GUI or the like for adding a database connection in a data quality management system in accordance with an embodiment of the present invention. 
         FIG. 8  is an example of a web page, GUI or the like in a data quality management system to present a program and project overview in accordance with an embodiment of the present invention. 
         FIG. 9  is an example of a web page, GUI or the like in a data quality management system to present statistics related to all projects in accordance with an embodiment of the present invention. 
         FIG. 10  is an example of a web page, GUI or the like in a data quality management system to present control charts and an associated spreadsheet in accordance with an embodiment of the present invention. 
         FIG. 11  is an example of a web page, GUI or the like in a data quality management system to present project management reports and associated spreadsheets in accordance with another embodiment of the present invention. 
         FIG. 12  is an example of a web page, GUI or the like in a data quality management system to present critical to quality (CTQ) performance in accordance with an embodiment of the present invention. 
         FIG. 13  is an example of a web page, GUI or the like in a data quality management system to update a CTQ query schedule and to enter or edit CTQ queries in accordance with an embodiment of the present invention. 
         FIG. 14  is an example of a web page, GUI or the like in a data quality management system to present CTQ information to a user in accordance with an embodiment of the present invention. 
         FIG. 15  is an example of a web page, GUI or the like in a data quality management system to update CTQ definitions in accordance with an embodiment of the present invention. 
         FIG. 16  is an example of a web page, GUI or the like in a data quality management system to present project goals in accordance with an embodiment of the present invention. 
         FIG. 17  is an example of a web page, GUI or the like in a data quality management system to add a project goal in accordance with an embodiment of the present invention. 
         FIG. 18  is an example of a web page, GUI or the like in a data quality management system to update a project goal in accordance with an embodiment of the present invention. 
         FIG. 19  is an example of a web page, GUI or the like in a data quality management system to select a project for editing a project definition in accordance with an embodiment of the present invention. 
         FIG. 20  is an example of a web page, GUI or the like in a data quality management system to update or edit a project in accordance with an embodiment of the present invention. 
         FIG. 21  is an example of a web page, GUI or the like in a data quality management system to add or update a category in a project definition in accordance with an embodiment of the present invention. 
     
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     The following detailed description of embodiments refers to the accompanying drawings, which illustrate specific embodiments of the invention. Other embodiments having different structures and operations do not depart from the scope of the present invention. 
     As will be appreciated by one of skill in the art, the present invention may be embodied as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Furthermore, the present invention may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium. 
     Any suitable computer readable storage medium may be utilized. The computer-usable or computer-readable storage medium may be, for example but not limited to, an electronic, magnetic, optical, or semiconductor system, apparatus or device medium. More specific examples (a nonexhaustive list) of the computer-readable medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, or a magnetic storage device. In the context of this document, a computer-usable or computer-readable medium may be any medium that can store the program for use by or in connection with the instruction execution system, apparatus, or device. 
     Computer program code for carrying out operations of the present invention may be written in an object oriented programming language such as Java7, Smalltalk or C++. However, the computer program code for carrying out operations of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language. The program code may execute entirely on the user&#39;s computer, partly on the user&#39;s computer, as a stand-alone software package, partly on the user&#39;s computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user&#39;s computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). 
     The present invention is described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. 
     These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks. 
     The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. 
     The following is a list of definitions for terms and abbreviations used in describing the invention. These terms and definitions are merely provided for purposes of explaining and understanding the invention. Other terms and definitions may be applicable as well and the invention is not intended to be limited by the specific terms and definitions used herein.
     (1)CTQ (Critical to Quality). CTQ is a term used in association with Six Sigma Quality programs or environments. However, CTQs may be applicable in any business or environment desiring to improve quality and may be any key measurable characteristics of a product or process whose performance standards or specifications limits are desired to be met in order to satisfy customers. CTQs may align improvement or design efforts with customer requirements. CTQs may represent product or service characteristics that may be defined by the customer (internal or external). They may include the upper and lower specification limits or any other factors related to the product or service. A CTQ may be interpreted from a qualitative customer statement to an actionable, quantitative business specification.   (2)Data Element or Element may be the logical representation of data entity attributes that provide the basis for the physical implementation of data elements or database table columns in information systems.   (3)Defect may be any nonconformity in a product or process. May also be any event that does not meet the performance standards CTQ of an entity. Examples of defects may include completeness or missing, accuracy, validity, timeliness or the like. Completeness or missing may mean that data is not populated or missing. Accuracy may mean that data cannot be verified as fact or accurate. Validity may mean that data is populated but may not be valid. Timeliness may means that the data is late.   (4)DPM (Defects per Million). The number of defects that may be encountered in one million outputs.   (5)DPMO (Defects per Million Opportunities). The average number of defects per unit observed during an average production run divided by the number of opportunities to make a defect on the product under study during that run normalized to one million.   (6)LCL (Lower Control Limit). LCL may be a horizontal line on a control chart or the like that represents the lower process limit capability of a process.   (7)Mean-Measure of central tendency where data values are summed and divided by the number of data points; may also be the average.   (8)OCAP (Out of Control Action Plan). OCAP may be a plan to bring a program, project, element, CTQ or the like back within limits or between the LCL and Upper Control Limit (UCL) on a control chart or the like.   (9)ODBC (Online DataBase Connection). ODBC may be a connection, link or path to a database, data source or the like via a network, such as the Internet, intranet or other private network.   (10) Out of Control may refer to rejecting the assumption that the current data are from the same population as the data used to execute the initial control limits. May also refer to any project, program, element, CTQ or the like that may be outside predefined limits such as LCL and UCL or similar limits.   (11) Program may be a system of projects.   (12) Project may be a planned undertaking.   (13) SOR-System of Record.   (14) UCL (Upper Control Limit). UCL may be a horizontal line on a control chart or the like that may represent an upper limit of process capability.   (15) User: Administrator may be an individual who sets up programs and projects per requests from a Project Leader or similar individual. Administrator may also perform database maintenance and update functions or similar functions or operations.   (16) User: Data Steward may be an individual whose role may be assigned by an Administrator, Project Leader or similar individual to provide the capability to perform selected functions, such as updating, editing or similar functions related to assigned defects, CTQs, or the like.   (17) User: General may have read-only authorization.   (18) User: Project Leader may set up CTQs, assign Data Steward roles for assigned programs, projects or like. Project Leader privileges may be assigned by the Administrator or similar individual.   

       FIGS. 1A and 1B  (collectively  FIG. 1 ) are an example of a method  100  for data quality management in accordance with an embodiment of the present invention. Different functions, operations or events of the method  100  may be performed by or involve different entities, individuals, systems or the like as illustrated in  FIG. 1 . Examples of the different entities, individuals, systems or the like may include (not an exhaustive list) Data Steward  102 , Data Quality (DQ) Project  104  or DQ Project Team, Data Quality Metric (DQM) which may be an online or web-enabled tool or system for data quality in accordance with an embodiment of the present invention. The invention is not intended to be limited by the entity, individual or system that may perform or be involved with a particular function or feature of the method  100 . 
     In block  108 , the method  100  may begin. The method  100  may be started by the Data Steward  102  or similar trained, skilled and authorized individual. In block  110 , a project, elements, data elements or the like may be defined along with key measurable characteristics (CTQs) of the elements or data elements may be defined. A project name may be identified and project leadership and hierarchy may be selected or determined. 
     In block  112 , information associated with the project defined in block  110  may be entered into a data quality management system, data quality metric, or the like. As will be described in more detail herein, a graphical user interface (GUI) or the like may be presented to a user, project leader or the like, to enter or edit information associated with a project or program. Examples of the project information that may be entered may include defect definitions; project goals; CTQs; CTQ queries in a structured query language (SQL) or similar format; data connectivity parameters; execution schedules or time schedules for generating or sending the CTQ queries to retrieve data related to the project; or similar project related information that may be dependent upon the particular nature of the project, elements, CTQs, etcetera. 
     In block  114 , data or trend data may be collected on a predefined time schedule that may have been entered in block  112 . A query for each CTQ or CTQ SQLs or the like may be executed according to the predefined time schedule in a Data Quality Metric or Management System and sent to the appropriate source databases to collect the desired data or trend data for each CTQ. In block  116 , a predetermined representation of the data may be formed for each CTQ and presented to a user. The data or trend data may be compared to the goals for each CTQ and a run chart or the like may be generated and presented to the user. Accordingly, the predetermined representation of the data may be a run chart, spreadsheet or similar data representation for each CTQ.  FIG. 2  is an example of a run chart  200  that may be presented to a user. The run chart  200  may be a graph representing trend data  202  of defects per million (DPM) or other key measurable characteristic (CTQ) of a product, service or the like over a predetermined time period compared to a goal for the CTQ that may be represented by a line  204  on the run chart  200 . The trend data  202  may also be presented in a spreadsheet or table  206  format as illustrated in the example of  FIG. 2 . 
     In block  118 , a determination may be made whether the project goals are being met. The determination may be made based on the predetermined representation of data or run chart  200  generated in block  116 . If a determination is made in block  118  that project goals are not being met, the method  100  may advance to block  120 . In block  120 , an improvement function or operation may be developed or designed and implemented or performed to close the gap or difference between the trend data for the CTQ and the project goals as indicated in the predetermined representation of the data or run charts in block  116 . 
     If project goals are being met in block  118 , the method  100  may advance to block  122 . In block  122 , a control plan may be defined or reviewed and revised if previously defined. A Data Steward or the like may also be assigned and entered into the Data Quality Management System as will be described in more detail herein. 
     In block  124 , a control chart may be generated for each CTQ. An example of a control chart will be described with reference to  FIG. 10 . An alert may be automatically generated by the method  100  or Data Quality Management or Metric System in response to a CTQ being out of control or exceeding preset limits, such as LCL and UCL limits or the like. The method  100  or Data Quality Management System may automatically generate an e-mail to advise the Data Steward or other management that the CTQ is out of control or limits. 
     In block  126 , trends, alerts or the like may be analyzed. The analysis may be conducted by the Data Steward or others. In block  128 , a determination may be made whether the trends, alerts or the like may require any action. If a determination is made that an action or actions may be needed, the method  100  may return to block  120 . In block  120 , as previously described, an improvement may be implemented or performed to bring the CTQ back into control or within control limits. If a determination is made that no action is required in block  128 , the method  100  may end at termination  130 . 
     Returning to block  124 , the method  100  may also advance to block  132  from block  124 . In block  132 , a management report may be generated on the control process or similar reports, such as effectiveness of the control process or the like. The management reports may be generated using data captured in a central repository or data source. Trend reports of the control process may be run to provide a better understanding of the healthiness or effectiveness of the process. For example, high-level trends, stages of improvement, missing resources and other process related factors may be evaluated and reported. An example of management reports generated in block  132  will be described with reference to  FIG. 11 . 
     In block  134 , the effectiveness of the control process may be reviewed along with any issues related to the control process. The management reports may be used to conduct the reviews. The trended management reports may support review sessions between management and the next level leaders. 
     In block  136 , a determination may be made whether the control process is effective. If a determination is made that the control process is not effective, the method  100  may return to block  122 . In block  122  the control plan may be reviewed and revised to improve effectiveness. The method  100  may then advance to block  124  and then proceed as previously described. If the control process is determined to be effective in block  136 , the method  100  may end at termination  130 . 
       FIG. 3  is a block diagram of an exemplary system  300  for data quality management in accordance with an embodiment of the present invention. Elements of the method  100  may be embodied in and performed by the system  300 . The system  300  may include one or more user or client computer systems  302  or similar systems or devices. 
     The computer system  302  may include a system memory or local file system  304 . The system memory  304  may include a read only memory (ROM) and a random access memory (RAM). The ROM may include a basic input/output system (BIOS) (not shown in  FIG. 3 ). The BIOS may contain basic routines that help to transfer information between elements or components of the computer system  302 . The RAM may contain an operating system  306  to control overall operation of the computer system  302 . The RAM may also include a browser  308  or web browser and an e-mail client or application  310 . The RAM may also include data structures  312  or computer-executable code for data quality management in accordance with an embodiment of the present invention that may be similar or include elements of the method  100  of  FIG. 1 . The RAM may further include other application programs  314 , other program modules, data, files and the like. 
     The computer system  302  may also include a processor or processing unit  316  to control operations of the other components of the computer system  302 . The operating system  306 , browser  308 , data structures  312  and other program modules  314  may be operable on the processor  316 . The processor  316  may be coupled to the memory system  304  and other components of the computer system  302  by a system bus  318 . 
     The computer system  302  may also include multiple input devices, output devices or combination input/output devices  320 . Each input/output device  320  may be coupled to the system bus  318  by an input/output interface (not shown in  FIG. 3 ). The input and output devices or combination I/O devices  320  permit a user to operate and interface with the computer system  302  and to control operation of the browser  308 , e-mail  310  and data structures  312  to access, operate and control the data quality management system  300 . The I/O devices  320  may include a keyboard and computer pointing device or the like to perform the operations discussed herein, such an entering and revising program and project information in GUIs illustrated and described herein and that form part of the data quality management system in accordance with an embodiment of the present invention. 
     The I/O devices  320  may also include disk drives, optical, mechanical, magnetic, or infrared input/output devices, modems or the like. The I/O devices  320  may be used to access a medium  322 . The medium  322  may contain, store, communicate or transport computer-readable or computer-executable instructions or other information for use by or in connection with a system, such as the computer system  302 . 
     The computer system  302  may also include or be connected other devices, such as a display or monitor  324 . The monitor  324  may be used to permit the user to interface with the computer system  302 . The monitor  324  may present the GUIs or web pages illustrated and described with reference to  FIGS. 5-21  and that may form part of the data quality management system  300  in accordance with an embodiment of the present invention. 
     The computer system  302  may also include a hard disk drive  326 . The hard drive  326  may be coupled to the system bus  318  by a hard drive interface (not shown in  FIG. 11 ). The hard drive  326  may also form part of the local file system or system memory  304 . Programs, software and data may be transferred and exchanged between the system memory  304  and the hard drive  326  for operation of the computer system  302 . 
     The client computer system  302  may also include a network interface  328  coupled to the system bus  318 . The network interface  328  may connect the client computer system to a network  330 . The network interface  328  may be a modem, Ethernet card, router, gateway or the like for coupling to the network  330 . The coupling may be a wired connection or wireless. The network  330  may be the Internet, private network, an intranet or the like. 
     The computer systems  302  may communicate with a web server  332 , application server  334 , database server  336  or the like, and may access other servers, such as or other computer systems similar to computer system  302  via the network  330 . The web server  332 , application server  334  and database server  336  may be separate servers as illustrated in  FIG. 3  or may be embodied in a single server. The web server  332 , application server  334  and database server  336  may communicate with one another via the network  330  or may be linked by separate communications means or a dedicated communication network, link or channel  338 . 
     The database server  336  may include a process information and storage management database  340  or data source, a project information storage and management database  342  or data source and a Data Critical to Quality (DCTQ) information storage and management database  344  or data source. The process information and storage management database  340  may store data or information related to the data quality management process performed by the data quality management system  300 . The project information storage and management database  342  may store information or data related to different projects entered into the data quality management system  300 . The DCTQ information and storage management database  344  may store information or data related to the business description of the CTQ, Source database, execution schedule and SQLs used to collect performance data. 
     The application server  334  may communicate with a plurality of source system databases  346 . The source system databases  346  may store data, such as trend data or the like, related to CTQs, projects and programs that may be entered and monitored and controlled by use of the data quality management system  300 . 
       FIG. 4  is a block diagram of an exemplary server  400  that may be used for the application server  334  in a system for data quality management in accordance with an embodiment of the present invention. The server  400  may include a system memory  402  that may include a file system, ROM, RAM and the like. The system memory  402  may include an operating system  404  similar to operating system  306  in computer systems  302 . The system memory  402  may also include data structures  406  for data quality management (DQM) in accordance with an embodiment of the present invention. The data structures  406  may include operations similar to those described with respect to method  100  in  FIG. 1  for data quality management. Users or clients, such as computer systems  302  or the like, may access the data structures  406  for data quality management in accordance with an embodiment of the present invention. The data structures  406  may include an authentication and security agent module  408 , a data entry module  410 , a run chart module  412 , a control chart module  414 , a management reports module  416 , a personalized reports and alerts module  418 , an administration and custom reporting module  420 , a query storage, scheduling and execution agent  422 , an alert definition and detection agent  424  and a personalized e-mail generation and delivery agent  426 . The authentication and security agent  408  may authenticate any user attempting to access the system to confirm the user is authorized. A username and password entered by a user may be checked against a list or database of authorized usernames and passwords as is known in the art. 
     The data entry module  410  may present a GUI or GUI&#39;s to a user to enter data related to programs, projects, CTQs and the like for monitoring and control using the data quality management system. The run chart module  412  may generate and display run charts similar to that described with respect to block  116  of  FIG. 1  and the exemplary run chart  200  described with respect to  FIG. 2 . The control chart module  414  may generate control charts similar to that provided by block  124  in  FIG. 1  and as will be described with respect to the control chart example illustrated in  FIG. 10  herein. The management reports module  416  may generate management reports and the like similar to block  132  in  FIG. 1  and the exemplary management reports illustrated in  FIG. 11  and described in more with reference to  FIG. 11  below. 
     The personalized reports and alerts module  418  permits a user to personalize the appearance and presentation of data in the reports that may be presented to the user by the data quality management system, such as system  300 , and the alerts presented to a user when a CTQ or the like is out of control or outside preset or predetermined limits. The administration and custom reporting module  420  may be used by a system administrator to customize the reporting features of the data quality management system as described and illustrated herein. 
     The query storage, scheduling and execution agent  422  may be responsible for storing the queries, SQLs or the like that may be used by the data quality management system in retrieving the appropriate information or data, such as trend data or the like, from the data sources or databases where the data may be stored. The agent  422  may also select the appropriate queries based on definitions and other parameters entered by a user into the system. The agent  422  may execute the queries pursuant to a predefined time schedule that may be entered into the agent  422  by a user. 
     The alert and definition detection agent  424  may generate and store LCLs and UCLs or similar limits to detect when a CTQ or the like is out of control or outside its preset limits. The agent  424  may then automatically generate an alert, which may be an e-mail message as described herein, to alert a Data Steward or similar person that a CTQ is out of limits and corrective action may be needed. The personalized e-mail generation and delivery agent  426  may automatically generate and deliver an e-mail including an alert in response to detecting a CTQ being out of limits by agent  424 . The server system memory  402  may also include other files  428 , applications, modules and the like. 
     The server  400  may also include a processor  430  or a processing unit to control operation of other devices in the server  400 . The server  400  may also include I/O device  432 . The I/O devices  432  may be similar to I/O devices  320  of computer systems  302 . The server  400  may further include other devices  434 , such as a monitor or the like to provide an interface along with the I/O devices  432  to the server  400 . The server  400  may also include a hard disk drive  436 . A system bus  438  may connect the different components of the server  400 . A network interface  440  may couple the server to a network, such as network  330  in  FIG. 3 . 
       FIG. 5  is an example of a web page, GUI  500  or the like to access a data quality management system or data quality metric, such as system  300 , in accordance with an embodiment of the present invention. The GUI  500  may be presented to a user after proper authentication, such as by module  408  ( FIG. 4 ) or the like, and the user is permitted access to the data quality metric or data quality management system via the user&#39;s browser, similar to browser  308  ( FIG. 3 ). The GUI  500  may include a command bar  502 . The command bar  502  may include tabs  504 - 514  that may be clicked-on or operated using a computer pointing device, mouse or the like to access the web pages or GUIs associated with the particular tab  504 - 514 . Each of the tabs  504 - 514  and the associated web pages or GUIs will be described in more detail below. 
       FIG. 6  is an example of a web page, GUI  600  or the like for entering, selecting or editing user profile information in a data quality management system or data quality metric (DQM), such as system  300 , in accordance with an embodiment of the present invention. The GUI  600  may be accessed by a user clicking-on or activating the “My Profile” tab  514  in  FIG. 5  which may be the same as the “My Profile” tab  614  in  FIG. 6 . The GUI  600  may be divided into different sections or segments. A first section  616  may be labeled “PROJECT SELECTION” or another appropriate legend or label that may describe the information entered, selected or edited in the section  616 . A second section  618  may be labeled “EMAIL PREFERENCE” or the like, and a third section  620  may be labeled “DATABASE CONNECTION” or a similar label or legend descriptive of the information or data that may be contained and edited or selected in the section  620 . 
     The Project Selection section  616  may include a list  622  of the projects that may be assigned to a user, Data Steward, project leader or similar individual. Projects may be selected from the list  622  using a computer pointing device or the like and added to a second list  624  of selected projects for more detailed viewing, monitoring or for other purposes. Projects may be added to the second list  624  by selecting projects in first list  622  and then clicking-on or operating a button  626  that may be labeled “Add” or the like. Projects may be removed from the second list  624  by clicking-on or operating a button  628  that may be labeled “Remove” or the like. The projects in the second or selected list  624  may be updated by the user clicking-on or activating a button  630  that may be labeled “Update Project Selection.” The user may be directed to a project screen in response to clicking-on the “Update Project Selection” button  630 . An example of a project screen is illustrated in  FIG. 8 . 
     In second section or “EMAIL PREFERENCE” section  618 , a user may select or enter preferences with respect to automatically receiving email summaries and email alerts from the data quality management system. Email alerts may be enabled or disabled by clicking or checking the appropriate box and the user may select the timing and schedule for regular email summaries related to the projects selected or added to the selection list  624 . A user&#39;s email preferences may be updated in the system by clicking-on or operating a button  632  that may be labeled “Update Email Preferences” or a similar descriptive label. 
     In the third section or “DATABASE CONNECTION” section  620 , database connection links, paths or the like may be specified for automated data collection in response to queries generated by the system. A database entry form or GUI  700  may be presented to a user in response to the user clicking-on or operating a button  634  that may be labeled “Add Database Connection” or a similar descriptive label or legend. The database entry form or GUI  700  may include a field or drop-down list  716  to enter or select a database from which data may be collected by the data quality management system. The GUI  700  may also include a user ID field  718  and a password field  720  for a user to enter his username or ID and password that may be needed to access the database designated in field  716 . The database connection selected in database field  716  may be added to the data quality management system by clicking-on or activating a button  722  that may be labeled “Add.” Similarly, the process of adding a database connection may be aborted by clicking-on a “Cancel” button  724 . By entering a user ID and password for the database designated in field  716  and clicking-on the “Add” button  722 , the user is authorizing the data quality management system or metric to access the database designated on the user&#39;s behalf according to the schedule defined by the user. 
       FIG. 8  is an example of a web page, GUI  800  or the like in a data quality management system or metric to present a program and project overview in accordance with an embodiment of the present invention. The GUI  800  may be accessed by a user clicking-on or activating a “Project” tab  804  in command bar  802  which may be the same as or similar to the “Project” tab with a corresponding reference numeral in other GUIs illustrated in the Figures. The project screen or GUI  800  may be divided into two sections or segments. A first section  816  may be labeled “Program Overview” or other appropriate descriptive label. A second section  818  may be labeled “Project Overview” or similar label. The Project Overview section  818  may be depicted below the Program Overview section  816 . The Program Overview section  816  may list all of the program level projects  818  that a user may have selected in GUI  600  or that the user has been assigned or owns. Also presented in Program Overview section  816  may be the collected data related to each program over a predetermined time horizon or time period in response to queries. In the example illustrated in  FIG. 8 , the data illustrated is defects per million (DPM) for a product or service on a per month basis over a selected number of months. The data illustrated also includes a “Sigma” or standard deviation associated with each statistic for each month over the time period. Other data may be presented depending upon the particular product, service or business using the data quality management system. 
     The second section or Project Overview section  820  may list all of the projects, their child projects and summaries  822 . The data illustrated may also be DPM and Sigma as illustrated in the example of  FIG. 8  or may be other data depending upon the particular product, service or business. 
     To view statistics for all projects in GUI  800 , a “Show Statistics” link  824  may be clicked-on or operated by a computer pointing device or the like. A GUI, such as GUI  900  in  FIG. 9 , to present statistics  924  related to all projects may be presented to a user in response to operating “Show Statistics” link  820  in GUI  800 . Examples of the statistics  924  that may be illustrated may include (not an exhaustive list) number of projects, number of CTQs, number of active queries, number of CTQs with at least one Data Steward, the number of Data Stewards associated with or assigned to each project and program or similar statistics. The statistics  924  may be hidden by operating a “Hide Statistics” link  926  or the like. 
       FIG. 10  is an example of a web page, GUI  1000  or the like in a data quality management system to present control charts  1002  and an associated spreadsheet  1004  or tables in accordance with an embodiment of the present invention. A control chart  1002  for a particular project may be accessed or presented by a user clicking-on a selected project or program  818  or  822  in GUI  800  or  918  or  922  in GUI  900 . The control charts  1002  may be generated and presented to the user as part of the method  100  for data quality management in block  124  of  FIG. 1  and control chart module  414  of  FIG. 4 . The control charts  1002  may indicate a UCL  1006  and LCL  1008  to indicate if any project or program may be out of control or outside of preset limits. Additionally, the statistics for any out of control project or program may be highlighted or otherwise identified in the table  1004 . For example, the data may be highlighted by using a different colored font, such as red, or identified by other means. Additional details, program management reports and the like may be accessed by a user operating or clicking-on links, such as links  1010  and  1012  that may be respectively labeled “Details”  1010 , “Program Mgmt. Report”  1012 , or other links. 
       FIG. 11  is an example of a web page, GUI  1100  or the like in a data quality management system to present project management reports  1102  and associated spreadsheets or tables  1104  in accordance with another embodiment of the present invention. The project management reports  1102  and associated tables  1104  may be presented in response to the user operating the “Details” or “Program Mgmt Report” links  1010  and  1012  in GUI  1000  of  FIG. 10 . The management reports  1102  may be generated and presented to the user as part of the method  100  for data quality management in block  132  and management reports module  416  in  FIG. 4 . 
       FIG. 12  is an example of a web page, GUI  1200  or the like in a data quality management system to present critical to quality (CTQ) performance data or information in accordance with an embodiment of the present invention. The “CTQ Performance” GUI  1200  may be presented in response to a user clicking-on or operating the tab  1206  in command bar  1202 . The command line  1202  and tabs  1204 - 1214  may be similar or the same as the tabs in the GUIs illustrated in the other Figures and may perform the same functions or access the same GUIs or web pages discussed herein. 
     A previously discussed, statistics or data for CTQs that may be out of control or outside preset limits, such as UCL and LCL, may be identified or highlighted in the spreadsheet or table of GUI  1200 . For example the statistics that are represent out of control data may be represented in a red font  1216 . In GUI  1200 , a user may edit a CTQ scheduler and queries by clicking-on or operating an icon  1218 . The icon  1218  may be a symbol resembling a calendar, a schedule or other descriptive symbol indicative of the purpose of the icon. A control chart  1002  for a particular CTQ may be accessed or presented by a user clicking-on a selected CTQ  1220  in GUI  1200 . 
       FIG. 13  is an example of a web page, GUI  1300  or the like in a data quality management system to update a CTQ query schedule and to enter or edit CTQ queries in accordance with an embodiment of the present invention. The GUI  1300  in  FIG. 13  may be presented in response to a user clicking-on or operating the icon  1218  in  FIG. 12 . The GUI  1300  may include a first section or segment  1316  that may be labeled “UPDATE CTQ SCHEDULE” or a similar descriptive label. The section  1316  may include fields for a user to select or enter a schedule when a query to collect data related to a CTQ identified in an “ID-Title” field  1318  may be executed. The “UPDATE CTQ SCHEDULE” section  1316  may also include a field  1320  to select or enter a status of the CTQ query and a field  1322  to select or enter a timing for the CTQ query. 
     The GUI  1300  may also include a second section or “Data Sourcing” section  1324 . The “Data Sourcing” section  1324  may include a field  1326  to enter or select a database connection. The “Data Sourcing” section  1324  may also include a “Defect SQL” field  1328  for a user to enter or define a SQL to collect the number of defects from the source database. The “Data Sourcing” section  1324  may further include an “Opportunity SQL” field  1330  for a user to enter or define a SQL to collect the number of opportunities (measurement population) from the source database. The CTQ schedule and queries entered or edited in GUI  1300  may be updated and the query tested without posting the results by a user clicking-on or operating a button  1332  that may be labeled “Update and Test Run” or similar descriptive legend or label. “Test” may also be selected in the drop-down Status field  1320  to test run a query without posting any results. Alternatively, the CTQ schedule and queries may just be updated by a user clicking-on or operating a button  1334  that may be labeled “Update” or the like. The entered data in GUI  1300  may be canceled by a user operating a “Cancel” button  1336 . When the “Status” box is set to “Active,” the data quality management system may run the query and post the results to the current month unless the “Post Results Under Last Month/Week” box  1338  is checked. 
       FIG. 14  is an example of a web page, GUI  1400  or the like in a data quality management system to present CTQ information to a user in accordance with an embodiment of the present invention. The GUI  1400  may be presented to a user in response to the user clicking-on or operating a “CTQ Info” tab in any of the GUIs illustrated in the Figures which is designated by the reference numeral  1408  in  FIG. 14 . The GUI  1400  may list the title  1415  of each CTQ and indicate the Data Steward or Stewards  1416  assigned to each CTQ. The CTQ information may be presented in different formats by clicking-on different options in a “Grouping Options” line  1418  or section. The CTQ Information GUI  1400  may also provide information about Unit of Measure (UOM) and CTQ stage  1420  as they are specified in a “Unit of Measure” field  1526  and a “CTQ Stage” field  1534  in GUI  1500 . The CTQ Information GUI  1400  may also provide access to the CTQ scheduler  1422  to schedule and define CTQ queries similar to that previously described. The CTQ scheduler may be edited by clicking-on an icon  1424  that may represent a calendar or other symbol to represent scheduling CTQ queries. New CTQ definitions may be added by clicking-on an “Add New CTQ Definition” link  1426 . The CTQ definitions may be edited by clicking on an edit CTQ definition icon  1428  or similar symbol indicative of editing a CTQ definition. 
       FIG. 15  is an example of a web page, GUI  1500  or the like in a data quality management system to update or edit CTQ definitions in accordance with an embodiment of the present invention. The GUI  1500  may be presented to a user in response to the user clicking-on or activating the edit CTQ definition icon  1428  in GUI  1400 . The GUI  1500  may be divided into an “Update CTQ Definition” Section  1516 , a “Classification” section  1518  and a “Misc. Information” section  1520 . 
     The “Update CTQ Definition” Section  1516  may include a “Title” field  1522  to enter or edit a title for the CTQ. A “CTQ Type (Control Chart) field  1524  may be included in section  1516  to enter a CTQ type and a type of control chart to be generated. Other fields may include a “Unit of Measure” field  1526 , a “Business Description” field  1528 , a “Data Steward/Responsible Contact” field  1530  or the like. 
     The “Classification” section  1518  may include a “Project” field  1532  to enter or select a project identification, a “CTQ Stage” field  1534  to enter or select from a drop-down list a CTQ stage, a “Line of Business” field  1536 , a “Data Element” field  1540 , an “Impact Business Partner” field  1542 , a “Region” field  1544  and “Source System” field  1546 . 
     The “Misc. Information” section  1520  may include baseline information, such as a date field  1548 , defect number field  1550 , opportunity number field  1552 , instructions to fix field  1554  and the like. The updated or edited CTQ information may be updated and stored by the system in response to a user clicking-on or operating a button  1556  that may be labeled “Update” or the like. The CTQ information or update may be canceled before being saved in the system by clicking-on a “Cancel” button  1558 . 
       FIG. 16  is an example of a web page, GUI  1600  or the like in a data quality management system to present project goals in accordance with an embodiment of the present invention. The GUI  1600  may be presented to a user in response to the user clicking-on a “Project Goals” tab (tab  1610  in  FIG. 16 ) in any of the GUIs illustrated in the drawings. 
       FIG. 17  is an example of a web page, GUI  1700  or the like in a data quality management system to add a new project goal in accordance with an embodiment of the present invention. The GUI  1700  may be presented in response to a user clicking-on or activating a link  1616  in GUI  1600  that may be labeled “Add New Goal Definition” or similar label. The GUI  1700  may include a “Title” field  1716 , a “Description” field  1718  and any other appropriate fields to identify a project goal. The project goal may be added in response to the user clicking-on or operating a button  1720  that may be labeled “Add” or a similar label. 
       FIG. 18  is an example of a web page, GUI  1800  or the like in a data quality management system to update a project goal in accordance with an embodiment of the present invention. The GUI  1800  may be presented to a user in response to the user clicking-on or activating a project goal link  1618  in GUI  1600  ( FIG. 16 ). The GUI  1800  may include a “Title” field  1816 , a “Description” field  1818 , “Target Goals” fields  1820  and “Project Goals” fields  1822 . Other fields may be provided as appropriate to specify any project goals. The information entered in the fields in GUI  1800  may be updated by the data quality management system in response to clicking-on or activating an “Update” button  1824   
       FIG. 19  is an example of a web page, GUI  1900  or the like in a data quality management system to select a project for editing a project definition in accordance with an embodiment of the present invention. The GUI  1900  may be same as GUI  800  ( FIG. 8 ) and may be presented to a user in response to the user clicking-on or operating a “Project” tab  1902  or similar “Project” tab in other GUIs illustrated in the Figures. The user may then edit a project definition by clicking-on or activating an edit icon  1916  or the like associated with a project. The edit icon  1916  may be a symbol that connotes an editing function. 
       FIG. 20  is an example of a web page, GUI  2000  or the like in a data quality management system to update or edit a project in accordance with an embodiment of the present invention. The GUI  2000  may be presented to a user in response to the user clicking-on the edit icon  1916  in GUI  1900  ( FIG. 19 ). The GUI  2000  may include a “Title” field  2016  to enter a project title. The GUI  2000  may also include a “Stage” field  2018  to enter a stage at which the project may be. The GUI  2000  may further include a “Leaders” field  2020  to identify project leaders, a “Parent Project” field  2022  to enter or select any parent project and a “Description” field  2024  to enter or edit a description of the project. The project information entered or edited in the GUI  2000  may be updated by the system in response to the user operating an “Update” button  2026 . 
       FIG. 21  is an example of a web page, GUI  2100  or the like in a data quality management system to add or update a category in a project definition in accordance with an embodiment of the present invention. The GUI  2100  may be presented to a user in response to the user clicking-on an “Add” link in GUI  2000  ( FIG. 20 ) to add a new project category or in response to the user clicking-on an edit icon  2030  in GUI  2000 . The GUI  2100  may include a “Title” field  2116  to enter or edit a title for the project category, a “Project” field  2118  to enter or edit a project designation, and a “Description” field  2120  to enter or edit a description of the project category. The new project category information entered in GUI  2100  may be added to the system in response to the user clicking-on or operating an “Add” button  2122 . 
     If the edit icon  2030  was activated in GUI  2000  ( FIG. 2 ) an Update GUI (not shown in the drawings) may be presented to the user. This Update GUI may be the same as GUI  2100  except the button  2122  may be labeled “Update” rather than “Add” in GUI  2100 . 
     The flowcharts and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. 
     The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more features, integers, steps, operations, elements, components, and/or groups thereof. 
     Although specific embodiments have been illustrated and described herein, those of ordinary skill in the art appreciate that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown and that the invention has other applications in other environments. This application is intended to cover any adaptations or variations of the present invention. The following claims are in no way intended to limit the scope of the invention to the specific embodiments described herein.