Training

Example materials

nProgram listing

nChecklists for common problems

–Style manuals

–Pattern guides

nDesign documents

–CRC cards

–UML diagrams

nReport forms


	Of course you need to bring the code.

	Some organizations have checklists of items that should be covered. There are many style manuals that contain lists and pattern guides that demonstrate recommended ways of doing things. There is, for example, a book called “Smalltalk Best Practice Patterns.”

	Sometimes it might not be clear that the code does what it is supposed to do, so design documents might come in handy.

	Often a report must be filled out that indicates the outcome of the review. The outcome might be
	that the code was accepted without change,
	that something must be clarified before progress can be made,
	that the code is accepted as soon as small corrections are made, or
	that the code must be rewritten.