title: Naming conventions for MVVM?
body: <p>I'm struggling a little over naming classes for my MVVM application.</p>
  
  <p>I have a TrainingCourse, which is called a TrainingCourseViewModel, but I can have many of these, so I have created a TrainingCourseViewManager to hold the list of courses and allow them to be added/removed. I also have an EmployeeViewController which has a reference to other view models as well as the TrainingCourseViewManager.</p>
  
  <p>The EmployeeViewController essentially wraps all of the other view models and view managers and when its instantiated it gets the employee and in turn instantiates each of the view models and view managers.</p>
  
  <p>The question is... What naming conventions are people using?</p>
  
  <p>Should my TrainingCourseViewManager be called TrainingCoursesViewModel and should my EmployeeViewManager be called EmployeeViewModel?</p>
  
  <p>Thanks</p>