Misplaced Pages

Business intelligence deployment

Article snapshot taken from[REDACTED] with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
The topic of this article may not meet Misplaced Pages's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted.
Find sources: "Business intelligence deployment" – news · newspapers · books · scholar · JSTOR (September 2015) (Learn how and when to remove this message)
This article provides insufficient context for those unfamiliar with the subject. Please help improve the article by providing more context for the reader. (September 2013) (Learn how and when to remove this message)
This article may be confusing or unclear to readers. Please help clarify the article. There might be a discussion about this on the talk page. (September 2013) (Learn how and when to remove this message)
This article is an orphan, as no other articles link to it. Please introduce links to this page from related articles; try the Find link tool for suggestions. (October 2015)
(Learn how and when to remove this message)

Utilising the DW/BI system is the final step before business users gain access to the information. The first impression the business community gets is when introduced to the BI frontend drives. Because acceptance from users is important, the deployment must be thoughtfully planned to ensure that the DW/BI system can perform and deliver the results it is designed to deliver. To ensure that the implementation can perform and deliver it has to be exposed to extensive end-to-end testing . The process of testing is an ongoing activity along the development process, because defects that should be correct later in the lifecycle are difficult to find and are associated with exponentially increasing costs. A way of securing that the testing is done through the development lifecycle is to follow a methodology. Kimball prescribe that before adding the DW/BI system, it should have passed a mock test that will cover the following procedures;

  • Testing procedures
  • Data quality
  • Operations process testing
  • Performance testing
  • Deployment testing
  • User desktop readiness.
  • Documentation and Training
  • Maintenance and Support

References

  1. Kimball et al., The Data Warehouse Lifecycle Toolkit, Second Edition. New York, Wiley, 2008, ISBN 978-0-470-14977-5, 542
  2. Information Management: Strategies for Testing Data Warehouse Applications


Stub icon

This business-related article is a stub. You can help Misplaced Pages by expanding it.

Categories:
Business intelligence deployment Add topic