A ModulusCount class, which might have a master window and two slave windows, one for the integer result of dividing the master windowís value by a certain number, and one displaying the integer remainder of that division, would be a simple reuse of this analysis. DivisorCountís evenCount could represent the result of integer division (the number of times the divisor evenly fits into the masterís value), while DivisorCountís oddCount could represent the integer remainder of the division, the odd part left over after integer division. ModulusCount would thus have two slave windows, Integer Division and Modulus. ModulusCount would be a subclass of DivisorCount. It would inherit all of DivisorCountís behaviours, but in addition it would need to know its divisor, and it would have to override the inherited increment and decrement methods to implement modulus functionality. Since in this reuse analysis, DivisorCount would have no instances, it becomes an abstract class. ModulusCount would have to be able to directly access the values of its slave windows. Fortunately, the slave models are inherited from DivisorCount, which creates them as IntegerCount instances, which understand the value: message, inherited from Count. The ButtonLessViewContainer class would serve perfectly well without modification or subclassing.