My way to view business requirements gathering for data warehousing and business intelligence projects is as a process to collect or gather information needs. Therefore, I see the process more focused on finding those business questions that require the right answer based on a single version of facts (i.e. the data warehouse).
These findings of information needs have to be encompassed with verification of data availability, which implies more that knowing that there is one or more sources of data containing records that can be utilized to answer the business question. It is important to confirm access to the data, frequency of the refresh, feasibility of the data integration, and many other technical and business considerations.
I indicate business considerations, as sometimes if not always, getting access to the right data involves political decisions.
After confirming that data is or can be available in the data warehouse, then we kind of cover the what (data) and how often (frequency) the answers will be ready to be used. This is not enough, as we have to deliver this information at the right time and in the right format. It is then when we start moving towards the business intelligence part of the solution. So far, we have travesed the data integration including ETL-ing and the data warehousing components.
It is important to filter out information wants from actual information needs. During the exercise, you will realize that decision makers will describe those information needs in different formats or presentations. You have the task of extracting measures and dimensions from each statement. In addition, you have to identify cross-functional requirements involving more than one business unit.
Business questions relate to one or more operational systems. A matrix is helpful to cross-validate and organize systems, measures, dimensions, and hierarchies.
PENDING: Business goals, business objectives, key contacts, etc.
