Reconcile the class diagram to the use case model.
Reconcile - Class Diagram Use Case Model
Reconcile terminology and classes
Reconcile the terminology of the use case model to the class names. This seems a bit redundant with the validation between scenarios and
interaction diagrams. However, the point is that there is value in comparing many different sources of the same information. Depending on your
frame of mind, one approach might reveal information not seen using another approach.
Is there a class to handle every resource mentioned in the use case model? When you initially created the class diagram, you used the
vocabulary of the problem domain as documented in the problem statement and use cases. As you continued with your analysis, you very likely
changed these documents. Verify that the new resources are added to (or removed from) your class diagram and that their purpose is fully
defined. Define their interfaces by updating the sequence diagrams.
Using the model, ask questions that require navigation through the model to verify that the objects can in fact support the navigation. For
example, in the Purchase Seats use case, can you get the event name that should be printed on the ticket?
During the use case navigation testing, you will sometimes notice that the path to the answers is rather long and involved.
During design, we will optimize the model using shortcuts called derived associations.