CSC/ECE 517 Fall 2007/wiki2 5 pr: Difference between revisions
Line 110: | Line 110: | ||
==Conclusion== | ==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:== | ==References:== | ||
http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card | http://en.wikipedia.org/wiki/Class-Responsibility-Collaboration_card |
Revision as of 19:25, 24 October 2007
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:
Why bother about CRC cards?
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.
Sites
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:
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.cs.gordon.edu/courses/cs320/ATM_Example/CRCcards.html
http://www.agilemodeling.com/artifacts/crcModel.htm
http://c2.com/doc/crc/draw.html
(iii) for self-study?
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.excelsoftware.com/quickcrcintro.html
http://www.extremeprogramming.org/example/crcsim.html
CRC Cards generation tool
http://www.fileboost.net/directory/development/miscellaneous/quickcrc_windows/007241/review.html
http://www.freedownloadscenter.com/Programming/Misc__Programming_Tools/QuickCRC_Windows.html
http://www.excelsoftware.com/crccards.html
Yet to add the CRC concepts wrt Java and Ruby!!
And ii and iii
One link i cud get on Ruby n CRC
http://weblog.rubyonrails.org/2006/6/14/remember-crc-cards
Its a blog but tahts 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