Side-by-Side Comparison

A comprehensive comparison of Curriculum-Based and Competency-Based instruction across all dimensions to help you make the right choice for your learning context.

Overview

πŸ“š

Curriculum-Based

Central Question:
"What content has the learner covered?"

Content-Centric Time-Based
🎯

Competency-Based

Central Question:
"What can the learner do?"

Skill-Focused Mastery-Based

Full Comparison

Dimension πŸ“š Curriculum-Based 🎯 Competency-Based
Central Question "What content has the learner covered?" "What can the learner do?"
Focus Content coverage Skill mastery
Time Fixed (semesters, units, terms) Variable (until mastery achieved)
Mastery Variable (grades A-F, percentages) Fixed (must demonstrate proficiency)
Progression By schedule (everyone moves together) By demonstration (advance when ready)
Learning Path Linear, predetermined sequence Flexible, mastery-driven
Pacing Group-based, synchronized Individual, self-paced
Assessment Type Knowledge recall, tests on covered material Performance demonstrations, real-world application
Progress Measure Content completion, time spent Demonstrated proficiency
Success Criteria Coverage of material, passing grades Mastery of defined competencies
Personalization Limited (same content for all) High (progress at own pace)
Framework Type Curriculum DSC (Domain-Specific Competency)
Framework ID Pattern dsc-curr-{name} dsc-comp-{name}
Structure Domain β†’ Subdomain β†’ Concept Category β†’ DSC β†’ Proficiency Levels
Levels/Depth Comprehension scale (1-10) Acquire (1/3) β†’ Deepen (2/3) β†’ Create (3/3)

Terminology Mapping

The same concepts have different names in each philosophy:

Generic Term πŸ“š Curriculum-Based 🎯 Competency-Based
Framework Curriculum DSC
Learning Unit (singular) Module Competency
Learning Units (plural) Modules Competencies
Progress Tracking Module Progress Competency Progress
Completion Status Modules Completed Competencies Mastered
Top-Level Category Domain Competency Category
Mid-Level Category Subdomain Domain-Specific Competency
Specific Item Concept Proficiency Level
Dynamic Terminology in UALS The UI automatically displays the correct terminology based on the class's philosophy. See Philosophy-Sensitive Design for implementation details.

Data Formats

πŸ“š Curriculum-Based Request

{
  "system": "KE",
  "config": {
    "domain": "Mathematics",
    "subdomain": "Calculus",
    "concept": "Derivatives",
    "comprehension": 5,
    "style": "visual"
  }
}

🎯 Competency-Based Request

{
  "module": "KE",
  "competency_category": "AI Literacy",
  "domain_specific_competency": "AI Capabilities",
  "proficiency_level": "2/3",
  "meta_category": "STEM"
}

Philosophy Detection

UALS automatically detects which philosophy to use based on request parameters:

  • Curriculum: Presence of domain, subdomain, concept
  • Competency: Presence of competency_category, domain_specific_competency, proficiency_level

Learning Systems Comparison

Both philosophies have access to the same learning systems, with content adapted accordingly:

System πŸ“š Curriculum Mode 🎯 Competency Mode
πŸ—ΊοΈ Knowledge Explorer Concept maps with topic relationships Skill maps with competency connections
πŸ’¬ Socratic Playground Guided practice on specific topics Skill-building through scenarios
πŸ“ SBCAT Assessment Tests on covered material Per-competency proficiency tracking
Universal Template Principle The UI templates are identical across both philosophies. Only the content and prompts differ. Learners get a consistent, familiar experience regardless of the instructional approach.