Difference between revisions of "Seven Parts"
Jump to navigation
Jump to search
Sfrancisco (talk | contribs) (Created patlet for pattern) |
Sfrancisco (talk | contribs) (Added link to reference) |
||
| 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= Anthony (1996)<ref name="Anthony1996">Anthony, D. L. (1996). Patterns for classroom education. In Pattern languages of program design 2 (pp. 391-406). Addison-Wesley Longman Publishing Co., Inc..</ref> | |source= Anthony (1996)<ref name="Anthony1996">Anthony, D. L. (1996). [http://ianchaiwriting.50megs.com/classroom-ed.html Patterns for classroom education.] In Pattern languages of program design 2 (pp. 391-406). Addison-Wesley Longman Publishing Co., Inc..</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) --> | ||
Revision as of 05:21, 22 September 2016
| Seven Parts | |
| Contributors | |
|---|---|
| Last modification | September 22, 2016 |
| Source | Anthony (1996)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Seven seems to be a good number for steps or sub-topics covered in a module. This highly depends on the length of the lecture, and other interactivity possibilities. Not very strong[1].
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ 1.0 1.1 Anthony, D. L. (1996). Patterns for classroom education. In Pattern languages of program design 2 (pp. 391-406). Addison-Wesley Longman Publishing Co., Inc..