電信產(chǎn)業(yè)數(shù)據(jù)儲(chǔ)藏技術(shù)概要(文件)
【正文】 ablementw However …. 1 of 2 DW projects fails !!!!8 Reasons of Failurew Success is hard to measure…Failure is easy !!!w Reasons why DW projects fail– No more funding– Bad data quality– Users unhappy with query tools– Only a small percentage of users use the DW– Poor performance– Inability to expand– Data is not integrated– ETL process does not fit batch windowCritical Success Factorsw Common Data Definitions– Consolidate different sets of departmental definitions (Extremely difficult ….)– These definitions are rarely documented !!!– Each project should have a glossary of business terms to support the projectLegacy ApplicationsVSAMIDMSIMS CICSCOBOLMultimediaDocumentsPackagedApplicationsGroupware DatabasesCritical Success Factorsw Welldefined transformation rules– Data from source systems will be transformed in one way or another.– Data will always be specifically selected, recorded, summarized and integrated with other data– Transformation rules are critical to do this correctlyCritical Success Factorsw Properly trained users– Regardless of how easy to use a tool is, users must be trained– Training should be geared to the level of user and the way they use the data warehouse– Types of training? how to use the tools? how to use any custom developed applications? availability of predefined queries reports? the data itself, and data structures for more powerful usersCritical Success Factorsw Expectations municated to users– Performance.– Availability of the data warehouse.– Functions and what data is accessible, what predefined queries and reports are available, the level of detail data and how data is integrated and aggregated.– The expectations of simplicity and easeofuse.– The expectations of accuracy in both data cleanliness and what the data means.– Timeliness of when data will be available, and frequency of refreshing the data.– Schedule expectations (system delivery).– Where support es from.Critical Success Factorsw Ensured user involvement– Solicit requirements input from users.– Have the users involved throughout the project.– Best scenario Business and Technical usersCritical Success Factorsw The project has a good sponsor– The best sponsor is from the business side, not IT.– Should be willing to provide ample budget.– Should be able to get resources needed for the project.– Should be accepting problems as they occur, and not use them as an excuse to kill the project.– Should be in serious need of DW capabilities to solve a problem, or gain some advantage.Critical Success Factorsw The team has the right skill set–Resources with the right skill sets should be dedicated to the team.–Critical roles should report directly to the PMCritical Success Factorsw The schedule is realistic– Unrealistic schedule most mon cause of failure.– Project schedules should be imposed with the concurrence of the PM and team members.– Schedules must include task and effort required.Critical Success Factorsw Proper project control procedures (change control)–The scope will always change.–Changes in the project must be managed and controlled.Critical Success Factorsw The right tools must be chosen– Decide on the right categories of tools– Tools must match requirements of the anization, users and project.– Tools must work together without the need to build interfaces or special code.EISDataWarehouseOLAPReportingHow to measure successw Functional quality–Do the capabilities of the data warehouse satisfy the user requirements?–Does the data warehouse provide the information necessary for the users to do their job?How to measure successw Data quality–Ask the users if their reports are accurate–Maintain a scorecard on the quality of the data.How to measure successw Computer performance–Query response time–Report response time–Time to load/update/refresh the data warehouse–Machine resourcesHow to measure successw User satisfaction–Is the DW solving their business problem?–Does the DW make their jobs easier?–Do they access the DW often to obtain information?–Are they asking for more information to be put into the DW?Data Warehouse Applicationsw Is a process … not a onetime project.w Is business driven … not product/technology.w Effort 8020 : 80% backend, 20% frontend.w Implementation required … not buyandinstall !!!w Is different for every anization.w Must be expandable, and more importantly, avoid repetition.w Should be built, using integrated technology and tools.Summaryw More anization realize the importance of DW.w DW is being part of the Inter.w Avoid the known failures before even thinking on how to achieve success.w Success is not always measured by numbersw DW is a solution which must consist of integrated tools,
教學(xué)課件相關(guān)推薦
鄂ICP備17016276號(hào)-1