Difference between revisions of "Remote Hand"

From Open Pattern Repository for Online Learning Systems
Jump to navigation Jump to search
(Created patlet for pattern)
 
(Edited patlet)
Line 5: Line 5:
|image= <!-- Provide the filename of the image to be displayed (e.g., Design_pattern.png) -->
|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 -->
|contributor= <!-- List of contributors separated by a " , "comma. This is optional so you can remove this field if there are no contributors -->
|source= Köppe and Schalken-Pinkster (2013)<ref name="Köppe2013a">Köppe, C., & Schalken-Pinkster, J. (2013). [http://dl.acm.org/citation.cfm?id=2725697 Lecture design patterns: improving interactivity]. In Proceedings of the 20th Conference on Pattern Languages of Programs (p. 23). The Hillside Group.</ref>
|source= Köppe and Schalken-Pinkster (2013)<ref name="Köppe2013a">Köppe, C., & Schalken-Pinkster, J. (2013). [http://dl.acm.org/citation.cfm?id=2725697 Lecture design patterns: improving interactivity]. In Proceedings of the 20th Conference on Pattern Languages of Programs (p. 23). The Hillside Group.</ref><ref name="KÖPPE">Also mentioned in Köppe, C., Portier, M., Bakker, R., & Hoppenbrouwers, S. (2015). [http://hillside.net/plop/2015/papers/panthers/2.pdf Lecture Design Patterns: More Interactivity Improvement Patterns.] In Proceedings of the 22nd Conference on Pattern Languages of Programs (PLoP 2015). Pittsburgh, USA.</ref>
|dataanalysis= <!-- If applicable, list of data analyses used for mining the pattern separated by a " , "comma -->
|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) -->
|domain= <!-- Learning domain the design pattern belongs to (e.g., General, Math, Algebra) -->
Line 14: Line 14:
}}
}}


To demonstrate a tool during a lecture, let the students tell you what to do and then execute it so that everyone can see it instead of presenting the tool all by yourself. Combine the tool’s feedback with your own.  This avoids placing the students in a consuming role and saves time from having different students try out and use the tool so that everyone can understand it. <ref name="Köppe2013a"/>
When demonstrating a tool, let the students tell you what to do and then execute it so that everyone can see it. Combine the tool’s feedback with your own.<ref name="Köppe2013a"/><ref name="KÖPPE"/>


==Context==
==Context==

Revision as of 14:07, 27 September 2016


Remote Hand
Contributors
Last modification September 27, 2016
Source Köppe and Schalken-Pinkster (2013)[1][2]
Pattern formats OPR Alexandrian
Usability
Learning domain
Stakeholders

When demonstrating a tool, let the students tell you what to do and then execute it so that everyone can see it. Combine the tool’s feedback with your own.[1][2]

Context

Problem

Forces

Solution

Consequences

Benefits

Liabilities

Evidence

Literature

Discussion

Data

Applied evaluation

Related patterns

Example

References

  1. 1.0 1.1 Köppe, C., & Schalken-Pinkster, J. (2013). Lecture design patterns: improving interactivity. In Proceedings of the 20th Conference on Pattern Languages of Programs (p. 23). The Hillside Group.
  2. 2.0 2.1 Also mentioned in Köppe, C., Portier, M., Bakker, R., & Hoppenbrouwers, S. (2015). Lecture Design Patterns: More Interactivity Improvement Patterns. In Proceedings of the 22nd Conference on Pattern Languages of Programs (PLoP 2015). Pittsburgh, USA.