On June 27^th Mike and Kelvin met at Kelvin’s Office. The following are records from our discussion.

 

1. Feedback from Ruth: Ruth provided us with excellent feedback for MonteCarlo assignment from R1. Based on her assignment, we told her to skip BurstABubble for now, and that she should move on to R2’s ModAndCondition Here are some of the major issues Ruth brought up:
   1. XNA: machine, need know if a machine supports XNA
   2. VS help: for people not familiar with VS
   3. Controller: is a pain, (as Mike as pointed out earlier) Kelvin will develop keyboard input support.
   4. XNA: documentation for MC assignment was weak. We have figured out how to fix this. Let’s see if we can have better feedback for R2 and for this weeks’ assignments.
   5. Release folder structure: this is a problem we are fixing. Let’s see if we can get a better review with R2 and R3 (from this week).
   6. Assessment:

                                                               i.      Everywhere we say “Adaptation” we should use “Adoption” (Kelvin is a foreigner, this is the lame excuse we have).

                                                             ii.      Need to re-phrase some of the questions under “Potential for Adaptation” such that the reviewer can comment more on the assignment, rather then general questions that applies to all assignment in general.

                                                            iii.      Ruth pointed out a very good point that language and textbook are often decided by committee, so we should re-phrase some of questions.

 

2. For this Friday, for R3, we hope to release: BurstABubble and LinkedList
   1. General: MakeRelease tool

                                                               i.      Kelvin: Need to re-examine after ReadMe naming convention fixes

                                                             ii.      Both Mike and Kelvin: should remove all the .zip files from Assignment folders. The MakeRelease tool will automatically create these.

                                                            iii.      Kelvin: Try to integrate keyboard input to XnaAssignmentBase.

                                                            iv.      Kelvin: Assessment form update (based on Ruth’s input)

2. BurstABubble to do list:

                                                               i.      Mike: Readme file: naming convention

                                                             ii.      Mike: Console Rubric needs percentage

3. LinkedList:

                                                               i.      Kelvin: XNA Solution:

1.       speed of balls should be kept

2.       must make sure balls will not bounce only horizontally (initial-X velocity must be set properly)

                                                             ii.      XNA Student starter project:

1.       Pass1 (Mike): go through the code comment and indicate what students should do.

2.       Pass2 (Kelvin): go thought the code and make sure solution still valid and clean up the code.

                                                            iii.      Mike: XNA student assignment description

                                                            iv.      Mike: XNA grading rubric

                                                              v.      Mike: move the console solution to the right place

 

4. Mike: finish the above to do list and forward the work to Kelvin by tomorrow night.
5. Kelvin: complete the release by Friday afternoon.

 

3. For next Thursday 7/5 (meeting time 11am):
   1. Monte Carlo should be done: to do list:

                                                               i.      Kelvin: XNA Solution:

1.       use array for initial computation (just like console solution)

2.       after array-functions, let user change circle radius

3.       keep dots on screen to show approximation process (make dots small), see if we can let student use this function also.

                                                             ii.      XNA Student starter project :

1.       Pass1 (Mike): go through the code comment and indicate what students should do.

2.       Pass2 (Kelvin): go thought the code and make sure solution still valid and clean up the code.

                                                            iii.      Mike: XNA student assignment description

                                                            iv.      Mike: XNA grading rubric

2. Othello (if time):

                                                               i.      XNA Student starter project :

1.       Pass1 (Mike): go through the code comment and indicate what students should do.

2.       Pass2 (Kelvin): go thought the code and make sure solution still valid and clean up the code.

                                                             ii.      Mike: XNA student assignment description

                                                            iii.      Mike: XNA grading rubric

                                                            iv.      Mike: Console solution + Start project

 

4. Others:
   1. PriodicTable: Mike will check in a sample solution