Expertiza_Wiki - User contributions [en]

CSC/ ECE 517 Fall 2007/wiki3 5 pr

2007-11-20T04:10:10Z

Pmzachar: /* Example 2: */

==Introduction to Patterns==

   Design patterns are recurring solutions to software design problems that is found in real-world application development. Patterns are about design and interaction of objects, as well as providing a communication platform concerning elegant, reusable solutions to commonly encountered programming challenges.
The Gang of Four (GoF) patterns are generally considered the foundation for all patterns. They are categorized in three groups: Creational, Structural, and Behavioral.
 
The attributes that generally define a pattern are:
Pattern name is a descriptive name, that conveys the essence of the pattern.
Synopsis describes the purpose of the pattern, its intent, and the particular design problem(s) it addresses.
Description discusses the participating objects, the communication, and general structure of the pattern.
Forces specifies any constraints that must be considered when using the pattern. For example, a solution to some problem may be constrained by the fact that the solution must run on distributed computers.
Implementation shows how the pattern might be implemented in a specific instance.
Consequences describes the positive and negative effects of employing the pattern.
Related Patterns identifies those patterns that either replace the given pattern in different contexts, extend the given pattern, or collaborate with the pattern in more complex cases. 
==Creator Pattern==
   Creational design patterns are design patterns that deal with object creation mechanisms, trying to create objects in a manner suitable to the situation. The basic form of object creation could result in design problems or added complexity to the design. Creational design patterns solve this problem by controlling this object creation.
   The Creator pattern is used to decide which object should be responsible for creating new objects (instances of some class). There are several cases to consider. 
==Examples==
===Example 1===
Let A and B be objects.
B aggregates A objects. That is, there is a whole-part relationship between B and A. A objects are considered to be a part of B objects.
B contains A objects. This is a stronger whole-part relationship, also called composition. With composition, the A objects have no existence outside of their relationship with B objects.
B records instances of A objects.
B closely uses A objects.
B has the initializing data that will be pass to A when it is created (thus B is an Expert with respect to creating A).
In these cases, B is a creator of A objects. If more than one option applies, prefer a class B which aggregates or contains class A. 
Problem: Who should be responsible for creating a new instance of some class?
Solution: Assign class B the responsibility to create an instance of class A if one of these is true (the more the better):
B “contains“ or compositely aggregates A.
B records A.
B closely uses A.
B has the initializing data for A that will be passed to A when it is crated. Thus B is an Expert with respect to creating A.
In general, the class that contains (aggregates) A is typically the best class to create A because it will probably satisfy one or more of the options mentioned above. 

===Example 2 ===
   Another example is adding a new DataRow to a DataTable. To get a new row, you ask the DataTable to create a new DataRow for you and then add the row to the table.
DataRow myRow = myTable.NewRow();

...

myTable.Rows.Add(myRow);
The DataTable object contains / aggregates DataRows and therefore is the logical class to create the DataRow.
By having the aggregate class create the child class, it not only follows the creator pattern but also supports the Information Expert, High Cohesion, and Low Coupling GRASP(General Responsibility Assignment Software Patterns: gives guidelines for assigning responsibility to classes and objects.) Patterns. 

There are many types of Creator patterns as mentioned below:
Abstract Factory
Builder
Factory Method
Prototype
Singleton
 

==Factory Pattern==
   The factory method is not different from the creational pattern, instead is a type of creational pattern. Like other creational patterns, it deals with the problem of creating objects (products) without specifying the exact class of object that will be created.
   The factory method design pattern handles this problem by defining a separate method for creating the objects, which subclasses can then override to specify the derived type of product that will be created. More generally, the term factory method is often used to refer to any method whose main purpose is creation of objects.
This pattern helps determine who should be responsible for creating objects when there are special considerations, such as complex creation logic.
 
==References==
http://en.wikipedia.org/wiki/GRASP_%28Object_Oriented_Design%29 
http://en.wikipedia.org/wiki/Factory_method_pattern 
http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/Creator.html

CSC/ ECE 517 Fall 2007/wiki3 5 pr

2007-11-20T04:09:44Z

Pmzachar: /* Example 1: */

==Introduction to Patterns==

   Design patterns are recurring solutions to software design problems that is found in real-world application development. Patterns are about design and interaction of objects, as well as providing a communication platform concerning elegant, reusable solutions to commonly encountered programming challenges.
The Gang of Four (GoF) patterns are generally considered the foundation for all patterns. They are categorized in three groups: Creational, Structural, and Behavioral.
 
The attributes that generally define a pattern are:
Pattern name is a descriptive name, that conveys the essence of the pattern.
Synopsis describes the purpose of the pattern, its intent, and the particular design problem(s) it addresses.
Description discusses the participating objects, the communication, and general structure of the pattern.
Forces specifies any constraints that must be considered when using the pattern. For example, a solution to some problem may be constrained by the fact that the solution must run on distributed computers.
Implementation shows how the pattern might be implemented in a specific instance.
Consequences describes the positive and negative effects of employing the pattern.
Related Patterns identifies those patterns that either replace the given pattern in different contexts, extend the given pattern, or collaborate with the pattern in more complex cases. 
==Creator Pattern==
   Creational design patterns are design patterns that deal with object creation mechanisms, trying to create objects in a manner suitable to the situation. The basic form of object creation could result in design problems or added complexity to the design. Creational design patterns solve this problem by controlling this object creation.
   The Creator pattern is used to decide which object should be responsible for creating new objects (instances of some class). There are several cases to consider. 
