There are few reasons that contribute to its failure; some of them are related to user requirement analysis.
Kimball et al.(2008) stated that requirement definition phase is paramount and impact almost every decision in DW
project [9]. Most of failed DW projects execute poor requirement definition phase and some of them skip this phase
[12]. They tend to focus on technical issues and not paid enough attention to requirement analysis [10]. Groggy
method of conducting requirement definition analysis will lead to unstable design process [13] and poor
communication between IT people and decision maker [3][10]. With lack of higher-level requirements vision [12], it
is difficult to ensure the project will meet business goal. Furthermore, incomplete or inconsistence requirement lead
developer to incorrect assumption [14]. In other hand, with tremendous amount of users requirements from different
levels and categories cause big challenge to specify important requirement that could lead to business goal [13].