Difference between revisions of "Problem Solving Machine"
Jump to navigation
Jump to search
Sfrancisco (talk | contribs) (Created patlet for pattern) |
Sfrancisco (talk | contribs) (Added contributors) |
||
| 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= [[Joseph Bergin]], [[Jutta Eckstein]], [[Markus Völter]], [[Mariana Sipos]], [[Eugene Wallingford]], [[Klaus Marquardt]], [[ Jane Chandler]], [[Helen Sharp]], [[Mary Lynn Manns]] | ||
|source= Bergin et al. (2012)<ref name="Bergin2012">Bergin, J., Eckstein, J., Völter, M., Sipos, M., Wallingford, E., Marquardt, K., Chandler, J., Sharp, H., and Manns, M.L. (2012). Pedagogical patterns: advice for educators. Joseph Bergin Software Tools.</ref> | |source= Bergin et al. (2012)<ref name="Bergin2012">Bergin, J., Eckstein, J., Völter, M., Sipos, M., Wallingford, E., Marquardt, K., Chandler, J., Sharp, H., and Manns, M.L. (2012). Pedagogical patterns: advice for educators. Joseph Bergin Software Tools.</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 --> | ||
Revision as of 13:20, 6 April 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 | April 6, 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].