<?xml version="1.0" encoding="ISO-8859-1"?>
<CAT xmlns:cat="http://www.w3.org/TR/html4/" version="2.0"> 
<cat:title>Programming Style Focused Listing</cat:title>
<cat:author>Tammy VanDeGrift and Kate Deibel</cat:author>
<cat:date>March 30, 2004</cat:date>

<cat:technique>Focused Listing</cat:technique>

<cat:purpose>
<p>
This activity allows instructors to see what students associate with good programming style.
</p>
</cat:purpose>
<cat:activity>
<p>
At the top of the page, write the phrase "Good Style". In the time allowed, please write as many words or phrases that you associate with good style below the heading "Good Style". Remember, this "Good Style" is in reference to programming.
</p>
</cat:activity>
<cat:solution>
<p>
Given the free-form nature of this CAT, student answers will encompass a wide range of possibilities. Primarily, it is important for the instructor to prepare his or her own list based on the class's materials.
</p>
</cat:solution>
<cat:analysis>
<p>
Create your own list and put it aside.
</p>

<p>
Read through the student lists and record entries as either "Good", "Questionable," or "Wrong." Note that you do not have to record every list item.
</p>

<p>
Look over the "Good" entries and add them to you master list if appropriate. Also, select a few entries from the other piles that highlight common misconceptions that you wish to address.
</p>
</cat:analysis>
<cat:variant_uses>
	<cat:variation>Have students work in groups to complete this activity. The instructor may want to circulate throughout the groups to ensure that each group is making progress. After the groups have completed their lists, the instructor can make a composite list with all phrases from every group. As a group adds a new word or phrase, encourage the groups to explain why this concept contributes to good style.</cat:variation>
	<cat:variation>Have students work individually on their lists and then form groups of 4-5 people to discuss their individual lists with other members of the group.</cat:variation>
</cat:variant_uses>
<cat:classification>
<cat:assessment_goals>
	<cat:goal>Learn concepts and theories</cat:goal>
	<cat:goal>Improve skill at paying attention</cat:goal>
	<cat:goal>Improve listening skills</cat:goal>
	<cat:goal>Learn terms and ideas of programming style</cat:goal>
</cat:assessment_goals>
<cat:topics>
	<cat:topic>Programming Style</cat:topic>
</cat:topics>
<cat:participation_level>
</cat:participation_level>
<cat:time>
	<cat:preparation_time>LOW</cat:preparation_time>
	<cat:class_time>LOW</cat:class_time>
	<cat:in_class_analysis_time>LOW</cat:in_class_analysis_time>
	<cat:out_class_analysis_time>LOW</cat:out_class_analysis_time>
</cat:time>
<cat:instructor_response>
	<cat:response>Lecture</cat:response>
	<cat:response>Next Day Summary</cat:response>
</cat:instructor_response>
<cat:device_enabled>Straightforward to Enable</cat:device_enabled>
<cat:related_topics>
	<cat:topic>Commenting</cat:topic>
	<cat:topic>Naming conventions</cat:topic>
	<cat:topic>Readability</cat:topic>
	<cat:topic>Conciseness</cat:topic>
	<cat:topic>Design</cat:topic>
</cat:related_topics>
</cat:classification>
</CAT>