{"id":5003159,"date":"2015-12-16T21:45:19","date_gmt":"2015-12-17T05:45:19","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&p=5003159"},"modified":"2023-03-12T12:41:02","modified_gmt":"2023-03-12T19:41:02","slug":"crc-cards","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/crc-cards\/","title":{"rendered":"CRC Cards"},"content":{"rendered":"
\n
\n

CRC cards (for Class, Responsibilities, Collaborators) are an activity bridging the worlds of role-playing games and object-oriented design.<\/p>\n

With the intent of rapidly sketching several different ideas for the design of some feature of an object-oriented system, two or more team members write down on index cards the names of the most salient classes involved in the feature. The cards are then fleshed out with lists of the responsibilities of each class and the names of collaborators, i.e. other classes that they depend on to carry out their own responsibilities.<\/p>\n

The next step is to validate \u2013 or invalidate as the case may be \u2013 each design idea by playing out a plausible scenario of the computation, each developer taking on the role of one or more classes.<\/p>\n

The dialogue may go as follows, for instance: \u201cHello, Authentication Controller! I am a Web Request and I would like the contents of this resource.\u201d \u2013 \u201cVery well, let me have your Credentials so I can give them, together with the name of the operation you are trying to perform, to our Access Control List; I will redirect you to one of our View components depending on the result, etc.\u201d<\/p>\n<\/div>\n<\/div>\n

Origins<\/h2>\n
\n
\n