Difference between revisions of "Pattern Discovery"
Jump to navigation
Jump to search
***
***
Sfrancisco (talk | contribs) (Added contributors) |
Sfrancisco (talk | contribs) (Added category) |
||
| Line 33: | Line 33: | ||
We consider this pattern as true invariant, taking into account that it is only applicable for patterns which match with the experience of the students or pattern learners. It was for example used for introducing pedagogical patterns during a lecturer’s workshop and also during a presentation at the Dutch Conference on Computer Science Education in 2011<ref name="Koppe2011">Köppe, C. (2011). [http://www.koeppe.nl/publications/PedagogicalPatterns_NIOC2011_proceedings.pdf Een tijd-(en grenze) loze manier van onderwijs: Pedagogical Patterns]. In ''Proceedings of the NIOC 2011 conference''. Heerlen, Netherlands.</ref>. | We consider this pattern as true invariant, taking into account that it is only applicable for patterns which match with the experience of the students or pattern learners. It was for example used for introducing pedagogical patterns during a lecturer’s workshop and also during a presentation at the Dutch Conference on Computer Science Education in 2011<ref name="Koppe2011">Köppe, C. (2011). [http://www.koeppe.nl/publications/PedagogicalPatterns_NIOC2011_proceedings.pdf Een tijd-(en grenze) loze manier van onderwijs: Pedagogical Patterns]. In ''Proceedings of the NIOC 2011 conference''. Heerlen, Netherlands.</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]] [[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 08:31, 5 May 2017
| Pattern Discovery | |
| Contributors | Christian Köppe |
|---|---|
| Last modification | May 5, 2017 |
| Source | Köppe (2011)[1][2]; Köppe (2013)[3] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Also Known As: Discover Your Own Pattern
The students have enough knowledge of the subject addressed by some of the more simple patterns and they probably already applied the pattern solution without knowing that this was a pattern implementation. You now want to show the students where patterns come from.
Students see patterns as something that intelligent people have written. They don’t understand that these mostly are captured “best known practices" and that experienced people use them without thinking about them.
Therefore: Show students how patterns emerge by letting them discover an existing and well-known pattern by themselves.
We consider this pattern as true invariant, taking into account that it is only applicable for patterns which match with the experience of the students or pattern learners. It was for example used for introducing pedagogical patterns during a lecturer’s workshop and also during a presentation at the Dutch Conference on Computer Science Education in 2011[4].
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ Pattern first published in Köppe, C. (2011). A pattern language for teaching design patterns (part 1). In Proceedings of the 16th European Conference on Pattern Languages of Programs (p. 2). ACM:New York.
- ↑ Patlet published in Köppe, C. (2011). A pattern language for teaching design patterns (part 2). In Proceedings of the 18th Conference on Pattern Languages of Programs. ACM:New York.
- ↑ Pattern also published in Köppe, C. (2013). A Pattern Language for Teaching Design Patterns. In Transactions on Pattern Languages of Programming III (pp. 24-54). Springer Berlin Heidelberg.
- ↑ Köppe, C. (2011). Een tijd-(en grenze) loze manier van onderwijs: Pedagogical Patterns. In Proceedings of the NIOC 2011 conference. Heerlen, Netherlands.