==Examples==
===Example 1===
Let A and B be objects.
B aggregates A objects. That is, there is a whole-part relationship between B and A. A objects are considered to be a part of B objects.
B contains A objects. This is a stronger whole-part relationship, also called composition. With composition, the A objects have no existence outside of their relationship with B objects.
B records instances of A objects.
B closely uses A objects.
B has the initializing data that will be pass to A when it is created (thus B is an Expert with respect to creating A).
In these cases, B is a creator of A objects. If more than one option applies, prefer a class B which aggregates or contains class A. 
Problem: Who should be responsible for creating a new instance of some class?
Solution: Assign class B the responsibility to create an instance of class A if one of these is true (the more the better):
B “contains“ or compositely aggregates A.
B records A.
B closely uses A.
B has the initializing data for A that will be passed to A when it is crated. Thus B is an Expert with respect to creating A.
In general, the class that contains (aggregates) A is typically the best class to create A because it will probably satisfy one or more of the options mentioned above. 

===Example 2: ===
   Another example is adding a new DataRow to a DataTable. To get a new row, you ask the DataTable to create a new DataRow for you and then add the row to the table.
DataRow myRow = myTable.NewRow();

...

myTable.Rows.Add(myRow);
The DataTable object contains / aggregates DataRows and therefore is the logical class to create the DataRow.
By having the aggregate class create the child class, it not only follows the creator pattern but also supports the Information Expert, High Cohesion, and Low Coupling GRASP(General Responsibility Assignment Software Patterns: gives guidelines for assigning responsibility to classes and objects.) Patterns. 

There are many types of Creator patterns as mentioned below:
Abstract Factory
Builder
Factory Method
Prototype
Singleton
 
==Factory Pattern==
   The factory method is not different from the creational pattern, instead is a type of creational pattern. Like other creational patterns, it deals with the problem of creating objects (products) without specifying the exact class of object that will be created.
   The factory method design pattern handles this problem by defining a separate method for creating the objects, which subclasses can then override to specify the derived type of product that will be created. More generally, the term factory method is often used to refer to any method whose main purpose is creation of objects.
This pattern helps determine who should be responsible for creating objects when there are special considerations, such as complex creation logic.
 
==References==
http://en.wikipedia.org/wiki/GRASP_%28Object_Oriented_Design%29 
http://en.wikipedia.org/wiki/Factory_method_pattern 
http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/Creator.html

CSC/ ECE 517 Fall 2007/wiki3 5 pr

2007-11-20T04:08:42Z

Pmzachar: /* References */

==Introduction to Patterns==

   Design patterns are recurring solutions to software design problems that is found in real-world application development. Patterns are about design and interaction of objects, as well as providing a communication platform concerning elegant, reusable solutions to commonly encountered programming challenges.
The Gang of Four (GoF) patterns are generally considered the foundation for all patterns. They are categorized in three groups: Creational, Structural, and Behavioral.
 
The attributes that generally define a pattern are:
Pattern name is a descriptive name, that conveys the essence of the pattern.
Synopsis describes the purpose of the pattern, its intent, and the particular design problem(s) it addresses.
Description discusses the participating objects, the communication, and general structure of the pattern.
Forces specifies any constraints that must be considered when using the pattern. For example, a solution to some problem may be constrained by the fact that the solution must run on distributed computers.
Implementation shows how the pattern might be implemented in a specific instance.
Consequences describes the positive and negative effects of employing the pattern.
Related Patterns identifies those patterns that either replace the given pattern in different contexts, extend the given pattern, or collaborate with the pattern in more complex cases. 
==Creator Pattern==
   Creational design patterns are design patterns that deal with object creation mechanisms, trying to create objects in a manner suitable to the situation. The basic form of object creation could result in design problems or added complexity to the design. Creational design patterns solve this problem by controlling this object creation.
   The Creator pattern is used to decide which object should be responsible for creating new objects (instances of some class). There are several cases to consider. 
==Examples==
===Example 1:===
Let A and B be objects.
B aggregates A objects. That is, there is a whole-part relationship between B and A. A objects are considered to be a part of B objects.
B contains A objects. This is a stronger whole-part relationship, also called composition. With composition, the A objects have no existence outside of their relationship with B objects.
B records instances of A objects.
B closely uses A objects.
B has the initializing data that will be pass to A when it is created (thus B is an Expert with respect to creating A).
In these cases, B is a creator of A objects. If more than one option applies, prefer a class B which aggregates or contains class A. 
Problem: Who should be responsible for creating a new instance of some class?
Solution: Assign class B the responsibility to create an instance of class A if one of these is true (the more the better):
B “contains“ or compositely aggregates A.
B records A.
B closely uses A.
B has the initializing data for A that will be passed to A when it is crated. Thus B is an Expert with respect to creating A.
In general, the class that contains (aggregates) A is typically the best class to create A because it will probably satisfy one or more of the options mentioned above. 
===Example 2: ===
   Another example is adding a new DataRow to a DataTable. To get a new row, you ask the DataTable to create a new DataRow for you and then add the row to the table.
