In the free Data Model Scorecard Validation Tool, there are five “killer” questions out of the over 150 questions that are part of the tool, that if answered improperly will automatically score the model with the lowest setting of “Poor”. If you’ve used the tool, you might have experienced one or more of these questions :L).
A model can represent how a business works today or how a business might work sometime in the future. A model with the “as is” perspective captures how the business works today. If there are archaic business rules, they will appear on this model even if the business is planning on modifying them in the near future. A model with the “to be” perspective can represent any time period in the future. Whether end of the year, five years out, or ten years out, a “to be” perspective represents an ideal view of the organization. When a model needs to support an organization’s vision or strategic view, a “to be” perspective is preferred. Note that most organizations who need a “to be” perspective first have to build an “as is” perspective to create a starting point.
If we are modeling the current ordering process, we would expect the data model to capture the “as is” perspective. If we are building a data model for a proposed data warehouse that does not exist today, we would expect the “to be” perspective.