These are quotes from the specs. While it does not specifically say anywhere that you have to have MVC pattern. No in these quotes interpretation is the key. And you will find that you can argue both. My opinion is that MVC would win out because of the benefits of maintainability, readability, and extensibility.
With MVC, if you want to change the View/GUI, then you can also knowing that you won't have to change the Model or view. Now in some cases you will have to change all three, but when someone say where do I find "A", you can saa is "A" GUI based, Data bases, or Business Process/Action based. Based on their answer you know where to go. If it is all in one class, one file, then you will probably have to do some searching for it. Of course if you wrote it recently, then you know where to go. But to a Junior Programmer who has never seen the code before, it will take lots of time for that person to find it. And we all know that the most costs on any project is in maintenance.
Your user interface should be designed with the expectation of future functionality enhancements, and it should establish a control scheme that will support this with minimal disruption to the users when this occurs.
User Interface (Total 24)
layout uses good/accepted Human/Computer Interaction (HCI) principles (24)
General Considerations (Total 58)
ease of use (23)
coding standards and readability (23)
clarity and Maintainability maintainability of the design and implementation (12)
Mark