(undergraduate studies only)
The tool to build plan requirements is the same as course requisites – Rules. The list of predetermined rules (and associated wording) will be different. But the idea behind the logic is the same.
For plan requirements, users first need to understand the different rule fields and when to use them and understand rule categories.
Rule fields
On the Programs and Plans form, there exists several fields that can house undergraduate plan requirement lists, each with a different purpose.
| Field name | Conditions for field to display | Totals units automatically | Rules available | Default Rule Category | Subcategories available | When to use |
|---|---|---|---|---|---|---|
| Course Requirements (units) |
Career = Undergraduate Credential Type = any Program Type = any Degree = all except BASc, BArch, BSE |
Yes | Rules limited; only to be used if requirements are simple and list active University of Waterloo courses. | Required Courses | Yes | When plan should display an automatic calculation of units required based on courses/rules used |
| Course Requirements (no units) |
Career = Undergraduate Credential Type = any Program Type = any Degree = all except BASc, BArch, BSE |
No | Rule choice available | Required Courses | Yes | When plan should not display an automatic calculation of units required based on courses/rules used |
| Required Courses (Term by Term) |
Career = Undergraduate Credential Type = Major Program Type = Honours Degree = BASc, BArch, BSE |
No | Rule choice available | 1A Term | No | Engineering-owned major plans only |
| Course Lists | All plans | No | Rule choice available | Required Courses | Yes | When need to display "lists" of courses, often in combination with the "Course Requirements (units)" or "Course Requirements (Term by Term)" fields |
Rule categories overview
Each plan requirement field is set up to use pre-determined rule categories – essentially a series of headers. Each field will have a default category (see table above).
The list of rule categories can be accessed via the arrow pair next to the default header, e.g., "Required Courses".
Use the action items on the right to control the rule categories:
- Gear icon: Controls some default rule categories settings. When more than one category exists, the option to delete a category section becomes available.
- + icon: Add another rule category.
Note: Each rule category (or subcategory) can only be used once within each field. When more than one rule category (or subcategory) exists, the rule category name already used is removed from the choice. - Arrow icon: Collapses or expands the rule category section.
- … button: Appears when more than one category exists and allows user to change the order of category sections by moving one up or down.
Rule subcategories overview
In some fields, rule categories can also have subcategories. If this option is available (see table above), the + Add Rule Subcategory button will be visible.
Tip: If using subcategories, a rule must be used in the top rule category, otherwise "Rule Not Selected" will display in the Calendar. The rule does not need to be one of the predetermined ones, Free Form Text can be used.
Guidelines: Rule categories
Not all rule categories can be used in all scenarios. For instance, the list is shared between the undergraduate and graduate academic calendar, and the Office of the Registrar has created guidelines to provide consistency across the undergraduate calendar.
| Rule Category | Career use | Constraints |
|---|---|---|
| Required Courses | Both | Default (most fields) |
| 1A Term - 4B Term | Undergraduate | Only plans with term promotion rules: all Faculty of Engineering majors |
| Year One - Year Four | Undergraduate | Only plans with term promotion rules: Optometry and Pharmacy [to be used in combination with a rule subcategory] |
| Elective Courses | Undergraduate | One possibility to balance "Required Courses" |
| Additional Requirements | Both | To list non-course related requirements |
| Approved Courses List | Undergraduate | One possibility to balance "Required Courses" |
| Breadth Courses List | Undergraduate | For plans that have a "breadth" requirement |
| Ethics List | Undergraduate | For plans that have an "ethics" requirement |
| Natural Science List | Undergraduate | For plans have a specific type of electives list that fits a "natural science" categorization |
| Technical Electives List | Undergraduate | For plans that have a specific type of electives list that fits a "technical" categorization |
| Complementary Studies Elective List | Undergraduate | For Bachelor of Applied Science degree-level requirements, for accreditation purposes |
| Undergraduate Communication Requirement | Undergraduate | For degree-level or plan-level requirements to outline the Undergraduate Communication Requirement |
Order
Only one of each rule category can be used per field. When using more than one rule category per field, the order to display should match the order they appear in within the system and in the above table.
Guidelines: Rule subcategories
Not all rule subcategories can be used in all scenarios. For instance, the list is shared between the undergraduate and graduate academic calendar, and the Office of the Registrar created guidelines to provide consistency across the undergraduate calendar.
| Rule Subcategory | Career use | Constraints |
|---|---|---|
| Fall/Winter/Spring | Undergraduate |
Default = Fall Only plans with term promotion rules: Optometry and Pharmacy [to be used in combination with a rule category] |
| List 1 - 4 | Undergraduate | To be used when lists need to be split, and only when contractually required (e.g., complicated requirements or need to refer to the list to make requirements clear) |
| Thesis Option | Graduate | Do not use in undergraduate calendar |
| Coursework Option | Graduate | Do not use in undergraduate calendar |
| Research Option | Graduate | Do not use in undergraduate calendar |
| List A - D | Undergraduate | Degree-level requirements (e.g., Engineering's CSEs or Math's list of shared courses); preference is List 1 - 4 |
Order
Only one of each rule subcategory can be used per rule category within a given field. When using more than one rule subcategory per field, the order to display should match the order they appear in within the system and in the above table.
Example 1 – Engineering Technical Electives:
Example 2 – Optometry requirements:
Guidelines: Building rules
- All cross-listed courses must be listed (per guiding principles), unless the desire is not to have the other course automatically counted towards the requirement or the average calculation (Senate must be aware of this intent).
- For cross-listed courses, they can be listed in one of two ways:
- If the requirement is to complete one of the set, the "# of courses" rule must be used.
- If the course is listed in a list of choice, each offering must be listed in the proper alpha-numeric order.
- For cross-listed courses, they can be listed in one of two ways:
- Use a pre-determined available rule before using the "Free form text" rule.
- Within a rule, all courses must be listed in alpha-numerical order by subject code and course number.
- List rules in the following order:
- List of rules where all course(s) must be taken from the list.
- List of rules where # of course(s) must be taken from the list.
- Only undergraduate courses can be listed via linked course rules; if a graduate course needs to be listed, you must use the "Free form text" rule.
- For listing Laurier courses, you must use the "Free form text" rule.
Free form text rule
- Don't use punctuation at the end of a requirement.
- When listing graduate-level or Laurier courses, display them as SubjectCode (no space between), for example "BUS111W".
- Some standard phrasing that must be used when needing to use the "Free form text" rule:
- For courses in a particular subject:
- Complete # additional SubjectCode courses
- Complete # additional SubjectCode courses at the #00-level
- Complete # additional SubjectCode courses at the #00-level or above
- Complete # additional courses at the #00-level from: list of subject codes (alpha order, separated by commas)
- For Laurier courses:
- Complete all the following: list of courses (alpha-numeric order, separated by commas)
- Complete # of the following: list of courses (alpha-numeric order, separated by commas)
- For courses in a particular subject:
Example plan requirement scenarios
Scenario 1: Adding and removing courses from an existing program or plan
- Locate the program or plan that needs requirements updated in the Kuali CM Programs & Plans database, and open it.
- Select Propose Changes, and complete required fields in the form pertaining to the change(s).
- Navigate to the Requirements Information section of the form.
- Locate the rule(s) to be updated.
- For any courses that need to be removed from a list, select the trash can icon to the right of the course.
- To add a course to the list, start typing the Subject Code in the "Courses" box, and select the correct course from the list that populates, by clicking on it (or using the arrows and enter keys). In this example, KIN121 is being added to a list of required courses.
- The selected course will automatically be added to the end of the list. Important: Do not try to reorder the list for alpha-numeric order. The Office of the Registrar will ensure alpha-numeric order is achieved in their step in the workflow.
- Once changes are complete, select Save and Exit. Submit your proposal once all changes are complete.
Scenario 2: Updating rules in an existing program or plan
It will sometimes be necessary when making changes to requirements, to need to make changes to the existing rules. Changing a rule will category will clear any records that were already in the field. It is recommended to create the new rule first, before making a change (or removing) the rule that needs updating.
Goal: Change rule A from a "Complete 2 of the following" rule to a "Complete all the following" rule.
- Navigate to the record, select propose changes, and locate the rule(s) to be updated in the form. In this example, we are changing rule A.
- If we try to change rule A to a "complete all" list, the 3 course records that exist in it will be automatically removed, as pictured.
- Instead of changing the rule, we will first add a new rule after Rule A, select the appropriate new rule, and add in the courses.
- Now we can delete rule A, by clicking the ellipsis icon next to rule A, and selecting Delete.
- Once completed, we select Save and Exit.
Building a new program or plan
When building a new program or plan in Kuali CM, new course requirement lists will also need to be created.
- Navigate to the Programs & Plans database, and select + New Program & Plan.
- A blank Program & Plan form will open. Complete the fields as required for your specific program or plan.
- In the Requirements Information section of the form, the Course Requirements rule options will appear once the Career and Undergraduate Credential Type fields on the form have been selected.
- Determine if your Course Requirements should be built with units automatically tallied, or no units, and work within your selected option.
- Select the appropriate rule type by clicking on the arrow pair next to Required Courses.
- Select + Add Rules to input course requirements.
- Select + Add Rule Subcategory to input a subcategory of course requirements (if needed, and allowed for your program/plan).
Scenario 3: Engineering Technical Electives
In this scenario, the rule type is changed from Required Courses (the default) to Technical Electives List. To add a list, a subcategory is added by selecting + Add Rule Subcategory. Additional lists are added using the + next to the term. The arrow pair next to the title is selected to change the subcategory title to "List #". Rules can be added within each category and subcategory.
Scenario 4: Optometry requirements
In this scenario, the rule type is changed from Required Courses (the default) to Year One. To add the term, a subcategory is added by selecting + Add Rule Subcategory. Additional terms are added using the + next to the term. Rules can be added within each category and subcategory.