DataRow myRow = myTable.NewRow();

...

myTable.Rows.Add(myRow);
The DataTable object contains / aggregates DataRows and therefore is the logical class to create the DataRow.
By having the aggregate class create the child class, it not only follows the creator pattern but also supports the Information Expert, High Cohesion, and Low Coupling GRASP(General Responsibility Assignment Software Patterns: gives guidelines for assigning responsibility to classes and objects.) Patterns. 

There are many types of Creator patterns as mentioned below:
Abstract Factory
Builder
Factory Method
Prototype
Singleton
 
==Factory Pattern==
   The factory method is not different from the creational pattern, instead is a type of creational pattern. Like other creational patterns, it deals with the problem of creating objects (products) without specifying the exact class of object that will be created.
   The factory method design pattern handles this problem by defining a separate method for creating the objects, which subclasses can then override to specify the derived type of product that will be created. More generally, the term factory method is often used to refer to any method whose main purpose is creation of objects.
This pattern helps determine who should be responsible for creating objects when there are special considerations, such as complex creation logic.
 
==References==
http://en.wikipedia.org/wiki/GRASP_%28Object_Oriented_Design%29 
http://en.wikipedia.org/wiki/Factory_method_pattern 
http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/Creator.html

CSC/ ECE 517 Fall 2007/wiki3 5 pr

2007-11-20T04:04:47Z

Pmzachar:

==Introduction to Patterns==

   Design patterns are recurring solutions to software design problems that is found in real-world application development. Patterns are about design and interaction of objects, as well as providing a communication platform concerning elegant, reusable solutions to commonly encountered programming challenges.
The Gang of Four (GoF) patterns are generally considered the foundation for all patterns. They are categorized in three groups: Creational, Structural, and Behavioral.
 
The attributes that generally define a pattern are:
Pattern name is a descriptive name, that conveys the essence of the pattern.
Synopsis describes the purpose of the pattern, its intent, and the particular design problem(s) it addresses.
Description discusses the participating objects, the communication, and general structure of the pattern.
Forces specifies any constraints that must be considered when using the pattern. For example, a solution to some problem may be constrained by the fact that the solution must run on distributed computers.
Implementation shows how the pattern might be implemented in a specific instance.
Consequences describes the positive and negative effects of employing the pattern.
Related Patterns identifies those patterns that either replace the given pattern in different contexts, extend the given pattern, or collaborate with the pattern in more complex cases. 
==Creator Pattern==
   Creational design patterns are design patterns that deal with object creation mechanisms, trying to create objects in a manner suitable to the situation. The basic form of object creation could result in design problems or added complexity to the design. Creational design patterns solve this problem by controlling this object creation.
   The Creator pattern is used to decide which object should be responsible for creating new objects (instances of some class). There are several cases to consider. 
==Examples==
===Example 1:===
Let A and B be objects.
B aggregates A objects. That is, there is a whole-part relationship between B and A. A objects are considered to be a part of B objects.
B contains A objects. This is a stronger whole-part relationship, also called composition. With composition, the A objects have no existence outside of their relationship with B objects.
B records instances of A objects.
B closely uses A objects.
B has the initializing data that will be pass to A when it is created (thus B is an Expert with respect to creating A).
In these cases, B is a creator of A objects. If more than one option applies, prefer a class B which aggregates or contains class A. 
Problem: Who should be responsible for creating a new instance of some class?
Solution: Assign class B the responsibility to create an instance of class A if one of these is true (the more the better):
B “contains“ or compositely aggregates A.
B records A.
B closely uses A.
B has the initializing data for A that will be passed to A when it is crated. Thus B is an Expert with respect to creating A.
In general, the class that contains (aggregates) A is typically the best class to create A because it will probably satisfy one or more of the options mentioned above. 
===Example 2: ===
   Another example is adding a new DataRow to a DataTable. To get a new row, you ask the DataTable to create a new DataRow for you and then add the row to the table.
DataRow myRow = myTable.NewRow();

...

myTable.Rows.Add(myRow);
The DataTable object contains / aggregates DataRows and therefore is the logical class to create the DataRow.
By having the aggregate class create the child class, it not only follows the creator pattern but also supports the Information Expert, High Cohesion, and Low Coupling GRASP(General Responsibility Assignment Software Patterns: gives guidelines for assigning responsibility to classes and objects.) Patterns. 

There are many types of Creator patterns as mentioned below:
Abstract Factory
Builder
Factory Method
Prototype
Singleton
 
==Factory Pattern==
   The factory method is not different from the creational pattern, instead is a type of creational pattern. Like other creational patterns, it deals with the problem of creating objects (products) without specifying the exact class of object that will be created.
   The factory method design pattern handles this problem by defining a separate method for creating the objects, which subclasses can then override to specify the derived type of product that will be created. More generally, the term factory method is often used to refer to any method whose main purpose is creation of objects.
