Difference between revisions of "Problem Solving Machine"
Jump to navigation
Jump to search
Sfrancisco (talk | contribs) (Added contributors) |
Sfrancisco (talk | contribs) (Added category) |
||
| Line 65: | Line 65: | ||
<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:11, 5 May 2017
| Problem Solving Machine | |
| Contributors | Joseph Bergin, Jutta Eckstein, Markus Völter, Mariana Sipos, Eugene Wallingford, Klaus Marquardt, Jane Chandler, Helen Sharp, Mary Lynn Manns |
|---|---|
| Last modification | May 5, 2017 |
| Source | Bergin et al. (2012)[1] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Stress software development as a means of solving problems. From the outset introduce problems that are familiar and well understood by the students but which have sufficient complexity to demonstrate the added value of the software solution. Provide prebuilt components, as a problem-solving toolkit, which can, at a later stage, be ‘unwrapped' to reveal the detailed syntax of their implementation[1].