Difference between revisions of "Learning Contract"
Jump to navigation
Jump to search
Sfrancisco (talk | contribs) (Added contributors) |
Sfrancisco (talk | contribs) (Added category) |
||
| Line 65: | Line 65: | ||
<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 14:52, 4 May 2017
| Learning Contract | |
| Contributors | Kathleen A. Larson, Frances P. Trees, D. Scott Weaver |
|---|---|
| Last modification | May 4, 2017 |
| Source | Larson et al. (2008)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Carefully go over the syllabus with the students so they are completely aware of the requirements. Let them be aware that it is your contract with them[1].
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ 1.0 1.1 Larson, K. A., Trees, F. P., & Weaver, D. S. (2008). Continuous feedback pedagogical patterns. In Proceedings of the 15th Conference on Pattern Languages of Programs, PLoP 2008 (p. 12). New York:ACM.