This post was originally published here by Valtech UK consultant Sachin Kanadia. I was playing around attempting to implement course grained MVVM in WPF. I used the Prism Application Block to achieve the most part. I came up with a few resulting base classes that formed the crux of the application I was deving at the time. [...]
MVC, MVVM, MVPI decided to get to the bottom of these patterns and what the differences are. The most common motivation behind these patterns are the cross cutting of concerns, swapping out the user interfaces (i.e. windows for web) and of ease of unit…
In the first part of this Object-Oriented Design principles series, I covered the Single Responsibility Principle (SRP). I had also covered the Liskov Substitution Principle (LSP) on a previous post. So let’s move on to another Object-Oriented Design P…
The Liskov Substitution Principle was initially introduced by Barbara Liskov in a 1987 conference keynote address entitled Data abstraction and hierarchy. LSP is also part of SOLID, a group of five Object-Oriented Design Principles put together by Rob…
The first thing I learnt when I started with Object-Oriented Programming was that an object should have state and behaviour. And indeed, that’s how it was back then. However, since J2EE (Entity Beans) and other ORM tools like Hibernate, iBATIS, TopLink…
Over the years, working in different web-based Java projects, I noticed that there is a big confusion about the boundaries and overlaps between MVC, that is an architectural pattern, and a multi-tier architecture (also known as n-tier architecture). Th…