Jump to content

Class-responsibility-collaboration card: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
Line 19: Line 19:
*[http://alistair.cockburn.us/crystal/articles/ucrcc/usingcrccards.html Using CRC Cards]
*[http://alistair.cockburn.us/crystal/articles/ucrcc/usingcrccards.html Using CRC Cards]
*[http://www.excelsoftware.com/crccards.html CRC cards for Software Design, a Commercial Product ]
*[http://www.excelsoftware.com/crccards.html CRC cards for Software Design, a Commercial Product ]
*[http://www.merobase.com Draw CRC cards online and search source for code matching them ]


== See also ==
== See also ==

Revision as of 20:43, 18 May 2007

Class-Responsibility-Collaboration cards (CRC cards) are a brainstorming tool used in the design of object-oriented software. They were proposed by Ward Cunningham. They are typically used when first determining which classes are needed and how they will interact.

CRC cards are usually created from index cards on which are written:

  1. The class name
  2. Its Super and Sub classes (if applicable)
  3. The responsibilities of the class.
  4. The names of other classes that the class will collaborate with to fulfill its responsibilities.
  5. Author

Using a small card keeps the complexity of the design at a minimum. It focuses the designer on the essentials of the class and prevents him from getting into its details and inner workings at a time when such detail is probably counter-productive. It also forces the designer to refrain from giving the class too many responsibilities. Because the cards are portable, they can easily be laid out on a table and re-arranged while discussing a design with other people.

A common method to determine what cards should be created is to read a specification for the program being designed and consider if each noun should be a class and if each verb should be a responsibility of the noun or class that it belongs to. Naturally, the existence of a noun or verb does not require a class or responsibility in the program, but it is considered a good starting point.

See also