PresentationModel and ViewModel (MVVM) pattern
are a synonym when talking about Prism. However, the MVC and MVP patterns are not. The choice of which pattern to implement greatly depends on your application’s needs and your comfort using each of them. The MVVM pattern, leverages the data binding
capabilities of WPF/Silverlight to reduce the amount of code behind in the view. In the MVP/MVC patterns, the view has to communicate with the Presenter/Controller (via a reference or events exposed through its interface), which handles the complex logic of
the application. This in the code behind of the view.
Have in mind that one of the important advantages of these patterns is the testing capability they offer, by decoupling the presentation
logic from the view. Thus, how much code you will be able to test with each pattern might also affect your choice.
You can read more about this patterns searching the Web (I personally recommend Martin Fowler’s explanation, you can search the Web
for it). Below I will provide some extra links that might make things more clear:
WPF Apps With The Model-View-ViewModel Design Pattern
Model View Presenter
Model-View-ViewModel In Silverlight 2 Apps
Interactive Application Architecture Patterns
Please let me know if this helps.