<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exam essay: Design science</title>
	<atom:link href="http://visual.placodermi.org/2009/01/02/exam-essay-design-science/feed/" rel="self" type="application/rss+xml" />
	<link>http://visual.placodermi.org/2009/01/02/exam-essay-design-science/</link>
	<description></description>
	<lastBuildDate>Wed, 18 Aug 2010 16:00:05 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Malek</title>
		<link>http://visual.placodermi.org/2009/01/02/exam-essay-design-science/comment-page-1/#comment-1029</link>
		<dc:creator>Chris Malek</dc:creator>
		<pubDate>Fri, 02 Jan 2009 07:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://visual.placodermi.org/?p=471#comment-1029</guid>
		<description>&lt;strong&gt;My self-critique:&lt;/strong&gt;

I had to go back to my notes in order to remember all of Hevner’s seven characteristics of good design science research, so that wasn’t so good.   Maybe I can remember it better if I tell it as a story of the research process:   We want to make an artifact that provides utility both to the business and to the research community (this is the research contribution).  We evaluate our solution in order to determine utility and applicability, and we provide a research contribution by solving a heretofore unsolved yet important business problem (or by providing a better solution to a solved problem) in a scientifically rigorous (but not too rigorous) manner.  And we want to communicate our results to both practitioners and scientists.   Don’t try to remember the numbers from the paper, remember the story I told above, keeping in mind that design science occurs in a real business environment and yet is science, too, and so we have two sets of criteria and two audiences.  That and that design science is concerned with utility, and not understanding.

I had trouble remembering how you evaluate non-instantiation artifacts.   It goes like this: you evaluate them by how well they help you to design instantiations, essentially.   I would guess that this means: evaluate constructs by how well they allow you to model; evaluate models by how well they allow you to build methods and instantiations; and methods by how well they help you design appropriate instantiations.   The evaluations go from the general to the specific (assuming that constructs are the most general and instantiations are the most specific).
I should add that the symbiotic relationship between behavioral science and design science also goes behavioral -&gt; design: behavioral science develops the theories and expands the IS knowledge base that design science uses.
I should talk about how design science has two audiences: practitioners and scientists.  And in this way it is a way (like action science) of addressing the rigor-relevance dilemma.

I feel like this was a little short.  I probably needed to expand the evaluations bit and the rigor bit.  I could also expand the communication bit.</description>
		<content:encoded><![CDATA[<p><strong>My self-critique:</strong></p>
<p>I had to go back to my notes in order to remember all of Hevner’s seven characteristics of good design science research, so that wasn’t so good.   Maybe I can remember it better if I tell it as a story of the research process:   We want to make an artifact that provides utility both to the business and to the research community (this is the research contribution).  We evaluate our solution in order to determine utility and applicability, and we provide a research contribution by solving a heretofore unsolved yet important business problem (or by providing a better solution to a solved problem) in a scientifically rigorous (but not too rigorous) manner.  And we want to communicate our results to both practitioners and scientists.   Don’t try to remember the numbers from the paper, remember the story I told above, keeping in mind that design science occurs in a real business environment and yet is science, too, and so we have two sets of criteria and two audiences.  That and that design science is concerned with utility, and not understanding.</p>
<p>I had trouble remembering how you evaluate non-instantiation artifacts.   It goes like this: you evaluate them by how well they help you to design instantiations, essentially.   I would guess that this means: evaluate constructs by how well they allow you to model; evaluate models by how well they allow you to build methods and instantiations; and methods by how well they help you design appropriate instantiations.   The evaluations go from the general to the specific (assuming that constructs are the most general and instantiations are the most specific).<br />
I should add that the symbiotic relationship between behavioral science and design science also goes behavioral -> design: behavioral science develops the theories and expands the IS knowledge base that design science uses.<br />
I should talk about how design science has two audiences: practitioners and scientists.  And in this way it is a way (like action science) of addressing the rigor-relevance dilemma.</p>
<p>I feel like this was a little short.  I probably needed to expand the evaluations bit and the rigor bit.  I could also expand the communication bit.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
