Difference between revisions of "Use A Styleguide"
Jump to navigation
Jump to search
***
Sfrancisco (talk | contribs) (Added category) |
Sfrancisco (talk | contribs) (Added category) |
||
| Line 69: | Line 69: | ||
<references/> | <references/> | ||
[[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]] --> | [[Category:Design_patterns]] [[Category:Patlet]] [[Category:Learning Patterns for Group Assignments]] [[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 08:03, 17 May 2017
| Use A Styleguide | |
| Contributors | Christian Köppe |
|---|---|
| Last modification | May 17, 2017 |
| Source | Köppe (2012)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
The team will get a lower grade if the deliverables are inconsistent in terms of style, as the teacher expects deliverables from one team and not from individuals.
Therefore: Define a styleguide or decide on an existing one and use this consequently throughout the whole assignment.
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ Köppe, C. (2012). Learning patterns for group assignments: part 1. In Proceedings of the 19th Conference on Pattern Languages of Programs (PLoP 2012). The Hillside Group.