Difference between revisions of "Abstraction Gravity-From High to Low"
Jump to navigation
Jump to search
Sfrancisco (talk | contribs) (Created patlet) |
Sfrancisco (talk | contribs) (Edited patlet to pattern template) |
||
| Line 1: | Line 1: | ||
<!-- Design pattern template | |||
Fill in all succeeding fields that are either surrounded by a comment tag (<!-- - ->) or angle brackets (< >) when applicable --> | |||
{{Infobox_designpattern | |||
|image= <!-- Provide the filename of the image to be displayed (e.g., Design_pattern.png) --> | |||
|contributor= <!-- List of contributors separated by a " , "comma. This is optional so you can remove this field if there are no contributors --> | |||
|dataanalysis= <!-- If applicable, list of data analyses used for mining the pattern separated by a " , "comma --> | |||
|domain= <!-- Learning domain the design pattern belongs to (e.g., General, Math, Algebra) --> | |||
|stakeholders= <!-- List of stakeholders separated by a " , "comma --> | |||
|evaluation = <!-- List of evaluations on the pattern separated by a " , "comma --> | |||
|application = <!-- List of environments where the pattern was applied separated by a " , "comma --> | |||
|appliedevaluation = <!-- List of environments where the pattern was applied and evaluated separated by a " , "comma --> | |||
}} | |||
Concepts that need to be understood at two levels of abstraction may be time consuming. Introduce a concept at its highest level of abstraction then use reflection on the concept to link it to a lower-level abstraction. | Concepts that need to be understood at two levels of abstraction may be time consuming. Introduce a concept at its highest level of abstraction then use reflection on the concept to link it to a lower-level abstraction. | ||
Originally presented in Bergin et al. (2012)<ref>Bergin, J., Eckstein, J., Völter, M., Sipos, M., Wallingford, E., Marquardt, K., Chandler, J., Sharp, H., and Manns, M.L. (2012). Pedagogical patterns: advice for educators. Joseph Bergin Software Tools.</ref>. | Originally presented in Bergin et al. (2012)<ref>Bergin, J., Eckstein, J., Völter, M., Sipos, M., Wallingford, E., Marquardt, K., Chandler, J., Sharp, H., and Manns, M.L. (2012). Pedagogical patterns: advice for educators. Joseph Bergin Software Tools.</ref>. | ||
==Context== | |||
<!-- Context of the design pattern --> | |||
==Problem== | |||
<!-- Problem the design pattern solves --> | |||
==Forces== | |||
<!-- List of forces affecting the solution. Each entry is preceded by an * For example: | |||
# Entry 1 | |||
# Entry 2 --> | |||
==Solution== | |||
<!-- Solution to the design problem --> | |||
==Consequences== | |||
===Benefits=== | |||
<!-- List of benefits from applying the solution to the problem Each entry is preceded by an * For example: | |||
# Entry 1 | |||
# Entry 2 --> | |||
===Liabilities=== | |||
<!-- List of liabilities from applying the solution to the problem Each entry is preceded by an * For example: | |||
# Entry 1 | |||
# Entry 2 --> | |||
==Evidence== | |||
===Literature=== | |||
<!-- Evidence from literature that was used in producing the pattern or evaluating the pattern--> | |||
===Discussion=== | |||
<!-- Discussion with experts or stakeholders used in producing the pattern --> | |||
===Data=== | |||
<!-- Evidence from data that was used in producing the pattern --> | |||
===Applied evaluation=== | |||
<!-- Results from randomized controlled trials (RCTs) or similar tests that measures the pattern's effectiveness in an actual application. For example, compare student learning gains in an online learning system with and without applying the pattern. --> | |||
==Related patterns== | |||
<!-- Other design patterns related to the current design pattern and a description of how it is related --> | |||
==Example== | |||
<!-- Example of applying the design pattern --> | |||
==References== | ==References== | ||
<references/> | <references/> | ||
[[Category:Design_patterns]] <!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] --> | |||
[[Category:Design_patterns]] | |||
Revision as of 07:25, 9 June 2016
| Abstraction Gravity-From High to Low | |
| Contributors | |
|---|---|
| Last modification | June 9, 2016 |
| Source | {{{source}}} |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Concepts that need to be understood at two levels of abstraction may be time consuming. Introduce a concept at its highest level of abstraction then use reflection on the concept to link it to a lower-level abstraction.
Originally presented in Bergin et al. (2012)[1].
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ Bergin, J., Eckstein, J., Völter, M., Sipos, M., Wallingford, E., Marquardt, K., Chandler, J., Sharp, H., and Manns, M.L. (2012). Pedagogical patterns: advice for educators. Joseph Bergin Software Tools.