Visual Modeling with Rational Rose 2002 and UML

Combining Classes

If different teams are working on different scenarios, a class may be called by different names. The name conflicts must be resolved. This is accomplished mainly through model walk-throughs. Examine each class along with its definition. Also examine the attributes and operations defined for the classes, and look for the use of synonyms. Once you determine that two classes are doing the same thing, choose the class with the name that is closest to the language used by the customers.

Pay careful attention to the control classes created for the system. Initially, one control class is allocated per use case. This might be overkill—control classes with similar behavior may be combined. Examine the sequencing logic in the control ...