Problem Solving Machine

	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 16, 2017
Source	Bergin et al. (2012)
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].

Context

Problem

Forces

Solution

Consequences

Benefits

Liabilities

Evidence

Literature

Discussion

Data

Applied evaluation

Related patterns

Example

References

↑ ^1.0 ^1.1 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.

[Bergin2012-1] 1.0 ^1.1 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.

[1]