Curriculum Map¶

Artifact — instantiates Knowledge Map Navigation

A program-level chart that lays out the units of a course of study, the outcomes each serves, and the prerequisite order that binds them into a coherent whole.

A Curriculum Map is the institution-level chart of an entire program of study: it lays out the units or courses, groups them into strands, records which learning outcome each unit serves, and fixes the prerequisite order that holds the whole thing together. Its defining trait is that it maps a shared program against declared outcomes — it exists to answer the questions only a whole-program view can: is every outcome we promise actually taught somewhere? taught more than once redundantly? in a sensible order? by which unit? Where a personal learning route serves one learner's goal, a Curriculum Map serves a cohort and an institution — it's the artifact a department uses to see, govern, and defend the coherence of a degree, not to guide a single student through it.

Example¶

A university computer-science department suspects its degree has grown incoherent — some graduates can't do things the program promises. The faculty builds a Curriculum Map: a grid of every course against the program's declared learning outcomes (e.g., "can design a concurrent system", "can reason about algorithmic complexity"), with each cell marking whether a course introduces, develops, or masters that outcome, plus the prerequisite arrows between courses. Laid out this way, two problems become visible instantly. One promised outcome — secure software design — is marked "introduce" in three courses and "master" in none: taught repeatedly but never brought home. And a capstone lists a prerequisite that itself isn't offered until the following semester. Following the principle of aligning what's taught, assessed, and intended,^[1] the department reslots two courses and adds a mastery-level unit. The map governed the program's coherence — something no single student's path could reveal.

How it works¶

Enumerate units and group into strands. List the courses and cluster them into coherent tracks (systems, theory, applications) so the program's structure is visible.
Map units to outcomes. For each declared program outcome, mark which units introduce, develop, and master it — exposing outcomes that are over-taught, under-taught, or never brought to mastery.
Fix the prerequisite order. Record the dependency arrows between units so the sequence is checkable for impossible orderings and missing precursors.
Read for coherence gaps. Orphaned outcomes, mastery-less promises, and broken prerequisite chains are read directly off the map.

What distinguishes it from its siblings is the outcome-against-program view: it's governance of a whole curriculum's coherence, not a route for an individual and not the bare dependency graph.

Tuning parameters¶

Outcome granularity — coarse outcomes are easy to map but hide whether specifics are covered; fine-grained outcomes catch gaps but make the grid huge and the mapping laborious.
Coverage-level scheme — a simple "taught / not taught" mark is fast; an introduce/develop/master gradient reveals depth problems but demands judgment on every cell.
Strand structure — organizing by subject strand, by year, or by outcome each surfaces different coherence problems; the axis you choose is the lens you get.
Enforcement weight — advisory (a planning aid faculty may ignore) versus binding (accreditation-grade, changes require review); heavier enforcement guarantees coherence but slows change.

When it helps, and when it misleads¶

Its strength is program-level coherence: it makes visible whether a whole course of study actually delivers what it promises, in a defensible order — indispensable for curriculum design, accreditation, and diagnosing why graduates have predictable blind spots.

Its failure mode is confusing coverage on the map with learning in students. A cell marked "mastered" asserts a course is meant to bring an outcome home, not that any student did — the map can look immaculate over a program that isn't working, because it charts intended structure, not achieved competence. It also tends to ossify: an accreditation-grade map is expensive to change, so it lags the field. The classic misuse is building it to pass an audit — reverse-mapping existing courses onto outcomes to make the grid look complete rather than to test whether the program is. The discipline is to pair the map with actual outcome evidence (assessment results, graduate capability) and to treat clean coverage as a claim to verify, not a result.

How it implements the components¶

A Curriculum Map fills the archetype's program-and-outcome slots:

navigation_goal — the declared learning outcomes the whole program is charted against.
prerequisite_link — the dependency order between units, checked for coherence at program scale.
cluster_boundary — the strands or tracks that group units into a coherent structure.

It does not personalize a route to one learner's state (user_state_marker, navigation_path for an individual — that's Learning Path Guide), render the pure topic-level dependency graph (prerequisite_link at topic granularity with entry_point — that's Prerequisite Tree in its raw form), or test whether learners can actually navigate it (navigation_validation_loop — that's Map Navigation User Test).

Instantiates: Knowledge Map Navigation — the Curriculum Map is the program-level chart of a course of study against its outcomes.
Consumes: Prerequisite Tree supplies the underlying dependency relations the program order must respect.
Sibling mechanisms: Learning Path Guide · Prerequisite Tree · Domain Map · Concept Map · Ontology Map · Knowledge Graph · Research Landscape Map · Documentation Navigation Map · Knowledge Gap Register · Map Navigation User Test

Notes¶

The Curriculum Map governs a program for a cohort; the Learning Path Guide routes one learner through material. A curriculum sets the institutional structure and outcomes; a learning path is a personalized traversal that respects them but starts from an individual's state and goal.

References¶

[1] "Constructive alignment" — John Biggs's principle that intended learning outcomes, teaching activities, and assessment should all line up so that what is taught and tested is what is meant to be learned; a Curriculum Map is a standard instrument for checking that alignment across a program. ↩