I'd love to give you a ready-made, one-size-fits-all questionnaire. The fact is, there really is no such thing....
You are well on the way of developing a comprehensive approach to gathering requirements. I encourage you to not overlook the technology architecture, infrastructure and operational procedures. These aspects all have requirements that need to be flushed out. I also firmly believe that understanding the business process model as well as enterprise data model is critical to fully understanding the functional requirements of your data warehouse. Understanding the process model drives to understanding the corporate & functional goals, key performance metrics and business information needs. These drive towards understanding what your information access layer needs to support.
For More Information
- What do you think about this answer? E-mail us at editor@searchDatabase.com with your feedback.
- The Best Data Warehousing and Business Intelligence Web Links: tips, tutorials, scripts, and more.
- Have an DW tip to offer your fellow administrators and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical data warehousing questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Related Q&A from Mike Lampa
When trying to design a data warehouse, we often try to model the database on the operational data model. Are there any guidelines in trying to ...continue reading
What is a surrogate key in a table?continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.