<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://w.arbores.tech/w/index.php?action=history&amp;feed=atom&amp;title=Problem_solving</id>
	<title>Problem solving - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://w.arbores.tech/w/index.php?action=history&amp;feed=atom&amp;title=Problem_solving"/>
	<link rel="alternate" type="text/html" href="http://w.arbores.tech/w/index.php?title=Problem_solving&amp;action=history"/>
	<updated>2026-04-04T05:27:30Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.11</generator>
	<entry>
		<id>http://w.arbores.tech/w/index.php?title=Problem_solving&amp;diff=17358&amp;oldid=prev</id>
		<title>Daniel K. Schneider: 1 revision imported</title>
		<link rel="alternate" type="text/html" href="http://w.arbores.tech/w/index.php?title=Problem_solving&amp;diff=17358&amp;oldid=prev"/>
		<updated>2021-04-10T02:03:55Z</updated>

		<summary type="html">&lt;p&gt;1 revision imported&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 04:03, 10 April 2021&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-notice&quot; lang=&quot;en&quot;&gt;&lt;div class=&quot;mw-diff-empty&quot;&gt;(No difference)&lt;/div&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</summary>
		<author><name>Daniel K. Schneider</name></author>
	</entry>
	<entry>
		<id>http://w.arbores.tech/w/index.php?title=Problem_solving&amp;diff=16763&amp;oldid=prev</id>
		<title>Daniel K. Schneider: 1 revision imported</title>
		<link rel="alternate" type="text/html" href="http://w.arbores.tech/w/index.php?title=Problem_solving&amp;diff=16763&amp;oldid=prev"/>
		<updated>2021-04-10T01:37:21Z</updated>

		<summary type="html">&lt;p&gt;1 revision imported&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 03:37, 10 April 2021&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-notice&quot; lang=&quot;en&quot;&gt;&lt;div class=&quot;mw-diff-empty&quot;&gt;(No difference)&lt;/div&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</summary>
		<author><name>Daniel K. Schneider</name></author>
	</entry>
	<entry>
		<id>http://w.arbores.tech/w/index.php?title=Problem_solving&amp;diff=17357&amp;oldid=prev</id>
		<title>Daniel K. Schneider: /* Jonassen problem types */</title>
		<link rel="alternate" type="text/html" href="http://w.arbores.tech/w/index.php?title=Problem_solving&amp;diff=17357&amp;oldid=prev"/>
		<updated>2019-04-16T16:44:03Z</updated>

		<summary type="html">&lt;p&gt;&lt;span dir=&quot;auto&quot;&gt;&lt;span class=&quot;autocomment&quot;&gt;Jonassen problem types&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 18:44, 16 April 2019&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-notice&quot; lang=&quot;en&quot;&gt;&lt;div class=&quot;mw-diff-empty&quot;&gt;(No difference)&lt;/div&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</summary>
		<author><name>Daniel K. Schneider</name></author>
	</entry>
	<entry>
		<id>http://w.arbores.tech/w/index.php?title=Problem_solving&amp;diff=16762&amp;oldid=prev</id>
		<title>edutechwiki_en&gt;Daniel K. Schneider: /* Jonassen problem types */</title>
		<link rel="alternate" type="text/html" href="http://w.arbores.tech/w/index.php?title=Problem_solving&amp;diff=16762&amp;oldid=prev"/>
		<updated>2019-04-16T16:44:03Z</updated>

		<summary type="html">&lt;p&gt;&lt;span dir=&quot;auto&quot;&gt;&lt;span class=&quot;autocomment&quot;&gt;Jonassen problem types&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{stub}}&lt;br /&gt;
