LYCOS RETRIEVER 
Data Warehouse: Users
built 276 days ago
The Data Warehouse is organized according to a decision model, called Monitor School Performance, which mirrors users’ analytic processes for making decisions. This decision model involves the evaluation of academic performance through four processes that:
Source:
Once the Planning and Design stages are complete, the project to implement the current Data Warehouse iteration can proceed quickly. Necessary hardware, software and middleware components are purchased and installed, the development and test environment is established, and the configuration management processes are implemented. Programs are developed to extract, cleanse, transform and load the source data and to periodically refresh the existing data in the Warehouse, and the programs are individually unit tested against a test database with sample source data. Metrics are captured for the load process. The metadata repository is loaded with transformational and business user metadata. Canned production reports are developed and sample ad-hoc queries are run against the test database, and the validity of the output is measured.
Source:
Access to the Data Warehouse is granted based on an employee's needs in his/her department as authorized by the department manager and the data subject owner. Depending on the employee’s function and authorization, users have access to a defined data subset based on department, college, or division as appropriate.
Source:
The EDS is the cornerstone of the Data Warehouse. It can be accessed for both immediate informational needs and for analytical processing in support of strategic decision making, and can be used for drill-down support for the Data Marts which contain only summarized data. It is fed by the existing subject area operational systems and may ... contain data from external sources. The EDS in turn feeds individual Data Marts that are accessed by end-user query tools at the user's desktop. It is used to consolidate related data from multiple sources into a single source, while the Data Marts are used to physically distribute the consolidated data into logical categories of data, such as business functional departments or geographical regions. The EDS is a collection of daily "snapshots" of enterprise-wide data taken over an extended time period, and thus retains and makes available for tracking purposes the history of changes to a given data element over time.
Source:
There is always one thing you can count on: "Requirements Creep." The more successful the data warehouse, the faster requirements creep will occur. As your users become more sophisticated they will want more and more capabilities. If you can respond quickly and efficiently, your users will again sing your praises (and upper management will definitely take notice :-). Make sure that you have designed in the ability to add features from the very beginning. Remember to design in scalability and flexibility at all phases of development.
Source:
In the final deployment of the data warehouse project, database or operating systems independence is a fallacy. As this text will detail, at some point the IT team must choose an infrastructure and become dependent upon their choices. Software companies have invested hundreds of millions of dollars in the research and development of commercial-off-the-shelf (COTS) tools for the user and development community. The "vendor-independence" movement has sometimes caused managers and developers to resist or avoid using such high quality products as a query environment. With the broad number of databases and systems that COTS products interfaces with, comes increasing flexibility in integrating a large scale environment. The data warehouse manager can maximize the quality of a data warehouse project through the management of these design choices.
Source:
MORE ABOUT
Users