This pattern helps determine who should be responsible for creating objects when there are special considerations, such as complex creation logic.
 
==References==
http://en.wikipedia.org/wiki/GRASP_%28Object_Oriented_Design%29
http://en.wikipedia.org/wiki/Factory_method_pattern
http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/Creator.html

CSC/ ECE 517 Fall 2007/wiki3 5 pr

2007-11-20T04:03:42Z

Pmzachar:

==Introduction to Patterns==

   Design patterns are recurring solutions to software design problems that is found in real-world application development. Patterns are about design and interaction of objects, as well as providing a communication platform concerning elegant, reusable solutions to commonly encountered programming challenges.
The Gang of Four (GoF) patterns are generally considered the foundation for all patterns. They are categorized in three groups: Creational, Structural, and Behavioral.
 
The attributes that generally define a pattern are:
Pattern name is a descriptive name, that conveys the essence of the pattern.
Synopsis describes the purpose of the pattern, its intent, and the particular design problem(s) it addresses.
Description discusses the participating objects, the communication, and general structure of the pattern.
Forces specifies any constraints that must be considered when using the pattern. For example, a solution to some problem may be constrained by the fact that the solution must run on distributed computers.
Implementation shows how the pattern might be implemented in a specific instance.
Consequences describes the positive and negative effects of employing the pattern.
Related Patterns identifies those patterns that either replace the given pattern in different contexts, extend the given pattern, or collaborate with the pattern in more complex cases. 
==Creator Pattern==
   Creational design patterns are design patterns that deal with object creation mechanisms, trying to create objects in a manner suitable to the situation. The basic form of object creation could result in design problems or added complexity to the design. Creational design patterns solve this problem by controlling this object creation.
   The Creator pattern is used to decide which object should be responsible for creating new objects (instances of some class). There are several cases to consider. 
==Examples==
===Example 1:===
Let A and B be objects.
B aggregates A objects. That is, there is a whole-part relationship between B and A. A objects are considered to be a part of B objects.
B contains A objects. This is a stronger whole-part relationship, also called composition. With composition, the A objects have no existence outside of their relationship with B objects.
B records instances of A objects.
B closely uses A objects.
B has the initializing data that will be pass to A when it is created (thus B is an Expert with respect to creating A).
In these cases, B is a creator of A objects. If more than one option applies, prefer a class B which aggregates or contains class A. 
Problem: Who should be responsible for creating a new instance of some class?
Solution: Assign class B the responsibility to create an instance of class A if one of these is true (the more the better):
B “contains“ or compositely aggregates A.
B records A.
B closely uses A.
B has the initializing data for A that will be passed to A when it is crated. Thus B is an Expert with respect to creating A.
In general, the class that contains (aggregates) A is typically the best class to create A because it will probably satisfy one or more of the options mentioned above. 
===Example 2: ===
   Another example is adding a new DataRow to a DataTable. To get a new row, you ask the DataTable to create a new DataRow for you and then add the row to the table.
DataRow myRow = myTable.NewRow();

...

myTable.Rows.Add(myRow);
The DataTable object contains / aggregates DataRows and therefore is the logical class to create the DataRow.
By having the aggregate class create the child class, it not only follows the creator pattern but also supports the Information Expert, High Cohesion, and Low Coupling GRASP(General Responsibility Assignment Software Patterns: gives guidelines for assigning responsibility to classes and objects.) Patterns. 

There are many types of Creator patterns as mentioned below:
Abstract Factory
Builder
Factory Method
Prototype
Singleton
 
==Factory Pattern== 
   The factory method is not different from the creational pattern, instead is a type of creational pattern. Like other creational patterns, it deals with the problem of creating objects (products) without specifying the exact class of object that will be created.
   The factory method design pattern handles this problem by defining a separate method for creating the objects, which subclasses can then override to specify the derived type of product that will be created. More generally, the term factory method is often used to refer to any method whose main purpose is creation of objects.
This pattern helps determine who should be responsible for creating objects when there are special considerations, such as complex creation logic.
 
==References== 
http://en.wikipedia.org/wiki/GRASP_%28Object_Oriented_Design%29
http://en.wikipedia.org/wiki/Factory_method_pattern
http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/Creator.html

CSC/ ECE 517 Fall 2007/wiki3 5 pr

2007-11-20T03:56:23Z

Pmzachar:

Introduction to Patterns

Design patterns are recurring solutions to software design problems that is found in real-world application development. Patterns are about design and interaction of objects, as well as providing a communication platform concerning elegant, reusable solutions to commonly encountered programming challenges.
The Gang of Four (GoF) patterns are generally considered the foundation for all patterns. They are categorized in three groups: Creational, Structural, and Behavioral.
 
