How to stay away from abstraction/generalisation to Data vault mode or don't we?

Generalization or abstraction is a technique used in data modelling to be able to create a flexible storage of data where we are minimizing the need for reengineering..... or doesn't it work that way. And if not how to avoid generalization and abstraction without getting into the woods of too many of the same trees?

First question to be answered: Is it really true that abstraction and supertyping make your model more flexible?
Second question: Is an abstracted and generalized model useful?

The ELM methodology will guide you to find the balance between abstraction/generalization and specialization without getting lost.

The end result of this whole process is a Logical Data model which is a more or less one-to-one translation to the physical Data Vault model.

And as a bonus the whole process is business driven, business-facing and keeps business people (the non-IT folks) connected to your data model and be the valuable partner.

Join DAMA SA and Remco Broekmans to learn more!