Not knowing your business requirements or the scope of the application I would have to blindly say - it's a great approach :) As a team player I rarely, if ever, question another developers approach to solving a problem - we all know that
if 10 of us were thrown into a room with a problem we would all come out with different ways of solving it (with the problem solved they would all be right).
With that said. I'd have to ask some questions so that "you" could determine if it is the best approach. Is this an enterprise level application? Is there a need for the business logic to be reused (now or in
If the answer is yes you might want to consider the
Separated Presentation pattern which is well suited for PRISM's dependency injection (DI) environment. By creating a Business Logic Layer and Data Access Layer (both with their own interfaces) you get the same benefits WITH reusability