COBA prerequisite rules by
Robin Snyder
,
robin@RobinSnyder.com
, source: STICS/rules-01
[NV/asp]
[page formatted/updated on 2008/02/15 at 10:18:00
, loaded on 2010/09/08 at 08:41:45
]
versions:
screen-friendly
printer-friendly
Here are the current prerequisite rules that are used to generate class prereq violation reports, help in advising students, etc. Only courses that have prereqs and that explicitly appear on the COBA checksheets are listed. If you see any rule that is missing or is not
correct, please let me know.
An explanation key and list of future improvements appear at the bottom of this page.
"none" is the user friendly term for "true" which means that the prereq requirement is always satisfied. That is, there are no prereqs for the course.
"and" is the logical conjunction "and". Both operands are required to be true. Parentheses enclose the operands of logical conjunctions. Example: "(a and b)".
"or" is the logical disjunction "or". Either or both operands are required true. Square brackets enclose the operands of logical disjunctions. Example: "[a or b]".
"hoursx" means that x or more credit hours are required.
"withx" means that a letter grade of x or better is required.
"sincex" means that the rule part applies since the term x. The current abbreviations are "A" for Spring, "B" for Summer, "C" for Fall, and "D" for Winter (if needed).
"permission" means that permission is needed. Currently, all such conditions are assumed to be true.
Make the rule formatting more clear. Unfortunately, this is not always easy to do automatically.
Provide more meaningful formatting. Again, this is not always easy to do.
Add meaningful course names and course descriptions. Unfortunately, I do not want to type these in, so I need to get them in a form that can be automatically processed.