BASICS: VDDW Architecture   >   What's Left Out

 
  • Some may note that everything diagrammed and described about the VDDW makes no mention of many different sub-disciplines within the DW / BI industry. What about the ODS? What about textual integration engines and content management repositories?  What about real-time DW concerns? What about data mining? Web ClickStream DW's?  Predictive analytics and interactive visualization? What about metadata management?

  • The DW/BI field is indeed a rich one, quickly changing, and also, arguably, a cluttered one with numerous parties offering different solutions and tools for which the precise distinguishing characteristics are sometimes hard to identify and difficult to which to assign hard value.  

  • A common issue that seems to be felt across many organizations is an ongoing dearth of high-quality, performance improving insight coming out of their DW / BI systems, despite significant investments made to that end. This is primarily a complicated modeling and integration issue, not a tool issue. 

  • The VDDW is a design and integration approach for how to most efficiently cobble together several different tools and disciplines so as to deliver a single system that addresses these deficiencies, by beginning with the elucidation of NOP Performance as the driving design criteria. 

  • VDDW neither precludes nor presumes any of these other areas of focus, but rather emphasizes getting the most important pieces in place first, around which other components can be integrated, as needed, and with clearer context and prioritization.

  •