== Introduction ==&lt;br /&gt;
&lt;br /&gt;
This article aims to address &amp;quot;problem solving&amp;quot; in education, i.e. how one make learners acquire problem-solving skills.&lt;br /&gt;
&lt;br /&gt;
{{quotation|Problem solving is generally regarded as the&lt;br /&gt;
most important cognitive activity in everyday&lt;br /&gt;
and professional contexts. Most people are&lt;br /&gt;
required to and rewarded for solving problems.&lt;br /&gt;
However, learning to solve problems is too&lt;br /&gt;
seldom required informal educational settings,&lt;br /&gt;
in part, because our understanding of its&lt;br /&gt;
processes is limited.}} (Jonassen, 2000)&amp;lt;ref name=&amp;quot;jonassen2000&amp;quot;&amp;gt;Jonassen, D. H. (2007). A Taxonomy of Meaningful Learning. Educational Technology, 47(5), 30–35. Retrieved from https://www.jstor.org/stable/44429440?seq=1#metadata_info_tab_contents &amp;lt;/ref&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
Jonassen also states that problem solving is not {{quotation|sufficiently acknowledged or articulated in the instructional design literature}} (p.63). But he also mentioned that problem-solving is at the center of practice in contemporary learning theory: {{quotation|Contemporary conceptions of student-centered learning&lt;br /&gt;
environments, such as open-ended learning&lt;br /&gt;
environments (Hannafin, Hall, Land, &amp;amp; Hill, 1994; Land &amp;amp; Hannafin, 1996) &amp;lt;ref&amp;gt;Hannafin, MJ., Hall, C., Land, S., &amp;amp; Hill, J. (1994). Learning in open-ended learning environments: Assumptions, methods, and implications. Educational Technology, 34(8), 48-55.&amp;lt;/ref&amp;gt;,&lt;br /&gt;
goal-based scenarios (Schank, Fano, Bell, &amp;amp; Jona, 1993/1994) &amp;lt;ref&amp;gt;Schank, R.C., Fano, A., Bell, B., &amp;amp; Jona, M. (1993/1994). The design of goal-based scenarios. The Journal of the Learning Sciences, 3(4), 305-345. &amp;lt;/ref&amp;gt;,&lt;br /&gt;
and even problem-based learning (Barrows, 1985; Barrows &amp;amp; Tamblyn, 1980) &amp;lt;ref&amp;gt;Barrows, H.S. (1985). How to design a problem-based curriculum for the pre-clinical years. New York: Springer. &amp;lt;/ref&amp;gt;&lt;br /&gt;
focus on problem-solving outcomes. They recommend&lt;br /&gt;
instructional strategies, such as authentic cases,&lt;br /&gt;
simulations, modeling, coaching, and scaffolding, to support their implicit problem-solving&lt;br /&gt;
outcomes, but they inadequately analyze or&lt;br /&gt;
explicate the nature of the problems to be solved}}&lt;br /&gt;
(Jonassen, 2000a).&lt;br /&gt;
&lt;br /&gt;
== The anatomy of problem solving ==&lt;br /&gt;
&lt;br /&gt;
There are many definitions of &amp;#039;&amp;#039;problem solving&amp;#039;&amp;#039; both in psychology and related fields and computational sciences. &lt;br /&gt;
&lt;br /&gt;
In a computational perspective, in order to solve a problem, a problem-solver has to&lt;br /&gt;
perform a certain number of internal and external operations.&lt;br /&gt;
Each &amp;#039;&amp;#039;domain of action&amp;#039;&amp;#039; has in principle a certain&lt;br /&gt;
number of known &amp;#039;&amp;#039;operators&amp;#039;&amp;#039;,&lt;br /&gt;
i.e. generic actions that can be applied to a certain&lt;br /&gt;
class of mental or physical objects.&lt;br /&gt;
An &amp;#039;&amp;#039;operation&amp;#039;&amp;#039; is thus defined as concrete&lt;br /&gt;
realization (application) of an operator.&lt;br /&gt;
An operator is generally more abstract and more&lt;br /&gt;
general than one of its possible operation instantiation.&lt;br /&gt;
Each object that can form a problem&lt;br /&gt;
is a potential domain of action that can&lt;br /&gt;
be in different &amp;#039;&amp;#039;states&amp;#039;&amp;#039;.&lt;br /&gt;
Such a state is defined by several sub-states that&lt;br /&gt;
we can called &amp;#039;&amp;#039;facts&amp;#039;&amp;#039;.&lt;br /&gt;
We can call the set of facts that describe a problem&lt;br /&gt;
a &amp;#039;&amp;#039;description&amp;#039;&amp;#039;.&lt;br /&gt;
Thus technically speaking, problem solving&lt;br /&gt;
means transforming states by applying operators to&lt;br /&gt;
the facts, where a fact can be a mental object&lt;br /&gt;
or a physical object,&lt;br /&gt;
and an operation a mental or physical process.&lt;br /&gt;
This potential domain of action can&lt;br /&gt;
be call &amp;#039;&amp;#039;problem-domain&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
The selection and use of operators is driven by heuristics at various levels that we will not introduce here for the moment.&lt;br /&gt;
&lt;br /&gt;
== Jonassen problem types ==&lt;br /&gt;
&lt;br /&gt;
In his 2000 article &amp;lt;ref name=&amp;quot;jonassen2000&amp;quot; /&amp;gt; on &amp;#039;&amp;#039;Toward a Design Theory of Problem Solving&amp;#039;&amp;#039;, Jonassen identifies a number of problem-solving types: (a) logical,(b) algorithmic, (c) story, (d) rule-using, (e) decision making, (0 troubleshooting, (g) diagnosis-solution, (h) strategic performance, (i) case&lt;br /&gt;
analysis, (j) design, and (k) dilemma. In a 2011 article &amp;lt;ref name=&amp;quot;jonassen2011&amp;quot;&amp;gt;Jonassen, D. H. (2007). A Taxonomy of Meaningful Learning. Educational Technology, 47(5), 30–35. Retrieved from https://www.jstor.org/stable/44429440?seq=1#metadata_info_tab_contents &amp;lt;/ref&amp;gt;, Jonassen lists (a) story problems, (b) rule-using/rule induction problems, (c) decision-making problems, (d) troubleshooting problems, (e) strategic performance problems, (f) policy problems, (g) design problems, and (h) dilemmas.&lt;br /&gt;
&lt;br /&gt;
He also summarized these problem typologies as five abstract types as presented in the [[taxonomy of meaningful learning]] article. Problems are not the same and each type requires different educational designs.&lt;br /&gt;
&lt;br /&gt;
Each problem solving type was caracterized by a number of attribues:&lt;br /&gt;
* learning activity&lt;br /&gt;
* inputs&lt;br /&gt;
* success criteria&lt;br /&gt;
* context&lt;br /&gt;
* structuredness&lt;br /&gt;
* abstractness&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Problem type&lt;br /&gt;
! Learning activity !!Inputs&lt;br /&gt;
!Success criteria&lt;br /&gt;
!Context&lt;br /&gt;
!&lt;br /&gt;
Structuredness&lt;br /&gt;
!Abstractness&lt;br /&gt;
|-&lt;br /&gt;
| Logical  &lt;br /&gt;
|logical&lt;br /&gt;
&lt;br /&gt;
control and&lt;br /&gt;
&lt;br /&gt;
manipulation&lt;br /&gt;
&lt;br /&gt;
of limited&lt;br /&gt;
&lt;br /&gt;
variables;&lt;br /&gt;
&lt;br /&gt;
solve puzzle&lt;br /&gt;
|||||||&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Algorithmic ||procedural&lt;br /&gt;
&lt;br /&gt;
sequence of&lt;br /&gt;
manipulations;&lt;br /&gt;
algorithmic&lt;br /&gt;
process&lt;br /&gt;
applied to&lt;br /&gt;
similar sets&lt;br /&gt;
of variables;&lt;br /&gt;
Calculating&lt;br /&gt;
or producing&lt;br /&gt;
correct answer&lt;br /&gt;
|||||||&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Story ||disambiguate&lt;br /&gt;
variables;&lt;br /&gt;
select and&lt;br /&gt;
apply&lt;br /&gt;
algorithm to&lt;br /&gt;
produce&lt;br /&gt;
correct&lt;br /&gt;
answer using&lt;br /&gt;
prescribed&lt;br /&gt;
method&lt;br /&gt;
|||||||&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Rule-using ||procedural&lt;br /&gt;
process&lt;br /&gt;
constrained&lt;br /&gt;
by rules;&lt;br /&gt;
select and&lt;br /&gt;
apply rules&lt;br /&gt;
to produce&lt;br /&gt;
system-&lt;br /&gt;
constrained&lt;br /&gt;
answers or&lt;br /&gt;
products&lt;br /&gt;
|||||||&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Decision making ||identifying&lt;br /&gt;
&lt;br /&gt;
benefits and&lt;br /&gt;
&lt;br /&gt;
limitations;&lt;br /&gt;
&lt;br /&gt;
weighting&lt;br /&gt;
&lt;br /&gt;
options;&lt;br /&gt;
&lt;br /&gt;
selecting&lt;br /&gt;
&lt;br /&gt;
alternative&lt;br /&gt;
&lt;br /&gt;
and justifying&lt;br /&gt;
|||||||&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Trouble shooting ||examine&lt;br /&gt;
&lt;br /&gt;
system; run&lt;br /&gt;
&lt;br /&gt;
tests; evaluate&lt;br /&gt;
&lt;br /&gt;
results; hypo-&lt;br /&gt;
&lt;br /&gt;
thesize and&lt;br /&gt;
&lt;br /&gt;
confirm fault&lt;br /&gt;
&lt;br /&gt;
states using&lt;br /&gt;
&lt;br /&gt;
strategies (re-&lt;br /&gt;
&lt;br /&gt;
place, serial&lt;br /&gt;
&lt;br /&gt;
elimination,&lt;br /&gt;
&lt;br /&gt;
space split)&lt;br /&gt;
|||||||&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Diagnosis-&lt;br /&gt;
solution &lt;br /&gt;
|troubleshoot&lt;br /&gt;
&lt;br /&gt;
system faults;&lt;br /&gt;
&lt;br /&gt;
select and&lt;br /&gt;
&lt;br /&gt;
evaluate&lt;br /&gt;
&lt;br /&gt;
treatment&lt;br /&gt;
&lt;br /&gt;
options and&lt;br /&gt;
&lt;br /&gt;
monitor;&lt;br /&gt;
&lt;br /&gt;
apply&lt;br /&gt;
&lt;br /&gt;
problem&lt;br /&gt;
&lt;br /&gt;
schemas&lt;br /&gt;
|||||||&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Strategic &lt;br /&gt;
performance&lt;br /&gt;
|applying&lt;br /&gt;
&lt;br /&gt;
tactics&lt;br /&gt;
&lt;br /&gt;
to meet&lt;br /&gt;
&lt;br /&gt;
strategy in&lt;br /&gt;
&lt;br /&gt;
real-time,&lt;br /&gt;
&lt;br /&gt;
complex&lt;br /&gt;
&lt;br /&gt;
performance&lt;br /&gt;
&lt;br /&gt;
maintaining&lt;br /&gt;
&lt;br /&gt;
situational&lt;br /&gt;
&lt;br /&gt;
awareness&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Case analysis&lt;br /&gt;
|solution&lt;br /&gt;
&lt;br /&gt;
identification,&lt;br /&gt;
&lt;br /&gt;
alternative&lt;br /&gt;
&lt;br /&gt;
actions,&lt;br /&gt;
&lt;br /&gt;
argue&lt;br /&gt;
&lt;br /&gt;
position&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Design&lt;br /&gt;
|acting on&lt;br /&gt;
&lt;br /&gt;
goals to&lt;br /&gt;
&lt;br /&gt;
produce&lt;br /&gt;
&lt;br /&gt;
artifact;&lt;br /&gt;
&lt;br /&gt;
problem&lt;br /&gt;
&lt;br /&gt;
structuring&lt;br /&gt;
&lt;br /&gt;
&amp;amp;&lt;br /&gt;
&lt;br /&gt;
articulation&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|Dilemmas&lt;br /&gt;
|reconciling&lt;br /&gt;
&lt;br /&gt;
complex,&lt;br /&gt;
&lt;br /&gt;
non-&lt;br /&gt;
&lt;br /&gt;
predictive,&lt;br /&gt;
&lt;br /&gt;
vexing&lt;br /&gt;
&lt;br /&gt;
decision&lt;br /&gt;
&lt;br /&gt;
with no&lt;br /&gt;
&lt;br /&gt;
solution;&lt;br /&gt;
&lt;br /&gt;
perspectives&lt;br /&gt;
&lt;br /&gt;
irreconcil-&lt;br /&gt;
&lt;br /&gt;
able&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Bibliography ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[category: learning theories]]&lt;br /&gt;
[[category: educational theories]]{{edutechwiki}}&lt;/div&gt;</summary>
		<author><name>edutechwiki_en&gt;Daniel K. Schneider</name></author>
	</entry>
</feed>