Hello,

I would like to ask a plain and simple question about the Model-View-Controller architecture, in particular its implementation in ASP.NET - should the UML Class diagram for my application include all the controllers and views and their relationships, or should I just include my model classes, i.e. the entities that are the heart of the relationship, you know - like in an ordinary application - i.e. User, Administrator, Student, Teacher, Course, Grade etc...?

Thank you for any answer,

regards, robertmacedonia

Recommended Answers

>should the UML Class diagram for my application include all the controllers and views and their relationships

Strictly speaking. No.

>should I just include my model classes

Yes.

Jump to Post

All 2 Replies

>should the UML Class diagram for my application include all the controllers and views and their relationships

Strictly speaking. No.

>should I just include my model classes

Yes.

>should the UML Class diagram for my application include all the controllers and views and their relationships

Strictly speaking. No.

>should I just include my model classes

Yes.

Thanks a lot. I was hoping to hear something like this :)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of 1.20 million developers, IT pros, digital marketers, and technology enthusiasts learning and sharing knowledge.