Why Data Source Matters in Degree Planning: CMS vs SIS
Overview
Degree planning software relies on institutional data to represent program structures, rules, and student progress.
This data typically comes from two core systems:
- Curriculum Management Systems (CMS)
- Student Information Systems (SIS)
How these sources are used affects how planning, validation, and progression are supported.
Student Information Systems (SIS)
Student Information Systems are designed to manage:
- enrolment records
- grades and academic history
- administrative program data
SIS platforms provide the authoritative record of student activity and are widely used for:
- degree auditing
- compliance checking
- enrolment management
Because SIS data is structured for administrative processes, program information is often simplified to support transactional workflows.
This makes SIS well suited to validation and tracking, but less suited to generating complex, forward-looking study plans.
Curriculum Management Systems (CMS)
Curriculum Management Systems are designed to model:
- program structures (degrees, majors, minors)
- complex rules and requisites
- versioned curriculum and approval workflows
CMS platforms act as the source of truth for curriculum design and governance.
This includes hierarchical structures, conditional rules, and relationships between subjects that are not always fully represented in SIS data.
This makes CMS well suited to representing curriculum logic and supporting dynamic, forward-looking planning.
Key differences
Aspect | SIS | CMS |
Primary purpose | Student records and transactions | Curriculum design and governance |
Data focus | Enrolments, grades, simplified program data | Full program structures and rules |
Level of detail | Operational | Rule-based and structured |
Role in planning | Validation and tracking (audit) | Representation of curriculum logic |
How this affects degree planning
The underlying data model influences how study plans are created and maintained.
Systems built primarily on SIS data typically:
- validate subject selections against recorded data
- support auditing and compliance workflows
- rely on predefined pathways or manual planning
Systems built on structured curriculum data (CMS) can:
- represent complex program rules directly
- generate study plans from curriculum logic
- support adaptive, forward-looking planning as conditions change
Relationship between CMS and SIS
In most university environments:
- CMS defines what the curriculum is
- SIS records what the student has done
Effective degree planning depends on aligning these two layers so that planning reflects both curriculum design and student progress.
StudyPlanner approach
StudyPlanner uses structured curriculum data for planning and sequencing, while incorporating student data for validation and tracking.
This enables study plans that reflect both curriculum design and student progress.
Why this distinction matters
The distinction between CMS and SIS reflects the difference between:
- systems focused on record-keeping and validation
- systems that support forward-looking planning
Understanding this helps explain differences in how degree planning systems operate.
Summary
Degree planning depends on both curriculum data and student data.
SIS supports validation and tracking, while CMS enables structured representation of curriculum and forward-looking planning.
Resources
Copyright © 2025 Study Planner Enrolment Solutions Pty Ltd. All rights reserved.