Difference between revisions of "Buffers"
Jump to navigation
Jump to search
Sfrancisco (talk | contribs) (Added contributors) |
Sfrancisco (talk | contribs) (Added category) |
||
| Line 66: | Line 66: | ||
<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]] [[Category:Patlet]]<!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] --> | ||
Revision as of 10:09, 4 May 2017
| Buffers | |
| Contributors | Astrid Fricke, Markus Völter |
|---|---|
| Last modification | May 4, 2017 |
| Source | Fricke and Völter (2000)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Include buffers in your planning for a lecture so that you have time for reacting on unforeseen problems, questions, and topics[1].
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
An alternative to directly answering questions would be to use a Question Parking Space[2]
Example
References
- ↑ 1.0 1.1 Fricke, A., & Völter, M. (2000). SEMINARS: A Pedagogical Pattern Language about teaching seminars effectively. In Proceedings of the 5th European Conference on Pattern Languages of Programs, EuroPLoP 2000 (pp. 87-128). New York:ACM.
- ↑ 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.