Difference between revisions of "Model Courses"
Jump to navigation
Jump to search
m |
|||
Line 33: | Line 33: | ||
sethomework0.def |
sethomework0.def |
||
sethomework1.def |
sethomework1.def |
||
+ | etc. |
||
+ | Set_Headers/ |
||
+ | setheader0.pg |
||
+ | setheader1.pg |
||
etc. |
etc. |
||
Problem_Files/ |
Problem_Files/ |
Revision as of 12:35, 16 June 2011
Prep Main Page > Web Conference 3 > Model Courses
What is a Model Course?
One of our goals is to create Model Courses. By this, we mean a set of WeBWorK problem sets with problems that will match the course syllabus for one or more textbooks.
Contents
What should be in a Model Course:
- Information about the text(s) to which it is matched
- Information about the syllabus that it assumes
- The set definition files (or sets of set definition files) that provide the problem sets for the course
- Any problems that are developed to fill in gaps in the NPL
Issues
- Naming conventions: how should we name sets and problems so that they are consistent (within the course) and useful?
- Completeness: how much should the model courses be a complete set of problem sets and problems for a course?
- Can/should we have model units that combine to make a model course?
- How would these model units fit into the organizational structure?
- How can we include documentation that discusses how these materials are used?
- Can this be addressed with naming convention?
- Should it be addressed by organizational structure within the model?
Organization
How should all of these data be organized? A possible model:
CourseName/ Textbook_Readme Syllabus_Readme Set_Definitions/ sethomework0.def sethomework1.def etc. Set_Headers/ setheader0.pg setheader1.pg etc. Problem_Files/ prob01.pg prob02.pg etc. Hardcopies/ homework0.pdf homework1.pdf etc.