MVC based system modeling and architecture

Question

hey,
I'm working on a modeling project for my software engineering class.
the system I'm trying to design is an e-commerce app that is based on MVC pattern.

now, does the fact I'm using MVC mean that every request goes from View to Controller to Model and back
like in the sequence diagram below(bear in mind the 'Administrator' class belongs to the Controller and the the 'Product' is a model class), or should I skip the 'UI' column?

also, this is my class diagram bellow, I tried to separate it to Model (in yellow), View, Controller (in blue)
I'm just not sure how everything should be connected, is the idea of an API class for the Controller correct? or should those functions be embedded in the relevant classes?

really any comments, suggestion etc. are welcome!
thanks

Answer 1

in the original MVC pattern from smalltalk, when the action modified the model via a message, and the model directly sent messages to the view. the messages were typically small datagrams.

the MVC model with web pages is slightly different. an MVC action is invoked by a browser get/post or Ajax request. the request data to bound to action model. the action processes the action model, and then creates the view model. the view model is passed to the view engine to build the response, which returns the response data (often html) to the browser.

often the same model class is used for the action model and the view model. but do not confuse the action/view models with the database/business models. most tutorials will use the same model for simplicity of the example, and implement simple CRUD operations.

Answer 2

Hi @ROG ,
Let's learn the MVC Architecture. MVC stands for Model, View, and Controller. MVC separates an application into three components - Model, View, and Controller.
Model objects store data retrieved from the database. View in MVC is a user interface. View display model data to the user and also enables them to modify them. The controller handles the user request. Typically, the user uses the view and raises an HTTP request, which will be handled by the controller. The controller processes the request and returns the appropriate view as a response. So, if you want to do some action functions , you could write into the controller.

Best regards,
Yijing Sun

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our  documentation  to enable e-mail notifications if you want to receive the related email notification for this thread.