CRC modeling - 4
Allows for formal walkthroughs
Give reviewers subsets of the CRC cards but no one has cards that provide responsibility to one of their own cards
Divide use-case and user interface scenarios into categories
A “leader” reads the scenario, a token is passed from class to class as objects are named
Group determines if the class is able to meet the requirement from its responsibilities
Collaborations are also checked