From charlesreid1

Line 58: Line 58:
* Remaining sections filled in with whatevers (small examples from book)
* Remaining sections filled in with whatevers (small examples from book)


==Quizzes==
==Homework==


Notes on procedure:
Notes on procedure:
* Review questions at end of chapter, and review questions at end of chapter in other Java books
* Review questions at end of chapter, and review questions at end of chapter in other Java books
* Formulate a list of potential questions that are similar in spirit to the building Java programs textbook
* Based on questions, build a rubric of what kinds of questions test what kind of skills
* Build a rubric of what we want to focus on with our questions
* Write some of your own questions
** Quizzes: easier questions, more syntax, what we want to nail down and how to ensure they're doing the requisite work
* Divide the questions based on the kinds of skills they teach (simpler, more complex)
** Exams: harder questions, more thinking, more tricky, give them sample exams.
* 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

Revision as of 05:07, 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

PDF

  • 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)

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