Program design and implementation (CAS HEiE) - week 2: Difference between revisions
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
* Competence map (hands-on Moodle) | * Competence map (hands-on Moodle) | ||
Example of a simple competence map structure: | Example of a simple competence map structure: | ||
* Competencies are usually defined in terms of levels (at least three, otherwise you only will have "pass"/"fail") | |||
* Competence levels are defined for each "topic" (dimension) that is part of the program. These can be well defined subject areas or transversal skills. | |||
* Each topic is further divided into sub-topics (sub-dimensions) | |||
In the following summary table, dimensions (also called "areas", "topics", "subject matters" are on one axis,, levels on another. | |||
{| class="wikitable" | |||
|+ | |||
! rowspan="2" |Level of competency | |||
! colspan="3" |Dimension 1 | |||
! colspan="2" |Dimension 2 | |||
! colspan="2" |Dimension 3 | |||
! colspan="2" |Dimension ... | |||
|- | |||
! | |||
! | |||
! | |||
! | |||
! | |||
! | |||
! | |||
! | |||
! | |||
|- | |||
|Level 1 | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
|- | |||
|Level 2 | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
|- | |||
|Level 3 | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
| | |||
|} | |||
== Program organisation == | == Program organisation == |
Revision as of 20:32, 23 October 2022
DKS:Program design and implementation (CAS HEiE)
Week 2 - Elements of educational program design
- Interactive Class: Monday October 24: 17h00 - 19h15
- Interactive Class: Wednesday October 26: 17h00 - 19h15
- Public tutoring session: Friday October 28: 17h-19h
Needs analysis, competence framework and learning goal definition
- Presentation and discussion of a competency framework: https://joint-research-centre.ec.europa.eu/digcompedu/digcompedu-framework/digcompedu-proficiency-levels_en
- Competence map (hands-on Moodle)
Example of a simple competence map structure:
- Competencies are usually defined in terms of levels (at least three, otherwise you only will have "pass"/"fail")
- Competence levels are defined for each "topic" (dimension) that is part of the program. These can be well defined subject areas or transversal skills.
- Each topic is further divided into sub-topics (sub-dimensions)
In the following summary table, dimensions (also called "areas", "topics", "subject matters" are on one axis,, levels on another.
Level of competency | Dimension 1 | Dimension 2 | Dimension 3 | Dimension ... | |||||
---|---|---|---|---|---|---|---|---|---|
Level 1 | |||||||||
Level 2 | |||||||||
Level 3 |
Program organisation
- Program structure (linked to the competence map)
- Program coordination and tutoring structure
Learner support and followup
- Global learner support (coaching, mentoring, advising, follow-up)
- Community building (-> Do profiles in Moodle, whatsapp, etc.)
Evaluation
Evaluation is a design factor or at least influences design
- Program and course evaluation (see also last module): Zaharias, P. (2004).
- Evaluation criteria, e.g. https://unesdoc.unesco.org/ark:/48223/pf0000382843
- Learning evaluation philosophy, policy and method
Certification
- accredited vs. micro-acreditations https://openbadges.org/
Assignments
Week 2 mini project
- Define a simple competency framework
- Map competencies to a program, i.e., a list of some courses
- Define learner support framework
- Suggest certification / collaboration with other institutions if appropriate.
Week 12 exchange
- Comment on the competency framework of two or more other participants. Make sure that everyone gets at least one feedback.
- Engage in discussion