Difference between revisions of "Centralize Work Product Management"
Jump to navigation
Jump to search
***
Sfrancisco (talk | contribs) (Added contributors) |
Sfrancisco (talk | contribs) (Added category) |
||
Line 70: | Line 70: | ||
<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 09:18, 4 May 2017
Centralize Work Product Management | |
Contributors | Christian Köppe |
---|---|
Last modification | May 4, 2017 |
Source | Köppe (2012)[1][2] |
Pattern formats | OPR Alexandrian |
Usability | |
Learning domain | |
Stakeholders |
If the work products are not available in the current versions to all concerned students, inconsistencies and incompleteness can occur as students might work on different versions which later have to be merged.
Therefore: Make all work products available via one centralized place and keep the work products up-to-date.[1][2]
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ 1.0 1.1 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.
- ↑ 2.0 2.1 Also mentioned in de Cortie, T., van Broeckhuijsen, R., Bosma, G., & Köppe, C. (2013). Learning patterns for group assignments: part 2. In Proceedings of the 20th Conference on Pattern Languages of Programs (PLoP 2013). The Hillside Group.