1) Verify each attribute in the model. Does this attribute belong in the class you have put it in? In other words (IOW), can you answer the question: What purpose does this attribute serve in this class? And: Does it match the requirements? If the attribute does *not* serve a purpose then remove it from the model. If the attribute belongs to a different class, then move the attriubte to that class. If there is an attribute mentioned in the requirements that does *not* yet exist in the model, the find the appropriate class and add it.
2) Verify each relationship in the model. What purpose does this relationship serve in the model? Does that purpose match a requirement? If the relationship does *not* serve a purpose then remove that relationship. If the requirements define a relationship that does not exist in the model, then add that relationship to the model.
3) Verify each relationship multiplicity in the model. What purpose does this multiplicity serve in the model? Does that purpose match a requirement? If the multiplicity does *not* serve a purpose, then remove it. Is the multiplicity the correct value as defined in the requirements? Does the multiplicity value use the simplest form? (for example, "N..N" should be just "N" and use standard notation so instead of "1..n" use "1..*") If the requirements define a multiplicity that does not exist in the model, the add that multiplicity.
