On September 27^th, Becky, Mike and Kelvin met in Kelvin’s office. The following are records from our discussion.

 

1. Student forms: We discussed and refine the Student assessment forms Becky designed.
2. Faculty forms: Becky will work on this.
3. Assessment procedure:
   1. Student:

                                                    i.     Pre test: will be assigned as part of the programming assignments. Students will be advice that they are supposed to _not_ know everything. Students will be graded on effort rather than correctness (credit/no-credit).

                                                   ii.     Post test: will be assigned as assignment after the programs are turned in. Students will be graded according to correctness. They should treat this as a regular homework assignment.

                                                  iii.     Polling: Becky and Kelvin will stop by the classroom during the last 10 minutes on the days the assignments are due.

1.      For 142: Oct 15, Oct 22, Nov 5, Nov 19

2.      For 143: Mike what are the due dates for 143?

                                                  iv.     Pre-class assessment on students’ general feeling:

1.      For 142: Oct 1^st at 7:35pm

2.      For 143: Oct 1^st at 8:00pm

                                                   v.     Post-class assessment on students’ general feeling:

1.      For 142: Nov 26^th at 7:35pm

2.      For 142: Nov 26^th at 8:00pm

2. Faculty:

                                                    i.     Becky will work on the form

                                                   ii.     Mike: will fill out the form for each of the 142/143 assignments.

4. Human subject: we suddenly realize we should get human subject approval going. This is may not be too late for Winter/Spring surveys. Becky will send Kelvin examples of what they have done. Kelvin will look into this.
5. Mike and Kelvin discussed about XNA assignments. The release status shows what is going on.
   1. 100/200: We are almost ready to re-release (Mike will clean up 200 starter project and tutorial).
   2. 300:

                                                    i.     Mike will re-examine and the starter project

                                                   ii.     Kelvin: must design a tutorial

3. 600:

                                                    i.     Mike: will design the starter project

                                                   ii.     Kelvin: must design a tutorial

4. 700: Kelvin MUST get his act together and design this!
5. Games class:
   1. We will approach this class with: teaching programming construct based on practical problem solving and using games to practice the programming constructs.
   2. We will start with building a simple game with a tool (e.g., game maker), students can play with their games, and then, the class will teach about programming constructs that relate to students’ games.
   3. Mike will design a sample schedule
   4. Kelvin will complete the new course proposal form and seek approval from CSS curriculum committee and faculty.
6. Next meeting time: Next Thursday at 11:30am. For the rest of this quarter, we will continue to meet at this time (cancel when necessary).