When you adhere to the model–view approach, you separate the classes that embody knowledge about your application's domain, called model classes, from classes that embody knowledge about information display, called view classes.
