You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Skills have an attribute level, which is currently ignored by the algorithm.
Target Situation
The level should implicitly refer to a taxonomy, which the user has into his mind, e.g., Bloom taxonomy. With this in mind, the user may create multiple skills with the same name, but with different levels. Higher levels include automatically all lower levels of the same name (w.r.t. the Repository that defines the Skills).
Purpose
User may define the "same" Skills (same name) multiple times, on different Levels and may assign them to separate LearningUnits. For instance:
LOOPS (APPLY): The user can use for, while, do while, for each
LOOPS (EVALUATE): The user may choose which kind of loops fits best for a given situation
Not all levels must be assigned. In this case, there are no Skills such as LOOPS (REMEMBER), LOOPS (UNDERSTAND), ... but they may be created if necessary.
Modifications to the Algorithm
The algorithm must check if a Skillat least on the specified level is fulfilled. If the Skill was already learned on a higher level then specified, the user does not need to learn also the lower level again.
The text was updated successfully, but these errors were encountered:
We need a property in the Skill to hold the ID that matches the skill levels for the same skill. It can be the name of the skill (In case we guarantee the name matching during the creation of the skills), or it can be a unique ID.
We use that ID to retrieve all levels for the same skill. For example, we use ID= 2 from the Skill A (Level 1) to get all skill levels with ID= 2.
A skill level can learned by a combination of different skill levels as children. For example, Skill A (Level 3) can learned by learning Skill B (level 1), Skill C (level 3), Skill D (level 3), and Skill D (level 2).
We should consider the level of the skills in the goals during the path planner algorithm to find a learning path.
A discussion point,
What if the requested skill level (goal skill level) does not exist?
What if a learning path is missing a skill with specific level?
Propose a higher level of the same skill since it includes the lower skill. Keep in mind, that the higher level of a skill gives more depth about the subject.
No path found for the requested skill level since other levels give more or less depth about the subject.
Actual Situation
Skills
have an attributelevel
, which is currently ignored by the algorithm.Target Situation
The level should implicitly refer to a taxonomy, which the user has into his mind, e.g., Bloom taxonomy. With this in mind, the user may create multiple skills with the same name, but with different levels. Higher levels include automatically all lower levels of the same name (w.r.t. the
Repository
that defines theSkills
).Purpose
User may define the "same" Skills (same name) multiple times, on different Levels and may assign them to separate
LearningUnits
. For instance:for
,while
,do while
,for each
Skills
such as LOOPS (REMEMBER), LOOPS (UNDERSTAND), ... but they may be created if necessary.Modifications to the Algorithm
The algorithm must check if a
Skill
at least on the specified level is fulfilled. If theSkill
was already learned on a higher level then specified, the user does not need to learn also the lower level again.The text was updated successfully, but these errors were encountered: