I worked on a DW for a major financial institution that had, as a basic requirement, a view for each table. This was used to apply standard filters and joins to some dimension tables. Sometimes is was great. Sometimes is caused serious performance problems, especially if too many dimensions where involved.

I have used the view approach for .NET development effectively, but I created a straight view for each table. On occasion, I had to point the view to a different data source and was able to do so without code changes.

This isn't always allowed in today's "change management" environment.

I still find that "one size" does not fit all. 😉