Let us suppose we are going to start new project - application that contains some business logic, user interface on ASP.NET, WPF or both of them. We\'d like to use ORM or DA
Start by not directly thinking about either, rather "model" (preferably on paper) what parts your application will have from the users point of view.
If you have a clear mental picture of that model, You can divide the parts up in common and specific little elements which you can translate to both object definitions and database tables.
I find this method to cut database normalization time and effort significantly.