I'm afraid that you have certain delusion here. Don't you think that the application architecture is reduced to the choice of some design pattern from the list of known patterns? If so, you are gravely mistaken. Even a choice of a set of patterns to use (but architectural and design ones) doesn't define an architecture or design. Yes, MVC seems to be a good choice in your case, but even that cannot be said with 100% certainty based on your information.
More importantly, that would not be all. The architecture is not a list of items or a picture with boxes and arrows. This is an iterative process which should support the application development on all stages. The same thing can be said about the main design elements of the application.
Also, you have to realize that the term "MVC" has two different meanings: 1)
architectural pattern; 2) available
ASP.NET framework.
Many well-known architectural and design patterns are quite good by themselves. At the same time, I can clearly see negative impact of the social factors related to them; in particular, it can be seen on the projects developed by the inquirers of this forum. For many, they become something like a
Procrustean bed. Please see my past answer:
Please suggest me some basic C++ project with design patters.
I would say, the pattern of going from the design patterns to the project architecture/design (instead of going from the project goals) can be considered as yet another
anti-pattern. :-)
This post cannot pretend to be a manual on the organization of project development or development method, but at least it can help you to develop some critical thinking related to this subject.
—SA
Submit an article or tip