Dr Sun,

For this homework we do not need to handle the user checkpoint functionality right? It's only the Admin tasks of add/edit right?

dr Sun , where to get the example codes that you wrote during the class like add/edit  ? Thanks!

Can you clarify this?

Designate a plan to be the official plan of a department, which means all new students of the department will use that plan.

Using your suggested design this means the 'currentPlan' field of the department model.  Is that correct?  Or, did you intend this to mean something slightly different.

Since the user model associates a department with a student  and a department has a currentPlan it seems that the 'official plan' is de facto the 'currentPlan' field.  I don't understand how this would affect the controller or view given the instructions in this exercise.  I guess if we were implementing a user registration in this assignment this would make sense, but that's not a part of HW4...

lmann2 wrote:

Can you clarify this?

Designate a plan to be the official plan of a department, which means all new students of the department will use that plan.

Using your suggested design this means the 'currentPlan' field of the department model.

Yes. Because a department may have multiple plans, this operation simply makes one of them the "currentPlan". Registering a new student would be a different operation which you don't need to worry about here.

In this homework just edit no delete, right