I also posted this question in the user interface application block group, but since I am also interested in the point of view of architects, I feel it also belongs in this group. The user interface application block implements a MVC pattern. I might get the point of the controller part wrong, but I thought the whole idea here was to seperate views (user interface) and business processes (the processes that use business objects). Personally I feel that the controller as put forward by this block does a pretty bad job at defining and seperating out the business processes. A business process is not just a collection of actions which can be called in any order by the views. However, by implementing the actions as methods, that is what the controller does. There is a process flow that should be enforced. Beside that, the navigation is definitely not part of the business process. Two different applications using the same process can have totally different navigation. Now, if I have missed some functionality of this block or misunderstood the functionality, please explain to me how I can achieve a clear definition of the business process (not the navigation path with some processing thrown in). Does anyone know of a framework that seperates the processes?