The attributes that generally define a pattern are:
Pattern name is a descriptive name, that conveys the essence of the pattern.
Synopsis describes the purpose of the pattern, its intent, and the particular design problem(s) it addresses.
Description discusses the participating objects, the communication, and general structure of the pattern.
Forces specifies any constraints that must be considered when using the pattern. For example, a solution to some problem may be constrained by the fact that the solution must run on distributed computers.
Implementation shows how the pattern might be implemented in a specific instance.
Consequences describes the positive and negative effects of employing the pattern.
Related Patterns identifies those patterns that either replace the given pattern in different contexts, extend the given pattern, or collaborate with the pattern in more complex cases. 
Creator Pattern
Creational design patterns are design patterns that deal with object creation mechanisms, trying to create objects in a manner suitable to the situation. The basic form of object creation could result in design problems or added complexity to the design. Creational design patterns solve this problem by controlling this object creation.
The Creator pattern is used to decide which object should be responsible for creating new objects (instances of some class). There are several cases to consider. 
Examples
Example 1:
Let A and B be objects.
B aggregates A objects. That is, there is a whole-part relationship between B and A. A objects are considered to be a part of B objects.
B contains A objects. This is a stronger whole-part relationship, also called composition. With composition, the A objects have no existence outside of their relationship with B objects.
B records instances of A objects.
B closely uses A objects.
B has the initializing data that will be pass to A when it is created (thus B is an Expert with respect to creating A).
In these cases, B is a creator of A objects. If more than one option applies, prefer a class B which aggregates or contains class A. 
Problem: Who should be responsible for creating a new instance of some class?
Solution: Assign class B the responsibility to create an instance of class A if one of these is true (the more the better):
B “contains“ or compositely aggregates A.
B records A.
B closely uses A.
B has the initializing data for A that will be passed to A when it is crated. Thus B is an Expert with respect to creating A.
In general, the class that contains (aggregates) A is typically the best class to create A because it will probably satisfy one or more of the options mentioned above. 
Example 2:
Another example is adding a new DataRow to a DataTable. To get a new row, you ask the DataTable to create a new DataRow for you and then add the row to the table.
DataRow myRow = myTable.NewRow();

...

myTable.Rows.Add(myRow);
The DataTable object contains / aggregates DataRows and therefore is the logical class to create the DataRow.
By having the aggregate class create the child class, it not only follows the creator pattern but also supports the Information Expert, High Cohesion, and Low Coupling GRASP(General Responsibility Assignment Software Patterns: gives guidelines for assigning responsibility to classes and objects.) Patterns.

There are many types of Creator patterns as mentioned below:
Abstract Factory
Builder
Factory Method
Prototype
Singleton
 
Factory Pattern
The factory method is not different from the creational pattern, instead is a type of creational pattern. Like other creational patterns, it deals with the problem of creating objects (products) without specifying the exact class of object that will be created.
The factory method design pattern handles this problem by defining a separate method for creating the objects, which subclasses can then override to specify the derived type of product that will be created. More generally, the term factory method is often used to refer to any method whose main purpose is creation of objects.
This pattern helps determine who should be responsible for creating objects when there are special considerations, such as complex creation logic.
 
References
http://en.wikipedia.org/wiki/GRASP_%28Object_Oriented_Design%29
http://en.wikipedia.org/wiki/Factory_method_pattern
http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/Creator.html

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-30T01:04:06Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

A sample CRC card is as shown in the picture below:

<center>[[Image:CRC_card.jpg]]</center>

