Database Reference
In-Depth Information
•
The reason we do data modeling is to confirm and document our understanding of other perspectives. A data
model is a communication tool.
•
Traditionally, data models have been built during the analysis and design phases of a project to ensure that
the requirements for a new application are fully understood and correctly captured before the actual
database is created (i.e. forward engineering). There are, however, other uses for modeling than simply
building databases including mitigating risk, performing reverse engineering, understanding the busi-
ness, and transferring knowledge.
•
Precision
,
with respect to data modeling, means that there is a clear, unambiguous way of reading every sym-
bol and term on the model.
•
There is an iterative cycle between eliciting and documenting requirements.
Remember the three important points that came out of our topic modeling exercise: 1) it's always the same
process of organizing things, 2) be creative on the form used for the data model, and 3) always follow
the 80/20 rule so that you can complete 80% of the data model in 20% of the time.
Half the time in data modeling we are organizers and the other half we are ambassadors.
