I was thinking that MVC is actually a representation of a Turing Machine: there is a Controller (input tape), Model (internal state), and View (output tape).
Although I mostly think that this is nothing more than an interesting observation, it could have meaningful uses. For example, something not defined by any interpretation of MVC is the issue of inter-connection between components beyond the one set. Most of the time this can be one Controller working with several Models and Views. I wonder if this idea of TMs could be applied to design the relationships between many Controllers. That would mean that Controllers would have to be set up as if they were the Views for other Controllers that they were interested in (the same way that the output tape of one machine is made as the input to another).
I don't really think that this is the best way to think of it, but it seems interesting that something as abstract as a design paradigm may define enough to be reducible to the fundamental component of logic (a TM).
Just something to think about,