| (11 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
There are many ways to use the kiwi as part of a course. Here are a few ideas: | There are many ways to use the kiwi as part of a course. Here are a few ideas: | ||
| − | * Student teams can work together to type lecture notes. They can then use these notes as a skeleton on which to add comments, questions, relevant links, etc. For example, in the spring of 2008, students in ECE662 typed all the [[ECE662:BoutinSpring08_OldKiwi#Class_Lecture_Notes| course notes]] online, and a few of students added animations (e.g., [[Lecture_11_-_Fischer%27s_Linear_Discriminant_again_OldKiwi#Fischer.27s_Linear_Discriminant_in_Projected_Coordinates|here]]) to better illustrate the material. | + | * Student teams can work together to type lecture notes. They can then use these notes as a skeleton on which to add comments, questions, relevant links, etc. For example, in the spring of 2008, students in ECE662 typed all the [[ECE662:BoutinSpring08_OldKiwi#Class_Lecture_Notes| course notes]] online, and a few of students added animations (e.g., [[Lecture_11_-_Fischer%27s_Linear_Discriminant_again_OldKiwi#Fischer.27s_Linear_Discriminant_in_Projected_Coordinates|here]]) to better illustrate the material. Students in ECE301 Fall 2007 took pictures of the board during the lecture and posted them [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/Lecture720070911 here] |
| − | * Students can write pages that summarize the material they learned "in their own words". Click [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/AliasingAnimatedExample here] for an example. | + | * Students can write pages that summarize the material they learned "in their own words". Click [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/AliasingAnimatedExample here] for an example. They can also discussion extensions of the material, as in [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/AMAndFMRadio here]. |
| − | * Individual students can write pages summarizing relevant background material. Click [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/EvenOddSignalsMakesEverythingClear here] for an example. While this helps them to brush up on the material, it also helps other students. Other students can then use the discussion page to point out mistakes or discuss the relevance of the material. | + | * Individual students can write pages summarizing relevant background material. Click [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/EvenOddSignalsMakesEverythingClear here] or [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/GuideToPartialFractionExpansion here] for an example. While this helps them to brush up on the material, it also helps other students. Other students can then use the discussion page to point out mistakes or discuss the relevance of the material. |
| − | * Individual students can write pages of practice exercises for certain computations/concepts along with their answers. The rest of the class can then use the discussion page to point out mistakes, ask questions, etc. | + | * Individual students can write pages of practice exercises for certain computations/concepts along with their answers. (See [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/ConvolutionExample here] for example.) The rest of the class can then use the discussion page to point out mistakes, ask questions, etc. |
* Student teams or individual students can type homework solutions on kiwi, along with questions/comments. For example, they may have two solutions with two different answers, and want to know which one is correct, or they may get to a different answer that what is given in the solutions and may want to know if their answer is correct. Ways to "go from my answer to the books answer" can be shared. Click [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/MakingAnswerFitSolutionKey here] for an example. | * Student teams or individual students can type homework solutions on kiwi, along with questions/comments. For example, they may have two solutions with two different answers, and want to know which one is correct, or they may get to a different answer that what is given in the solutions and may want to know if their answer is correct. Ways to "go from my answer to the books answer" can be shared. Click [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/MakingAnswerFitSolutionKey here] for an example. | ||
| Line 17: | Line 17: | ||
* Students can write pages that compare different solutions to a problem. | * Students can write pages that compare different solutions to a problem. | ||
| − | * Students can | + | * Students can list and discuss some "common mistakes" to a given type of problem. See for example [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/SamplingThmDef here]. |
* Students can propose numerical methods (e.g. Matlab code) to check their answers. You would be surprised what kind of tricks them can come up with, as [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/PartialFractionExpansionInMatlab this] for example. | * Students can propose numerical methods (e.g. Matlab code) to check their answers. You would be surprised what kind of tricks them can come up with, as [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/PartialFractionExpansionInMatlab this] for example. | ||
| Line 23: | Line 23: | ||
* Students can share code and datasets. | * Students can share code and datasets. | ||
| − | * Students can build a glossary of useful terms for the course. | + | * Students can build a glossary of useful terms for the course. Click [[Glossary_OldKiwi|here]] for an example. |
| − | * Students can build a table of useful formulas (e.g., [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/ComplexNumberFormulas here]) or share mathematical "tricks" (e.g., [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/2TricksToSimplifySummation here]). | + | * Students can build a table of useful formulas (e.g., [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/ComplexNumberFormulas here]) or share mathematical "tricks" (e.g., [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/2TricksToSimplifySummation here] or [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/GeometricSeries here]). |
* Students can work in groups to write solutions of the midterm after the midterm has been graded and handed back. | * Students can work in groups to write solutions of the midterm after the midterm has been graded and handed back. | ||
| − | * Before a midterm, students can post their solution to some old exam, and the instructor can grade these solutions for everybody's benefit. | + | * Before a midterm, students can post their solution to some old exam, and the instructor can grade these solutions for everybody's benefit. Click [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/Exam1 here] for an example. |
| − | * When handing back a midterm containing a question that was not successfully answered by the majority of the students, ask the students to post their solutions and discuss them, then ask that question again in a quiz or on the final exam. | + | * When handing back a midterm containing a question that was not successfully answered by the majority of the students, ask the students to post their solutions and discuss them, then ask that question again in a quiz or on the final exam. This was done with an exam question that asked the students to "state the sampling theorem in their own words". See the students answers [[ Students%27_statements_of_the_Sampling_Theorem_OldKiwi|here]] |
| − | * Invite your own students to become managers of the class kiwi, and let them come up with | + | * Invite your own students to become managers of the class kiwi, and let them come up with new features ideas, discuss them, and implement them. See for example this [https://engineering.purdue.edu/people/mireille.boutin.1/ECE301kiwi/Kiwi discussion]. |
* Invite your own students to suggest new ways to use the kiwi in your classroom. | * Invite your own students to suggest new ways to use the kiwi in your classroom. | ||
Latest revision as of 09:36, 25 August 2008
I am a Purdue Instructor. How can I use Kiwi in my class?
There are many ways to use the kiwi as part of a course. Here are a few ideas:
- Student teams can work together to type lecture notes. They can then use these notes as a skeleton on which to add comments, questions, relevant links, etc. For example, in the spring of 2008, students in ECE662 typed all the course notes online, and a few of students added animations (e.g., here) to better illustrate the material. Students in ECE301 Fall 2007 took pictures of the board during the lecture and posted them here
- Students can write pages that summarize the material they learned "in their own words". Click here for an example. They can also discussion extensions of the material, as in here.
- Individual students can write pages summarizing relevant background material. Click here or here for an example. While this helps them to brush up on the material, it also helps other students. Other students can then use the discussion page to point out mistakes or discuss the relevance of the material.
- Individual students can write pages of practice exercises for certain computations/concepts along with their answers. (See here for example.) The rest of the class can then use the discussion page to point out mistakes, ask questions, etc.
- Student teams or individual students can type homework solutions on kiwi, along with questions/comments. For example, they may have two solutions with two different answers, and want to know which one is correct, or they may get to a different answer that what is given in the solutions and may want to know if their answer is correct. Ways to "go from my answer to the books answer" can be shared. Click here for an example.
- Students can use the discussion pages to grade (and discuss) each others homework. A formal double-blind peer review system can also be set up. For example, the third homework assignment of ECE662 in Spring 08 consisted in a peer review of the second homework assignment. Click here to see the results.
- Students can write pages that compare different solutions to a problem.
- Students can list and discuss some "common mistakes" to a given type of problem. See for example here.
- Students can propose numerical methods (e.g. Matlab code) to check their answers. You would be surprised what kind of tricks them can come up with, as this for example.
- Students can share code and datasets.
- Students can build a glossary of useful terms for the course. Click here for an example.
- Students can build a table of useful formulas (e.g., here) or share mathematical "tricks" (e.g., here or here).
- Students can work in groups to write solutions of the midterm after the midterm has been graded and handed back.
- Before a midterm, students can post their solution to some old exam, and the instructor can grade these solutions for everybody's benefit. Click here for an example.
- When handing back a midterm containing a question that was not successfully answered by the majority of the students, ask the students to post their solutions and discuss them, then ask that question again in a quiz or on the final exam. This was done with an exam question that asked the students to "state the sampling theorem in their own words". See the students answers here
- Invite your own students to become managers of the class kiwi, and let them come up with new features ideas, discuss them, and implement them. See for example this discussion.
- Invite your own students to suggest new ways to use the kiwi in your classroom.
Should I reward the students?
Rewarding the students with either bonus points or homework points is a good way to stimulate contributions and make your class kiwi quickly gain momentum. But whether or not this is necessary is debatable.
