Use case diagrams for an MVC design pattern

Question

I have this UML use case diagram; I am wondering if in a use case diagram it is appropriate or required to represent the MVC design pattern i.e. controllers, models explicitly within the diagram itself.

I feel the purpose of a use case diagram is to represent the typical interactions the user will perform on the application thus keeping it as simple as possible, without controllers is the ideal approach. This is how I have structured the diagram below.

Should the diagram be good as it is or should it follow the MVC design pattern?

Answer 1

MVC is a design pattern. A use case is an analysis tool. So, I think, a use case diagram showning the MVC pattern would be plain wrong.