Formulating your requirements
I won't try to write an exhaustive requirements engineering paragraph here. Almost every Data Architect is already using a comprehensive method to collect requirements and derive suitable artifacts from them. Let's try to emphasize the direction and the results that should be focused on when the requirements have been gathered and engineered.
Asking in the right direction
When you are planning for a modern data warehouse, you need to come up with questions that must be answered. Please see the Questions section at the end of this chapter for more examples. Let's just go through some examples here, to give you an idea:
- For the main storage component, what is your expected volume of data?
- How will you put data in your system? Are you already using an ETL/ELT tool, and can it connect to all the sources and targets that you need to maintain?
- How will data be transformed throughout the system? Do you want to perform...
