This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
instructional_design:structural_learning [2011/03/15 16:59] jpetrovic [What is structural learning theory?] |
instructional_design:structural_learning [2011/03/15 16:59] jpetrovic [What is structural learning theory?] |
||
---|---|---|---|
Line 17: | Line 17: | ||
* **procedure** - the sequence of **operations** to perform **on the inputs**. | * **procedure** - the sequence of **operations** to perform **on the inputs**. | ||
- | In accordance with structural learning theory, first step in instructional design or learning is **definition of the problem domain through structural analysis**. Problem domain can be both well- and ill-defined((An ill-defined domain is one in which rules are quite simple, yet there is no direct complete solution like chess, or poetry writing)). In case of an ill-defined domain, it should be divided into well-defined sub-domains which can generate at least one rule. Domain sets the inputs and desired outputs for problem solving. | + | In accordance with structural learning theory, first step in instructional design or learning is **definition of the problem domain through structural analysis**. Problem domain can be both well- and ill-defined((An ill-defined domain is one in which rules are quite simple, yet there is no direct complete solution like chess, or poetry writing.)). In case of an ill-defined domain, it should be divided into well-defined sub-domains which can generate at least one rule. Domain sets the inputs and desired outputs for problem solving. |
Domain definition is followed by **construction of hierarchy of rules** for well-defined domains. Rules should be explained on prototype problems, but can also leave some **gaps** in problem solving procedure, which **are then converted into higher-order problems** containing gap rules. Higher-order rules are then used to fill the gap, but can also validate lower level rules. | Domain definition is followed by **construction of hierarchy of rules** for well-defined domains. Rules should be explained on prototype problems, but can also leave some **gaps** in problem solving procedure, which **are then converted into higher-order problems** containing gap rules. Higher-order rules are then used to fill the gap, but can also validate lower level rules. |