Let me answer your question more specifically and a bit well-described way. First of all,
MVC framework[
^], is not an approach of ASP.NET application building only. It is an architecture in software development, used for distributing the source code into three categories,
- Model -- I will explain it a little better below, for now they contain the data.
- View -- It is the actual HTML content of your website
- Controller -- The back-end logic of your application, including the handlers
Now coming to the Model part of the MVC. ASP.NET uses the same pattern for application development,
Model-view-controller. A model is the class, that defines the
structure of data in your application. It simply defines what members your object has, and a few other functions related to your data (such as getting enumerable for your objects; list).
Secondly, you do not need Entity framework to work with Models in ASP.NET MVC. A model is just the definition, it doesn't has to be coming from Entity framework, or a database even. You are not supposed to have a database to use a Model. I will attach an article of mine with this answer to support this statement.
You can use those stored procedures to execute and return the data, using that data you can fill your models. You will be using the Controller to execute the Sql commands to get the data from a stored procedure... And thus then fill in the Model. Just make sure you're having a member inside your model, which can hold a list. Please see the attached article; for more on this.
If you're not using Entity framework, then don't use it. Who's forcing you to use one? I will not answer this part.
This is the article of mine, that explains ASP.NET MVC for beginners and intermediates. It doesn't use Entity framework, because Entity framework has been explained well by the ASP.NET developers. That is why I tried using JSON (not SQL database) for the data source for my application. I guess that article is a perfect for your condition here. You should try it a try. It will clarify all of your concepts and confusions.
Understanding ASP.NET MVC using real world example, for beginners and intermediate[
^]