Defining technical requirements for a datawarehouse, an existing one at that
Page 1 of 1
Defining technical requirements for a datawarehouse, an existing one at that
I have no experience doing requirements documentation for a data warehouse, and am hoping an experienced practitioner or two can provide some practical lessons from documenting a data warehouse.
To add an extra twist, the data warehouse is already in place and in use. While this helps to see the functionality in-place, it does present some confusion as to what requirements are real and what are best left to the implementation level of things.
Any tips? References to check out?
To add an extra twist, the data warehouse is already in place and in use. While this helps to see the functionality in-place, it does present some confusion as to what requirements are real and what are best left to the implementation level of things.
Any tips? References to check out?
ckstevenson- Posts : 2
Join date : 2009-10-19
Similar topics
» Add New or Drop existing conformed dimension in existing DWH
» ETL Technical Metadata Tools ?
» technical support domain
» Technical architecture for budgetting information
» Segregate or not Analyst, Technical and Developer role
» ETL Technical Metadata Tools ?
» technical support domain
» Technical architecture for budgetting information
» Segregate or not Analyst, Technical and Developer role
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum