<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
   xmlns="http://purl.org/rss/1.0/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/"
   xmlns:dcterms="http://purl.org/dc/terms/"
>
<channel rdf:about="http://www.citeulike.org/about">

	<title>CiteULike: rabourn's design-process</title>
	<description>CiteULike: rabourn's design-process</description>


	<link>http://www.citeulike.org/user/rabourn/tag/design-process</link>
	<dc:publisher>CiteULike.org</dc:publisher>
	<dc:language>en-gb</dc:language>
	<dc:rights>Copyright &#169; 2004-2008 citeulike.org</dc:rights>
	<items>
    <rdf:Seq>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/1127156"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/455087"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/200800"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/200356"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/240389"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/319864"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/227940"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/420453"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/226967"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/400340"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/311304"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/201538"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/201522"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/1013"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/903"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/rabourn/article/895"/>

	</rdf:Seq>
	</items>
	</channel>


<item rdf:about="http://www.citeulike.org/user/rabourn/article/1127156">
    <title>Epistemological and theoretical challenges for studying power and politics in information systems</title>
    <link>http://www.citeulike.org/user/rabourn/article/1127156</link>
    <description>&lt;i&gt;Information Systems Journal, Vol. 17, No. 2. (April 2007), pp. 165-183.&lt;/i&gt;</description>
    <dc:title>Epistemological and theoretical challenges for studying power and politics in information systems</dc:title>

    <dc:creator>Silva</dc:creator>
    <dc:creator>Leiser</dc:creator>
    <dc:identifier>doi:10.1111/j.1365-2575.2007.00232.x</dc:identifier>
    <dc:source>Information Systems Journal, Vol. 17, No. 2. (April 2007), pp. 165-183.</dc:source>
    <dc:date>2007-02-27T13:25:02-00:00</dc:date>
    <prism:publicationName>Information Systems Journal</prism:publicationName>
    <prism:issn>1350-1917</prism:issn>
    <prism:volume>17</prism:volume>
    <prism:number>2</prism:number>
    <prism:startingPage>165</prism:startingPage>
    <prism:endingPage>183</prism:endingPage>
    <prism:publisher>Blackwell Publishing</prism:publisher>
    <prism:category>design-process</prism:category>
    <prism:category>epistemology</prism:category>
    <prism:category>theory</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/455087">
    <title>Managing cross-cultural issues in global software outsourcing</title>
    <link>http://www.citeulike.org/user/rabourn/article/455087</link>
    <description>&lt;i&gt;Commun. ACM, Vol. 47, No. 4. (April 2004), pp. 62-66.&lt;/i&gt;</description>
    <dc:title>Managing cross-cultural issues in global software outsourcing</dc:title>

    <dc:creator>S Krishna</dc:creator>
    <dc:creator>Sundeep Sahay</dc:creator>
    <dc:creator>Geoff Walsham</dc:creator>
    <dc:identifier>doi:10.1145/975817.975818</dc:identifier>
    <dc:source>Commun. ACM, Vol. 47, No. 4. (April 2004), pp. 62-66.</dc:source>
    <dc:date>2006-01-03T23:07:24-00:00</dc:date>
    <prism:publicationName>Commun. ACM</prism:publicationName>
    <prism:issn>0001-0782</prism:issn>
    <prism:volume>47</prism:volume>
    <prism:number>4</prism:number>
    <prism:startingPage>62</prism:startingPage>
    <prism:endingPage>66</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>context</prism:category>
    <prism:category>culture</prism:category>
    <prism:category>design-process</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/200800">
    <title>Human Values and the Design of Computer Technology</title>
    <link>http://www.citeulike.org/user/rabourn/article/200800</link>
    <description>&lt;i&gt;(15 February 2001)&lt;/i&gt;</description>
    <dc:title>Human Values and the Design of Computer Technology</dc:title>

    <dc:creator>Batya Friedman</dc:creator>
    <dc:source>(15 February 2001)</dc:source>
    <dc:date>2005-05-15T18:25:03-00:00</dc:date>
    <prism:publisher>Center for the Study of Language and Inf</prism:publisher>
    <prism:category>culture</prism:category>
    <prism:category>design-process</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/200356">
    <title>Behind the Blip: Essays on the Culture of Software</title>
    <link>http://www.citeulike.org/user/rabourn/article/200356</link>
    <description>&lt;i&gt;(01 July 2003)&lt;/i&gt;</description>
    <dc:title>Behind the Blip: Essays on the Culture of Software</dc:title>

    <dc:creator>Matthew Fuller</dc:creator>
    <dc:source>(01 July 2003)</dc:source>
    <dc:date>2005-05-14T21:56:23-00:00</dc:date>
    <prism:publisher>Autonomedia</prism:publisher>
    <prism:category>design-process</prism:category>
    <prism:category>sociology</prism:category>
    <prism:category>sts</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/240389">
    <title>Research Through Practice: Positioning the Practitioner as Researcher</title>
    <link>http://www.citeulike.org/user/rabourn/article/240389</link>
    <description>&lt;i&gt;Working Papers in Art and Design, Vol. 1 (2000)&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;A new conceptualisation of the relationship between practice and research is evolving as individual institutions put forward different examples of research and its relationship to professional and/or academic practice. It seems unlikely that as a discipline group we will reach consensus as to the legitimacy of one approach over another. A more likely process is the development of a debate, in which there is no one right way to do research, but in which the proposing of different interpretations of the practice /research relationship becomes a vital aspect of research culture itself. This paper evaluates selected examples of doctoral and postdoctoral research currently being developed at Gray's School of Art in Aberdeen, in which practice constitutes a critical part of the research methodology, a form of research through practice. It is shaped both by the academic and cultural /professional context in which the research is placed. Research questions or issues are articulated from the outset, the research is therefore intentional, not assumed; a methodology is identified to address the questions and with analysis, published as an argument which is text and visually based, depending on the nature of the original research questions. Practice and the framing of research questions through practice, forms the experimental basis of the research, in which individuals function as practitioner- researchers. This approach is legible and negotiated with the academic community as well as with sectors of the professions involved in culture, cultural policy, museums, art administration, design management. The paper will articulate in what way practice through research differs from other current approaches, such as within the context of studio practice in which research is fused with creative development as an assumed and unpublished personal activity. It also differs from a more professionally led approach in which research is &#34;time off&#34; from the pressures of creating product for an audience/client body to focus on the creator's process. This provides a mechanism for developing new fresh avenues, the outcome of which is often text based publication. Within this co-authored paper the different phases of postdoctoral and doctoral research are represented within a research centre which itself is positioned at a nodal point between academic, cultural and professional contexts. The paper attempts to address the current confusion surrounding different interpretations within both the terminology and practice of research, which arise in different locations and within different funding and support structures.</description>
    <dc:title>Research Through Practice: Positioning the Practitioner as Researcher</dc:title>

    <dc:creator>Anne Douglas</dc:creator>
    <dc:source>Working Papers in Art and Design, Vol. 1 (2000)</dc:source>
    <dc:date>2005-06-29T18:21:59-00:00</dc:date>
    <prism:publicationName>Working Papers in Art and Design</prism:publicationName>
    <prism:volume>1</prism:volume>
    <prism:category>design-process</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/319864">
    <title>Requirements Elicitation Using a Combination of Prototypes and Scenarios</title>
    <link>http://www.citeulike.org/user/rabourn/article/319864</link>
    <description>&lt;i&gt;&lt;/i&gt;</description>
    <dc:title>Requirements Elicitation Using a Combination of Prototypes and Scenarios</dc:title>

    <dc:creator>Markus</dc:creator>
    <dc:date>2005-09-14T14:24:15-00:00</dc:date>
    <prism:category>design-process</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/227940">
    <title>The myths of usability ROI</title>
    <link>http://www.citeulike.org/user/rabourn/article/227940</link>
    <description>&lt;i&gt;interactions, Vol. 11, No. 5. (2004), pp. 22-29.&lt;/i&gt;</description>
    <dc:title>The myths of usability ROI</dc:title>

    <dc:creator>Daniel Rosenberg</dc:creator>
    <dc:identifier>doi:10.1145/1015530.1015541</dc:identifier>
    <dc:source>interactions, Vol. 11, No. 5. (2004), pp. 22-29.</dc:source>
    <dc:date>2005-06-14T20:31:28-00:00</dc:date>
    <prism:publicationName>interactions</prism:publicationName>
    <prism:issn>1072-5520</prism:issn>
    <prism:volume>11</prism:volume>
    <prism:number>5</prism:number>
    <prism:startingPage>22</prism:startingPage>
    <prism:endingPage>29</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>design-process</prism:category>
    <prism:category>interface-design</prism:category>
    <prism:category>usability</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/420453">
    <title>Conceptual design: from user requirements to user interface</title>
    <link>http://www.citeulike.org/user/rabourn/article/420453</link>
    <description>&lt;i&gt;(1998), pp. 163-164.&lt;/i&gt;</description>
    <dc:title>Conceptual design: from user requirements to user interface</dc:title>

    <dc:creator>Kathy Potosnak</dc:creator>
    <dc:identifier>doi:10.1145/286498.286643</dc:identifier>
    <dc:source>(1998), pp. 163-164.</dc:source>
    <dc:date>2005-12-02T21:31:49-00:00</dc:date>
    <prism:startingPage>163</prism:startingPage>
    <prism:endingPage>164</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>design-process</prism:category>
    <prism:category>interface-design</prism:category>
    <prism:category>usability</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/226967">
    <title>Using Evolutionary Prototypes to Formalize Product Requirements</title>
    <link>http://www.citeulike.org/user/rabourn/article/226967</link>
    <description>&lt;i&gt;&lt;/i&gt;</description>
    <dc:title>Using Evolutionary Prototypes to Formalize Product Requirements</dc:title>

    <dc:creator>BH Junius</dc:creator>
    <dc:date>2005-06-13T14:35:54-00:00</dc:date>
    <prism:category>bricolage</prism:category>
    <prism:category>collaboration</prism:category>
    <prism:category>design-process</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/400340">
    <title>Finding Boundary Objects in SE and HCI: An approach through engineering oriented design theories</title>
    <link>http://www.citeulike.org/user/rabourn/article/400340</link>
    <description>&lt;i&gt;(2003), pp. 92-99.&lt;/i&gt;</description>
    <dc:title>Finding Boundary Objects in SE and HCI: An approach through engineering oriented design theories</dc:title>

    <dc:creator>A Walenstein</dc:creator>
    <dc:source>(2003), pp. 92-99.</dc:source>
    <dc:date>2005-11-18T23:03:09-00:00</dc:date>
    <prism:startingPage>92</prism:startingPage>
    <prism:endingPage>99</prism:endingPage>
    <prism:category>collaboration</prism:category>
    <prism:category>design-process</prism:category>
    <prism:category>sociology</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/311304">
    <title>When you can't talk to customers: using storyboards and narratives to elicit empathy for users</title>
    <link>http://www.citeulike.org/user/rabourn/article/311304</link>
    <description>&lt;i&gt;(2003), pp. 120-125.&lt;/i&gt;</description>
    <dc:title>When you can't talk to customers: using storyboards and narratives to elicit empathy for users</dc:title>

    <dc:creator>Heather Mcquaid</dc:creator>
    <dc:creator>Aradhana Goel</dc:creator>
    <dc:creator>Mickey Mcmanus</dc:creator>
    <dc:identifier>doi:10.1145/782896.782926</dc:identifier>
    <dc:source>(2003), pp. 120-125.</dc:source>
    <dc:date>2005-09-03T21:01:55-00:00</dc:date>
    <prism:startingPage>120</prism:startingPage>
    <prism:endingPage>125</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>design-process</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/201538">
    <title>Sustainable software development</title>
    <link>http://www.citeulike.org/user/rabourn/article/201538</link>
    <description>&lt;i&gt;(2004), pp. 274-278.&lt;/i&gt;</description>
    <dc:title>Sustainable software development</dc:title>

    <dc:creator>Heike Winschiers</dc:creator>
    <dc:creator>Barbara Paterson</dc:creator>
    <dc:source>(2004), pp. 274-278.</dc:source>
    <dc:date>2005-05-16T15:52:40-00:00</dc:date>
    <prism:startingPage>274</prism:startingPage>
    <prism:endingPage>278</prism:endingPage>
    <prism:publisher>South African Institute for Computer Scientists and Information Technologists</prism:publisher>
    <prism:category>design-process</prism:category>
    <prism:category>globalization</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/201522">
    <title>Cognitive Artifacts in Complex Work</title>
    <link>http://www.citeulike.org/user/rabourn/article/201522</link>
    <description>&lt;i&gt;Lecture Notes in Computer Science, Vol. 3345 (February 2005), pp. 152-183.&lt;/i&gt;</description>
    <dc:title>Cognitive Artifacts in Complex Work</dc:title>

    <dc:creator>Peter Jones</dc:creator>
    <dc:creator>Christopher Nemeth</dc:creator>
    <dc:source>Lecture Notes in Computer Science, Vol. 3345 (February 2005), pp. 152-183.</dc:source>
    <dc:date>2005-05-16T15:17:09-00:00</dc:date>
    <prism:publicationName>Lecture Notes in Computer Science</prism:publicationName>
    <prism:volume>3345</prism:volume>
    <prism:startingPage>152</prism:startingPage>
    <prism:endingPage>183</prism:endingPage>
    <prism:category>design-process</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/1013">
    <title>Why good engineers (sometimes) create bad interfaces</title>
    <link>http://www.citeulike.org/user/rabourn/article/1013</link>
    <description>&lt;i&gt;(1990), pp. 277-282.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;This paper presents a view of system design that shows how good engineering practice can lead to poor user interfaces. From the engineer’s perspective, the ideal interface reflects the underlying mechanism and affords direct access to the control points of the mechanism. The designer of the user interface is often also the designer of the mechanism (or at least is very familiar with the mechanism), and thus has a strong bias toward basing the interface on the engineering model. The user, however, wants to complete a task, and an interface that is based on the task is often more appropriate than one based on the system mechanism. We discuss these issues, and also discuss where to position the user interface between the poles of the engineering model and the task model.</description>
    <dc:title>Why good engineers (sometimes) create bad interfaces</dc:title>

    <dc:creator>Donald Gentner</dc:creator>
    <dc:creator>Jonathan Grudin</dc:creator>
    <dc:identifier>doi:10.1145/97243.97287</dc:identifier>
    <dc:source>(1990), pp. 277-282.</dc:source>
    <dc:date>2004-11-24T19:42:05-00:00</dc:date>
    <prism:startingPage>277</prism:startingPage>
    <prism:endingPage>282</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>design-process</prism:category>
    <prism:category>interface-design</prism:category>
    <prism:category>usability</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/903">
    <title>Design as bricolage: anthropology meets design thinking</title>
    <link>http://www.citeulike.org/user/rabourn/article/903</link>
    <description>&lt;i&gt;Design Studies, Vol. 20, No. 6. (November 1999), pp. 517-535.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;We identify a metaphor for the design activity: we view design as bricolage. We start from describing bricolage, and we proceed to the relationship of design to art. We obtain a characterisation of design that enables us to show that both traditional and contemporary design are forms of bricolage. We examine the consequences of `design as bricolage' for the relationship between design and science and for the extent of the design activity.</description>
    <dc:title>Design as bricolage: anthropology meets design thinking</dc:title>

    <dc:creator>P Louridas</dc:creator>
    <dc:identifier>doi:10.1016/S0142-694X(98)00044-1</dc:identifier>
    <dc:source>Design Studies, Vol. 20, No. 6. (November 1999), pp. 517-535.</dc:source>
    <dc:date>2004-11-22T04:15:06-00:00</dc:date>
    <prism:publicationName>Design Studies</prism:publicationName>
    <prism:volume>20</prism:volume>
    <prism:number>6</prism:number>
    <prism:startingPage>517</prism:startingPage>
    <prism:endingPage>535</prism:endingPage>
    <prism:category>bricolage</prism:category>
    <prism:category>design-process</prism:category>
    <prism:category>design-thinking</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/rabourn/article/895">
    <title>Is designing mysterious? challenging the dual knowledge thesis</title>
    <link>http://www.citeulike.org/user/rabourn/article/895</link>
    <description>&lt;i&gt;Design Studies, Vol. 12, No. 3. (July 1991), pp. 124-131.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;The hermeneutical philosophy of Gadamer and Heidegger and the pragmatism of Dewey are brought to bear in arguing against the view that designing involves a special kind of knowledge that is fundamentally difficult to grasp and therefore mysterious. The hermeneutical thesis maintains that understanding is acquired in a manner best described in terms of bringing expectations to bear on a situation. These expectations are derived from our effective historical consciousness and are constantly being renewed as we respond to situations. This mode of thinking is the only way of thinking, whether we are solving a mathematical problem or creating a work of art. Not withstanding this 'common sense' understanding, claims for the mystery of designing persist. These claims are examined in turn in the light of a hermeneutical understanding of thought. They include the dual knowledge thesis, the more fundamental notion of the thinking subject isolated from the world of objects, and the subjectivism of the Romantic movement that is evident in writings about the genius loci. There is then a consideration of the sense in which it is appropriate to talk about designing as being different to other activities and how this impinges on design teaching and practice. The argument is presented that when mystery is removed then effective dialogue, and hence learning, can ensue.</description>
    <dc:title>Is designing mysterious? challenging the dual knowledge thesis</dc:title>

    <dc:creator>Richard Coyne</dc:creator>
    <dc:creator>Adrian Snodgrass</dc:creator>
    <dc:identifier>doi:10.1016/0142-694X(91)90020-W</dc:identifier>
    <dc:source>Design Studies, Vol. 12, No. 3. (July 1991), pp. 124-131.</dc:source>
    <dc:date>2004-11-22T01:12:17-00:00</dc:date>
    <prism:publicationName>Design Studies</prism:publicationName>
    <prism:volume>12</prism:volume>
    <prism:number>3</prism:number>
    <prism:startingPage>124</prism:startingPage>
    <prism:endingPage>131</prism:endingPage>
    <prism:category>design-process</prism:category>
</item>



</rdf:RDF>

