Competencies

Revision as of 06:58, 25 May 2009 by Jonathan Newman (talk | contribs) (New page: ==Introduction== The outcomes and scales architecture introduced in Moodle 1.9 provide a solid foundation for competency management, particularly of course outcomes. To model the range of ...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Introduction

The outcomes and scales architecture introduced in Moodle 1.9 provide a solid foundation for competency management, particularly of course outcomes. To model the range of different types of competency frameworks used by organisations, Moodle 2.0's competency architecture needs to allow:

  • Competencies to be independent of courses and activities. Some examples:
    • Completing three specific course fulfills one competency
    • Providing electronic example (e.g., a scanned computer science diploma fulfills A-D competencies)
  • Competencies to be organised into frameworks on a site level in unlimited ways, allowing:
    • Taxonomies (i.e., categories)
    • Folksonomies (i.e., tags)
    • Hybrids of both
  • Multiple competency frameworks in the same Moodle instance
  • Competencies to rely on outcome types
  • Competencies to be gained by various methods (or types of evidence):
    • Achieving one or more outcomes in one or more courses
    • Completing one or more courses (i.e., when completing course A, course B, and course C)
    • Completing one or more activities (i.e., when completing activity x in course A and activity y in course B, and activity z in course C)
    • Exceeding the aggregate result threshold for a question category within an evaluation (i.e., feedback using quiz)
    • Exceeding the aggregate result threshold for a question category within an assessment (i.e., quiz)
    • Electronic file (a diploma, external certification)
      • User file area (via the file API)
      • External repository (via the portfolio API)
      • ePortfolio (via the repository API)
    • Comment / testimony / reference
  • Competencies to be attached to standard/custom user profile fields (e.g., 'level' - "First year student", or 'major' - "English")
  • Competencies to be tied an individual user (either by user profile field or by drag and drop)
  • Expected "evidence" and "competency proficiency levels" to be defined for links between standard/custom user profile field items and a competencies for each evidence type:
    • Outcome level (i.e., scale value)
    • A course's standard course completion criteria
    • A course's standard course activity criteria
    • Custom course completion criteria
    • Custom activity completion criteria
    • Aggregate result threshold for a question category
    • Required electronic file
  • Competencies to allow one or more types of evidence
  • Custom metadata to be easily attached to competencies and standard/custom user profile fields items