Also known as �requirements analysis and definition,� the discover step requires a business-centric approach, especially in data warehousing projects, since the output from a data warehouse needs to support the organizational goals.. Data warehousing project management person with authority over resources appropriate to project (data warehouse requires more authority and resources than data mart) overview of project (mission, scope, goals, objectives, benefits) project activity description (activity list and work breakdown structure). No data warehousing project should commence without: a clear statement of business objectives and scope; the goal of the design process is to define the warehouse components that will need to be built. the architecture, data and application designs are all inter-related, and are normally produced in parallel. a data warehouse is not.
Dplanning for a data warehouse. a data warehouse project is more like scientific research than anything in traditional is! a technical proof of concept for data warehousing. this is the goal of way too many pilot projects. suffice it to say data warehouse projects justified exclusively on technical grounds have the highest failure rate.. Warehouse. for example, when a project component is stored in the warehouse, they might want to annotate it with the unique id of a defect from a corporate defect tracker. these annotations could be important to enable integration of warehouse data with other systems.. This article is excerpted from a book tentatively titled, data warehouse project management (addison-wesley, spring 2000). all material is copyright addison wesley longman, sid adelman and larissa moss. it is the third in a three-part series on data warehouse goals and objectives..
No comments:
Post a Comment