The program is the largest-scale level of planning in CourseFlow, and it can be used to design and implement a curriculum of courses, create an ‘alignment’ between the outcomes of individual courses and those of the program, and then display this information in multiple different views.
It allows users to create a visual representation of the courses and learning outcomes or competencies of a curriculum. Learning outcomes are a critical part of the program level, allowing you to track and visualize the progression of student learning throughout the program.
The Program level workspace illustrates the following components:
- Terms: courses are organized into terms. Since all courses are typically taken at once in a term, there is no vertical ordering as at the course or activity level
- Categories: courses can be categorized for ease of reading. These customizable course categories are used to group similar courses.
- Linked workflows: A critical part of curriculum development requires course nodes to be linked to course-level workflows.
Note: To understand the relationship between the program Level and the activity and course levels, refer to Project Level Overview.
Role of Nodes, Sections, and Columns
At the program level, nodes represent individual courses. The sections are terms, which unlike other levels allow the nodes to be placed side by side to represent courses taken at the same time. The columns represent categories, and are used to organize the courses into similar groupings. Arrows can be drawn between nodes to represent prerequisites or corequisites.
A node at the program level can be linked to a course-level Workflow. See linking workflows to learn how to create the link. This allows you to plan the entire course within the context of the program, or to simply create a framework with outcomes to plan the relationships between course-level outcomes and program-level outcomes.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article