Gadgets and Technology

In order to produce a set of production-quality deliverables that grow to a full solution, the data warehouse manager must make sure that the overall requirements are understood, and that the overall system architecture is in place. The business requirements and technical blueprint phases are designed to address those two points. By understanding the business requirements for both the short and medium term, the data warehouse manager can design a solution that satisfies the short-term need, but is capable of growing to the full solution. Additionally, at least 20% of the time within the business requirements phase should be spent on understanding the likely longer-term requirement. Any less effort than that will affect the feasibility of designing a data warehouse that can grow to satisfy a future requirement.

Once done with domain name registration, you cannot change anything about your cheap web hosting deal, whether you get dedicated servers or not, your dsl is of no use either.

The technical blueprint phase must deliver an overall architecture that satisfies the longer-term requirements, and a definition of the components that must be implemented in the short term in order to derive any business benefit. A detailed design of the database is not produced at this stage; rather, the most significant components are identified and sized. In practice, these will tend to be the largest tables that contain information about the business: that is, the major fact tables and associated dimensions.