Difference between revisions of "Simplicity Above Patterns"
Jump to navigation
Jump to search
***
***
Sfrancisco (talk | contribs) (Added source) |
Sfrancisco (talk | contribs) m (Edited format) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
{{Infobox_designpattern | {{Infobox_designpattern | ||
|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= | |contributor= [[Christian Köppe]] | ||
|source= Köppe (2011)<ref>Pattern first published in Köppe, C. (2011). [http://dl.acm.org/citation.cfm?id=2396718 A pattern language for teaching design patterns (part 1)]. In ''Proceedings of the 16th European Conference on Pattern Languages of Programs'' (p. 2). | |source= Köppe (2011)<ref>Pattern first published in Köppe, C. (2011). [http://dl.acm.org/citation.cfm?id=2396718 A pattern language for teaching design patterns (part 1)]. In ''Proceedings of the 16th European Conference on Pattern Languages of Programs (EuroPLoP 2011)'' (p. 2). New York:ACM.</ref><ref>Patlet published in Köppe, C. (2011). [http://koeppe.nl/publications/PatternsForPatternTeaching_ACM_Plop11.pdf A pattern language for teaching design patterns (part 2)]. In ''Proceedings of the 18th Conference on Pattern Languages of Programs (PLoP 2011)''. New York:ACM.</ref>; Köppe (2013)<ref name="Koppe2013">Pattern also published in Köppe, C. (2013). [http://link.springer.com/chapter/10.1007/978-3-642-38676-3_2 A Pattern Language for Teaching Design Patterns.] In ''Transactions on Pattern Languages of Programming III'' (pp. 24-54). Springer Berlin Heidelberg.</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 34: | Line 34: | ||
This pattern is considered as true invariant for the teaching of patterns of all domains, as the tendency of applying patterns excessively after being introduced to them can be found in nearly all domains. | This pattern is considered as true invariant for the teaching of patterns of all domains, as the tendency of applying patterns excessively after being introduced to them can be found in nearly all domains. | ||
==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]] [[Category:Pattern Language for Teaching Design Patterns]] [[Category:Traditional Classroom]]<!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] --> | ||
Latest revision as of 13:17, 16 May 2017
| Simplicity Above Patterns | |
| Contributors | Christian Köppe |
|---|---|
| Last modification | May 16, 2017 |
| Source | Köppe (2011)[1][2]; Köppe (2013)[3] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Also Known As: Keep It Simple
You want to make sure that the students do not add unnecessary complexity through blindly applying design patterns.
While learning design patterns students want to show that they understand design patterns by implementing as many patterns as possible. Most often this adds unnecessary complexity without adding value.
Therefore: Motivate the students to always give a rationale for all design patterns they have used. Make sure that they only apply a design pattern when they have not only examined the design problem at hand, but also the consequences of applying the pattern. The application of the pattern should add value to the overall design.
This pattern is considered as true invariant for the teaching of patterns of all domains, as the tendency of applying patterns excessively after being introduced to them can be found in nearly all domains.
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 (EuroPLoP 2011) (p. 2). New York:ACM.
- ↑ 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 (PLoP 2011). New York:ACM.
- ↑ 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.