[Courtesy: http://www.agilemodeling.com/artifacts/crcModel.htm]

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each card that is used in the example. These explain this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Objects, classes, relationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

A screenshot of the tool that is used to develop the CRC card is shown below:

<center>[[Image:Tools.jpg]]</center>

[Courtesy:http://www.excelsoftware.com/quickcrcintro.html]

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt

     The above link talks about the design that can be used in Java where it makes a reference to CRC cards. How CRC cards helping reducing the design complexity. CRC is a concept and not a feature that is specific to any programming language. Hence in the presentation the author explains how this CRC concept can be used in Java to improve the design. 

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

     The above URL links to a blog where the author talks about the CRC concepts, how it originated and also how it can help using this concept in Ruby. The author gives a link to the first paper written by Ward Cunningham where the CRC details are explained. 

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-30T01:02:34Z

Pmzachar: /* What is CRC and what are the cards? */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

A sample CRC card is as shown in the picture below:

<center>[[Image:CRC_card.jpg]]</center>

[Courtesy: http://www.agilemodeling.com/artifacts/crcModel.htm]

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each card that is used in the example. These explain this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Objects, classes, relationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

A screenshot of the tool that is used to develop the CRC card is shown below:

<center>[[Image:Tools.jpg]]</center>
Courtesy:http://www.excelsoftware.com/quickcrcintro.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt

     The above link talks about the design that can be used in Java where it makes a reference to CRC cards. How CRC cards helping reducing the design complexity. CRC is a concept and not a feature that is specific to any programming language. Hence in the presentation the author explains how this CRC concept can be used in Java to improve the design. 

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

     The above URL links to a blog where the author talks about the CRC concepts, how it originated and also how it can help using this concept in Ruby. The author gives a link to the first paper written by Ward Cunningham where the CRC details are explained. 

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-30T01:01:09Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

A sample CRC card is as shown in the picture below:

<center>[[Image:CRC_card.jpg]]</center>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each card that is used in the example. These explain this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Objects, classes, relationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

A screenshot of the tool that is used to develop the CRC card is shown below:

<center>[[Image:Tools.jpg]]</center>
Courtesy:http://www.excelsoftware.com/quickcrcintro.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt

     The above link talks about the design that can be used in Java where it makes a reference to CRC cards. How CRC cards helping reducing the design complexity. CRC is a concept and not a feature that is specific to any programming language. Hence in the presentation the author explains how this CRC concept can be used in Java to improve the design. 

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

     The above URL links to a blog where the author talks about the CRC concepts, how it originated and also how it can help using this concept in Ruby. The author gives a link to the first paper written by Ward Cunningham where the CRC details are explained. 

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-30T00:59:55Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

A sample CRC card is as shown in the picture below:

<center>[[Image:CRC_card.jpg]]</center>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each card that is used in the example. These explain this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Objects, classes, relationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

A screenshot of the tool that is used to develop the CRC card is shown below:

<center>[[Image:Tools.jpg]]</center>

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt

     The above link talks about the design that can be used in Java where it makes a reference to CRC cards. How CRC cards helping reducing the design complexity. CRC is a concept and not a feature that is specific to any programming language. Hence in the presentation the author explains how this CRC concept can be used in Java to improve the design. 

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

     The above URL links to a blog where the author talks about the CRC concepts, how it originated and also how it can help using this concept in Ruby. The author gives a link to the first paper written by Ward Cunningham where the CRC details are explained. 

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-30T00:52:05Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

A sample CRC card is as shown in the picture below:

<center>[[Image:CRC_card.jpg]]</center>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each card that is used in the example. These explain this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Objects, classes, relationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

A screenshot of the tool that is used to develop the CRC card is shown below:

[[Image:Tools.jpg]]

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt

     The above link talks about the design that can be used in Java where it makes a reference to CRC cards. How CRC cards helping reducing the design complexity. CRC is a concept and not a feature that is specific to any programming language. Hence in the presentation the author explains how this CRC concept can be used in Java to improve the design. 

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

     The above URL links to a blog where the author talks about the CRC concepts, how it originated and also how it can help using this concept in Ruby. The author gives a link to the first paper written by Ward Cunningham where the CRC details are explained. 

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

File:Tools.jpg

2007-10-30T00:48:26Z

Pmzachar:

File:Tool.jpg

2007-10-30T00:24:29Z

Pmzachar: A screenshot of the tool used to develop CRC cards.

A screenshot of the tool used to develop CRC cards.

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-30T00:23:43Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

A sample CRC card is as shown in the picture below:

[[Image:CRC_card.jpg]]

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each card that is used in the example. These explain this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Objects, classes, relationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

[[Image:Tools.jpg]]

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-30T00:18:44Z

Pmzachar: /* What is CRC and what are the cards? */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

A sample CRC card is as shown in the picture below:

[[Image:CRC_card.jpg]]

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each card that is used in the example. These explain this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Objects, classes, relationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

File:CRC card.jpg

2007-10-30T00:17:26Z

Pmzachar: A sample CRC card is as shown in the picture.

A sample CRC card is as shown in the picture.

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-30T00:16:12Z

Pmzachar: /* What is CRC and what are the cards? */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

[[Image:CRC_card.jpg]]

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each card that is used in the example. These explain this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Objects, classes, relationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt.

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-29T20:50:21Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each card that is used in the example. These explain this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Objects, classes, relationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt.

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-29T20:48:19Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed above. In these examples each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which helps better understanding of the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt.

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-29T20:45:43Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a good place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt.

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-29T20:45:09Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few sites that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt.

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-29T20:43:25Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few examples that explain how to design the CRC cards in a specific situation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt.

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-29T17:08:13Z

Pmzachar: /* Site which explain CRC concepts in Java and Ruby */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few examples that explain how to design the CRC cards in a specific situvation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt.

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-29T17:07:21Z

Pmzachar: /* Sites which show examples which explain CRC concepts well */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Review on few sites which explain CRC cards</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Sites which show examples which explain CRC concepts well==

Below are few examples that explain how to design the CRC cards in a specific situvation.

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams. 
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm 
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==Site which explain CRC concepts in Java and Ruby==

Below are few links which talk about CRC cards specific to programming languages link Java and Ruby. The concept of CRC cards is the same in these languages. The links show how they are implemented specific to a language. The concept of CRC cards is not bound to a specific language.

JAVA:

http://rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt.

http://books.google.com/booksid=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://www.softstar-inc.com/Download/Intro%20to%20CRC.pdf

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T02:31:10Z

Pmzachar:

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

JAVA:

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:49:42Z

Pmzachar: /* CRC concepts in Java and Ruby */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

JAVA:

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:49:09Z

Pmzachar: /* Examples which explain CRC concepts well: */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 

    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.
 

(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

JAVA:

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:48:29Z

Pmzachar: /* Examples which explain CRC concepts well: */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm
http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

 
(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

JAVA:

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:44:39Z

Pmzachar: /* CRC concepts in Java and Ruby */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

 
(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

JAVA:

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

    CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:44:26Z

Pmzachar: /* Examples which explain CRC concepts well: */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

    It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

 
(iii) Self-study 

    Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

JAVA:

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:41:20Z

Pmzachar: /* CRC concepts in Ruby */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

 
(iii) Self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

JAVA:

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:41:11Z

Pmzachar: /* CRC concepts in Java and Ruby */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

 
(iii) Self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

JAVA:

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

RUBY:

http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

CRC concepts are very helpful for projects which will be developed in programming language like Java and Ruby. These are object oriented languages, using CRC helps the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==CRC concepts in Ruby==

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:39:45Z

Pmzachar: /* CRC concepts in Ruby */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

 
(iii) Self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

CRC concepts are very helpful for projects which will be developed in programming language like Java. Java is an object oriented language, using CRC with Java helps the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==CRC concepts in Ruby==

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:39:36Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

 
(iii) Self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java and Ruby==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

CRC concepts are very helpful for projects which will be developed in programming language like Java. Java is an object oriented language, using CRC with Java helps the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:39:07Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

 
(iii) Self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

CRC concepts are very helpful for projects which will be developed in programming language like Java. Java is an object oriented language, using CRC with Java helps the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:38:34Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

 
(iii) Self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

CRC concepts are very helpful for projects which will be developed in programming language like Java. Java is an object oriented language, using CRC with Java help the developers identify the objects, classes their relationships. The above links explains the JAVA object oriented concepts and how CRC helps in understanding the relationship between the various classes and objects.

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:32:47Z

Pmzachar: /* Examples which explain CRC concepts well: */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.
 

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

 
(iii) Self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

 
(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:31:32Z

Pmzachar: /* Examples which explain CRC concepts well: */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective. Helps in understanding the concept well when relating the same using state diagrams.

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below. In this example each card is explained well with all the required details.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) Self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself. It has descripts for each cards that is used in the example. Explains this concept using a state diagram which help better understanding on the concept.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.These are available for various platforms like Windows, Mac OS and so on. These tools automates CRC cards, which helps the designers to quickly identify Object, classes, replationships and related information before the coding phase. All these make the implementation a lot easier.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:23:44Z

Pmzachar: /* Examples which explain CRC concepts well: */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) Interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) To a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) Self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:22:42Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

==Examples which explain CRC concepts well:==

(i) interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:20:22Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:19:34Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html 
http://www.extremeprogramming.org/example/crcsim.html 

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:18:25Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit 
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

http://c2.com/doc/crc/draw.html 
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html
http://www.extremeprogramming.org/example/crcsim.html

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:16:54Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

    http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

    http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

    http://c2.com/doc/crc/draw.html
    http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html
http://www.extremeprogramming.org/example/crcsim.html

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.

http://www.excelsoftware.com/quickcrcintro.html 
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:16:28Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

    http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

    http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

    http://c2.com/doc/crc/draw.html
    http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html
http://www.extremeprogramming.org/example/crcsim.html

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.

http://www.excelsoftware.com/quickcrcintro.html
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:15:41Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

    http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

    http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

    http://c2.com/doc/crc/draw.html
    http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html
http://www.extremeprogramming.org/example/crcsim.html

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.
CRC Cards generation tool
    
http://www.excelsoftware.com/quickcrcintro.html
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:14:39Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

    http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

    http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

    http://c2.com/doc/crc/draw.html
    http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html
http://www.extremeprogramming.org/example/crcsim.html

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.
CRC Cards generation tool
    http://www.excelsoftware.com/quickcrcintro.html
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

==CRC concepts in Ruby==
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:12:38Z

Pmzachar: /* References */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

    // describes in details talks abt role play and structure..

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

    http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

    http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

    http://c2.com/doc/crc/draw.html
    http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html
http://www.extremeprogramming.org/example/crcsim.html

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.
CRC Cards generation tool
    http://www.excelsoftware.com/quickcrcintro.html
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

One link i cud get on Ruby n CRC
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards
Its a blog but thats all i cud get:(

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

http://alistair.cockburn.us/index.php/Using_CRC_cards

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:02:04Z

Pmzachar: /* CRC concepts in Java */

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

    // describes in details talks abt role play and structure..

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

    http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

    http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

    http://c2.com/doc/crc/draw.html
    http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html
http://www.extremeprogramming.org/example/crcsim.html

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.
CRC Cards generation tool
    http://www.excelsoftware.com/quickcrcintro.html
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

One link i cud get on Ruby n CRC
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards
Its a blog but thats all i cud get:(

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card

CSC/ECE 517 Fall 2007/wiki2 5 pr

2007-10-25T01:00:00Z

Pmzachar:

==Introduction==

        Applying the object-oriented paradigm to the development of software requires individuals and teams to think and act differently than when designing procedural projects. While proponents of the object paradigm often say identifying objects is a simple and intuitive process, experienced developers know that this is not always true. The solution is the CRC (Classes, Responsibilities, Collaboration) Card method, a proven technique for identifying classes and visualizing and testing different class-based models during the design phase.

==What is CRC and what are the cards?==

        CRC stands for Class, Responsibilities, and Collaborators, and each of these are recorded on index cards which are then used to facilitate team-based roleplay.

        A CRC card is an index card that defines a Class, Responsibilities of classes and the interaction between the classes. They are used to determine which classes are needed and how they will interact. CRC cards are an informal approach to object oriented modeling. The cards are created through scenarios, based on the system requirements, that model the behavior of the system.

The contents of an index card are:

        <li> The class name </li>
<li> Its Super and Sub classes (if applicable) </li>
<li> The responsibilities of the class. </li>
<li> The names of other classes with which the class will collaborate to fulfill its responsibilities. </li>
<li> Author </li>

==Why bother about CRC cards?==

<li> They are portable. No computers are required so they can be used anywhere. Even away from the office. </li>
<li> Reduces the complexity of the design.</li>
<li> The allow the participants to experience first hand how the system will work. No computer tool can replace the
interaction that happens by physically picking up the cards and playing     the roll of that object. </li>
<li> Helps the designer focus on the essentials of the class rather than getting into inner details. </li>
<li> The are a useful tool for teaching people the object-oriented paradigm. </li>
<li> They can be used as a methodology them selves or as a front end to a more formal methodology. </li>

==Where to learn about this new and innovative method?==

    There are many websites and books that talk about this technique. Some in depth and some just enough to make life simpler for everyone. Listed below are some of the many websites that talk about this method along with the effectiveness with which each site explains this method.

<h2>Sites</h2>

http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/crc_b/

    This site gives a very good description about CRC cards. It starts with a very simple definition of CRC cards which does not right away deal with too many technicalities. It gives a succinct description of almost all the required details, starting from a brief history to the reason behind its existence. It also gives a brief description of the advantages of having CRC cards. The ''Tutorial'' section in this link gives a step by step approach on how to go about making CRC cards and also how to use them.

Inference:
<li> A very introductory description to CRC cards. </li>
<li> The right kind of site for beginners. </li>
<li> Its disadvantage is same as its advantage, i.e it is just a basic layman way of explaining CRC cards. </li>

https://olt.qut.edu.au/it/itb611/gen/index.cfm?fa=frameLink&rNum=864389

    In this site the author describes the CRC concept by comparing it to the processes, data flow and data store of the procedural designs regardless of the programming language and environment. This concept is explained by taking an example from the Smalltalk-80 image.

http://www.cs.utexas.edu/users/ndale/ObjectOriented.html 

    //Pdh paper...remember ;)

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/RBiddle.html 

    One portion of the CRC card method that hasnt been covered in most of the other sites has been covered here- Roleplay. It says 'As a design technique, roleplay really creates a focus on how the design makes objects collaborate to work through a use case.' Here they also discuss about the usual problems faced while introducing people to this concept and also gives a way around this problem.

    // describes in details talks abt role play and structure..

http://www.cs.umu.se/~jubo/Meetings/OOPSLA01/Contributions/MNordstrom.pdf 

    This paper talks about the Object Oriented concepts using CRC cards and BlueJ. It gives a detailed case study on the benifits of using CRC cards as a tools for teaching Object oriented languages. The result of the case study proves the advantages of this technique.

Which exercises can be used to teach them best:

(i) interactively over the Web 

    http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
    This is a god place for anyone to practise the use and/or implementation of CRC cards. It gives a detailed explanation with a number of state diagrams which makes the experience much more effective.

(ii) to a class of students, via in-class exercises 

    http://www.agilemodeling.com/artifacts/crcModel.htm

It gives a detailed step by step process on how to use CRC cards in Object Oriented programming. There are many more such sites that gives a pretty good explanation about this method. Some of them have been listed below.

    http://c2.com/doc/crc/draw.html
    http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html

(iii) self-study 

Most of the above sites can be used as a means of learning about CRC cards all by oneself.

http://www.math-cs.gordon.edu/local/courses/cs211/ATMExample/CRCCards.html#Deposit
http://www.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html
http://www.extremeprogramming.org/example/crcsim.html

(iv) Tools

    There are some tools that are extremely useful in making CRC cards.
CRC Cards generation tool
    http://www.excelsoftware.com/quickcrcintro.html
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows_Download.html

==CRC concepts in Java==

http://books.google.com/books?id=SGOyQai2TboC&pg=PA215&lpg=PA215&dq=crc+in+java&source=web&ots=uV4gPOMunE&sig=TJmVqbYwB-LSibfSkpZzPGt6VHM

http://209.85.165.104/search?q=cache:iXZrNJdMCK8J:rohan.sdsu.edu/~stewart/cs310-fall07/Ch03v2.0.ppt+Class+Responsibility+Collaboration+card+for+java&hl=en&ct=clnk&cd=1&gl=us

One link i cud get on Ruby n CRC
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards
Its a blog but thats all i cud get:(

==Conclusion==

    The overall conclusion is that CRC cards remains an effective technique for learning and practicing OO design. There are weaknesses, but strategies to compensate it too. Using these strategies, it is found that the CRC card technique is sound. We advocate use of the strategies to take advantage of the strengths of the CRC card technique, while addressing the weaknesses.

==References==

http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card