dou you know the meaning of "mvc"? Model, View Controller. Look this up on google and read about it. In short, it's a design pattern
that aims to separate different types of logic into their own components to simply coding as well as to improve code reuse.
The model is the "thing" that contains your data and your business logic. The model is also used as a means to store data that should later be displayed in the view (UI). So in the controller, store the data to be displayed into the view, which in spring mvc, as far as I remember
is just something like a simple map. In the view, you can then later access this model to display it - this is a way to decouple your controller from the view.
Does that help?