We have an 3rd party HR application that takes exactly this approach. Mainly to implement row based security in the app by joining in a table that contains the employee id's that staff are permitted to see. The views get used for basic CRUD operations in the app screens and also in reports. Stored procs are used when a process requires more than a single query to accomplish the task. In this way most of the business logic has been moved into the database.