Look at the information users need to read or supply in order to complete each task. You'll see that this information is recorded in the designer's model as relationships between objects and attributes of objects. This also helps distinguish views from other objects. Note that in any UI system, a view may comprise several more specific views. For example, a hotel's views may combine views of rooms and guests.
All user interaction is accomplished through views.
Whenever users deal with an object, you must present them a view suited to the tasks they want to perform. Next you'll add objects to the system to represent the users of the system, showing how they employ each view to perform their tasks. In early iterations, you can usually show only the interactions between users and views. However, in later iterations you should also show details of interactions between views and the objects they represent. But before it can be of any benefit, that designer's model must be converted to a programmer's model, and then to an implementation that can be deployed.