CSC 142 Checklist: Difference between revisions
From charlesreid1
| Line 57: | Line 57: | ||
* References to Github on slide finished | * References to Github on slide finished | ||
* Remaining sections filled in with whatevers (small examples from book) | * Remaining sections filled in with whatevers (small examples from book) | ||
Week 0 Lecture | |||
* <s>Skeleton</s> | |||
* To do: expand and add sections corresponding to sections in syllabus | |||
** More fun, less dour. | |||
** More computer science. | |||
Week 1 Lecture | |||
* Sekeleton | |||
* Github code stub | |||
* Github code | |||
* Slides with Github code references | |||
* Slides filled in | |||
==Homework== | ==Homework== | ||
Revision as of 06:35, 5 September 2016
What do I want in my binder at the start of the quarter?
- Syllabus
- Expectation-setting, what to do for assignments
- Calendar (topics, homeworks, quizzes, exams)
- Content outline (detailed)
- Lecture notes - slides and code (in Github repo)
- Quizzes
&* exams
- Homework problems and worksheets (take-home problems)
So, let's come up with checklists.
CSC 142 Fall 2016 Checklist
Syllabus
Steps to completion:
- Fill in basic class information (sched/dates/times)
- Fill in book information
- Academic integrity
- Devices
- Course content (chapter by chapter breakdown)
- Course grade
- Homework
- Quizzes
- Exams
- Prereqs
Syllabus lecture:
- Syllabus lecture slides skeleton
- Syllabus lecture slides fill in
- Create pdf for syllabus lecture notes
Calendar
Content Outline
Chapter by chapter outline
Section by section outline
Lecture notes
Notes on format:
- Keynote slides - 1 slide deck per chapter - pdf format - provided to students
- Partial examples/syntax - in Keynote
- Complete examples - develop in Github repo
- Slides contain various break-points for code examples, worksheets
Checklist: Chapter N slide deck:
- Skeleton: Section-by-section with key topics in each section
- Skeleton: Reference to each lecture/worksheet example on Github
- Skeleton: Stub of code on Github
- Github code finished
- References to Github on slide finished
- Remaining sections filled in with whatevers (small examples from book)
Week 0 Lecture
Skeleton- To do: expand and add sections corresponding to sections in syllabus
- More fun, less dour.
- More computer science.
Week 1 Lecture
- Sekeleton
- Github code stub
- Github code
- Slides with Github code references
- Slides filled in
Homework
Notes on procedure:
- Review questions at end of chapter, and review questions at end of chapter in other Java books
- Based on questions, build a rubric of what kinds of questions test what kind of skills
- Write some of your own questions
- Divide the questions based on the kinds of skills they teach (simpler, more complex)
- Create two question pools: quiz question pool, exam question pool
Question types
- Homeworks are rote written questions taking the same form always
- Exams and quizzes can be matching, more interesting
Quizzes
Procedure:
- Review problems in quiz question pool
- Quizzes have easier problems, more syntax, less abstraction, more mechanical, less wordy
- Create quizzes
Exams
Procedure:
- Review problems in exam question pool
- Exams have more abstract, more complex, more involved problems, less rote, more critical thinking
- Create exams