<?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">
<pubDate>Thu, 21 Aug 2008 15:14:24 BST</pubDate>


	<title>CiteULike: Tag scen</title>
	<description>CiteULike: Tag scen</description>


	<link>http://www.citeulike.org/tag/scen</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/maike/article/625005"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/674656"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/133541"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/762409"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/820225"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/347906"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/1506190"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/989101"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/989102"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/881678"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/888456"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/943052"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/223137"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/311304"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/1082936"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/1275443"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/625341"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/989130"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/222845"/>
        <rdf:li rdf:resource="http://www.citeulike.org/user/maike/article/1292104"/>

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


<item rdf:about="http://www.citeulike.org/user/maike/article/625005">
    <title>Visualizing use context with picture scenarios in the design process</title>
    <link>http://www.citeulike.org/user/maike/article/625005</link>
    <description>&lt;i&gt;(2005), pp. 271-274.&lt;/i&gt;</description>
    <dc:title>Visualizing use context with picture scenarios in the design process</dc:title>

    <dc:creator>Sonja Pedell</dc:creator>
    <dc:creator>Frank Vetere</dc:creator>
    <dc:identifier>doi:10.1145/1085777.1085829</dc:identifier>
    <dc:source>(2005), pp. 271-274.</dc:source>
    <dc:date>2006-05-12T12:28:11-00:00</dc:date>
    <prism:publicationYear>2005</prism:publicationYear>
    <prism:startingPage>271</prism:startingPage>
    <prism:endingPage>274</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>2005</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/674656">
    <title>Requirements elicitation and validation with real world scenes</title>
    <link>http://www.citeulike.org/user/maike/article/674656</link>
    <description>&lt;i&gt;Software Engineering, IEEE Transactions on, Vol. 24, No. 12. (1998), pp. 1036-1054.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;A requirements specification defines the requirements for the future system at a conceptual level (i.e., class or type level). In contrast, a scenario represents a concrete example of current or future system usage. In early RE phases, scenarios are used to support the definition of high level requirements (goals) to be achieved by the new system. In many cases, those goals can to a large degree be elicited by observing, documenting and analyzing scenarios about current system usage. To support the elicitation and validation of the goals achieved by the existing system and to illustrate problems of the old system, we propose to capture current system usage using rich media (e.g., video, speech, pictures, etc.) and to interrelate those observations with the goal definitions. Thus, we aim at making the abstraction process which leads to the definition of the conceptual models more transparent and traceable. We relate the parts of the observations which have caused the definition of a goal or against which a goal was validated with the corresponding goal. These interrelations provide the basis for: 1) explaining and illustrating a goal model to, e.g., untrained stakeholders and/or new team members; 2) detecting, analyzing, and resolving a different interpretation of the observations; 3) comparing different observations using computed goal annotations; and 4) refining or detailing a goal model during later process phases. Using the PRIME implementation framework, we have implemented the PRIME-CREWS environment, which supports the interrelation of conceptual models and captured system usage observations. We report on our experiences with PRIME-CREWS gained in an experimental case study</description>
    <dc:title>Requirements elicitation and validation with real world scenes</dc:title>

    <dc:creator>P Haumer</dc:creator>
    <dc:creator>K Pohl</dc:creator>
    <dc:creator>K Weidenhaupt</dc:creator>
    <dc:source>Software Engineering, IEEE Transactions on, Vol. 24, No. 12. (1998), pp. 1036-1054.</dc:source>
    <dc:date>2006-05-30T03:22:21-00:00</dc:date>
    <prism:publicationYear>1998</prism:publicationYear>
    <prism:publicationName>Software Engineering, IEEE Transactions on</prism:publicationName>
    <prism:volume>24</prism:volume>
    <prism:number>12</prism:number>
    <prism:startingPage>1036</prism:startingPage>
    <prism:endingPage>1054</prism:endingPage>
    <prism:category>1998</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/133541">
    <title>Facilitating collaboration through design games</title>
    <link>http://www.citeulike.org/user/maike/article/133541</link>
    <description>&lt;i&gt;(2004), pp. 121-131.&lt;/i&gt;</description>
    <dc:title>Facilitating collaboration through design games</dc:title>

    <dc:creator>Eva Brandt</dc:creator>
    <dc:creator>Jörn Messeter</dc:creator>
    <dc:identifier>doi:10.1145/1011870.1011885</dc:identifier>
    <dc:source>(2004), pp. 121-131.</dc:source>
    <dc:date>2005-03-20T00:34:42-00:00</dc:date>
    <prism:publicationYear>2004</prism:publicationYear>
    <prism:startingPage>121</prism:startingPage>
    <prism:endingPage>131</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>2004</prism:category>
    <prism:category>dg</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/762409">
    <title>Teaching HCI with scenario-based design: the constructivist's synthesis</title>
    <link>http://www.citeulike.org/user/maike/article/762409</link>
    <description>&lt;i&gt;(2001), pp. 9-12.&lt;/i&gt;</description>
    <dc:title>Teaching HCI with scenario-based design: the constructivist's synthesis</dc:title>

    <dc:creator>Kam Vat</dc:creator>
    <dc:identifier>doi:10.1145/377435.377445</dc:identifier>
    <dc:source>(2001), pp. 9-12.</dc:source>
    <dc:date>2006-07-17T19:53:51-00:00</dc:date>
    <prism:publicationYear>2001</prism:publicationYear>
    <prism:issn>0097-8418</prism:issn>
    <prism:startingPage>9</prism:startingPage>
    <prism:endingPage>12</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>2001</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/820225">
    <title>Scenario-Based Design: Envisioning Work and Technology in System Development</title>
    <link>http://www.citeulike.org/user/maike/article/820225</link>
    <description>&lt;i&gt;(15 May 1995)&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Growing out of a historic workshop sponsored by IBM, this book brings together contributions from many of the leading figures in the field of human-computer interaction and object-oriented software engineering. The first book-length work devoted entirely to the subject of use-oriented design representations&#8212;or scenarios&#8212;it discusses an array of scenario-based design approaches and demonstrates their practical applications across the system development life cycle, from requirements analysis and software design, to documentation, training, and prototype evaluation. &#60;p&#62;Translates the latest research findings into techniques that readers can immediately use to enhance the effectiveness of user-interface design and object-oriented software engineering design &#60;p&#62;Features contributions from the top names in the field, including Rebecca Wirfs-Brock, Ivar Jacobson, Jakob Nielsen, Tom Carey, Allan MacLean, Scott Robertson, Morten Kyng, Mary Beth Rosson, and others &#60;p&#62;Assesses the effectiveness of various scenario-based design approaches in dealing with a wide range of design problems and in different types and sizes of organizations &#60;p&#62;Packed with case studies and enlightening illustrations</description>
    <dc:title>Scenario-Based Design: Envisioning Work and Technology in System Development</dc:title>

    <dc:creator>John Carroll</dc:creator>
    <dc:source>(15 May 1995)</dc:source>
    <dc:date>2006-08-28T20:41:33-00:00</dc:date>
    <prism:publicationYear>1995</prism:publicationYear>
    <prism:publisher>John Wiley &#38; Sons</prism:publisher>
    <prism:category>1995</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/347906">
    <title>Developing use cases and scenarios in the requirements process</title>
    <link>http://www.citeulike.org/user/maike/article/347906</link>
    <description>&lt;i&gt;(2005), pp. 561-570.&lt;/i&gt;</description>
    <dc:title>Developing use cases and scenarios in the requirements process</dc:title>

    <dc:creator>Neil Maiden</dc:creator>
    <dc:creator>Suzanne Robertson</dc:creator>
    <dc:identifier>doi:10.1145/1062455.1062555</dc:identifier>
    <dc:source>(2005), pp. 561-570.</dc:source>
    <dc:date>2005-10-11T14:50:01-00:00</dc:date>
    <prism:publicationYear>2005</prism:publicationYear>
    <prism:startingPage>561</prism:startingPage>
    <prism:endingPage>570</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>2005</prism:category>
    <prism:category>req</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/1506190">
    <title>Scenarios in user-centred design--setting the stage for reflection and action</title>
    <link>http://www.citeulike.org/user/maike/article/1506190</link>
    <description>&lt;i&gt;Interacting with Computers, Vol. 13, No. 1. (September 2000), pp. 61-75.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;This paper discusses three examples of use of scenarios in user-centred design. Common to the examples are the use of scenarios to support the tensions between reflection and action, between typical and critical situations, and between plus and minus situations. The paper illustrates how a variety of more specific scenarios emphasising, e.g. critical situations, or even caricatures of situations are very useful for helping groups of users and designers being creative in design. Emphasising creativity in design is a very different view on the design process than normally represented in usability work or software/requirement engineering, where generalising users' actions are much more important than, in this paper, the suggested richness of and contradiction between actual use situations. In general the paper proposes to attune scenarios to the particular purposes of the situations they are to be used in, and to be very selective based on these purposes.</description>
    <dc:title>Scenarios in user-centred design--setting the stage for reflection and action</dc:title>

    <dc:creator>Susanne Bødker</dc:creator>
    <dc:identifier>doi:10.1016/S0953-5438(00)00024-2</dc:identifier>
    <dc:source>Interacting with Computers, Vol. 13, No. 1. (September 2000), pp. 61-75.</dc:source>
    <dc:date>2007-07-27T06:49:35-00:00</dc:date>
    <prism:publicationYear>2000</prism:publicationYear>
    <prism:publicationName>Interacting with Computers</prism:publicationName>
    <prism:volume>13</prism:volume>
    <prism:number>1</prism:number>
    <prism:startingPage>61</prism:startingPage>
    <prism:endingPage>75</prism:endingPage>
    <prism:category>2000</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/989101">
    <title>Participatory analysis: shared development of requirements from scenarios</title>
    <link>http://www.citeulike.org/user/maike/article/989101</link>
    <description>&lt;i&gt;(1997), pp. 162-169.&lt;/i&gt;</description>
    <dc:title>Participatory analysis: shared development of requirements from scenarios</dc:title>

    <dc:creator>George Chin</dc:creator>
    <dc:creator>Mary Rosson</dc:creator>
    <dc:creator>John Carroll</dc:creator>
    <dc:identifier>doi:10.1145/258549.258654</dc:identifier>
    <dc:source>(1997), pp. 162-169.</dc:source>
    <dc:date>2006-12-11T22:56:55-00:00</dc:date>
    <prism:publicationYear>1997</prism:publicationYear>
    <prism:startingPage>162</prism:startingPage>
    <prism:endingPage>169</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>1997</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/989102">
    <title>The blind men and the elephant: views of scenario-based system design</title>
    <link>http://www.citeulike.org/user/maike/article/989102</link>
    <description>&lt;i&gt;interactions, Vol. 11, No. 6. (2004), pp. 44-53.&lt;/i&gt;</description>
    <dc:title>The blind men and the elephant: views of scenario-based system design</dc:title>

    <dc:creator>Kentaro Go</dc:creator>
    <dc:creator>John Carroll</dc:creator>
    <dc:identifier>doi:10.1145/1029036.1029037</dc:identifier>
    <dc:source>interactions, Vol. 11, No. 6. (2004), pp. 44-53.</dc:source>
    <dc:date>2006-12-11T22:59:08-00:00</dc:date>
    <prism:publicationYear>2004</prism:publicationYear>
    <prism:publicationName>interactions</prism:publicationName>
    <prism:issn>1072-5520</prism:issn>
    <prism:volume>11</prism:volume>
    <prism:number>6</prism:number>
    <prism:startingPage>44</prism:startingPage>
    <prism:endingPage>53</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>2004</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/881678">
    <title>From user to character: an investigation into user-descriptions in scenarios</title>
    <link>http://www.citeulike.org/user/maike/article/881678</link>
    <description>&lt;i&gt;(2002), pp. 99-104.&lt;/i&gt;</description>
    <dc:title>From user to character: an investigation into user-descriptions in scenarios</dc:title>

    <dc:creator>Lene Nielsen</dc:creator>
    <dc:identifier>doi:10.1145/778712.778729</dc:identifier>
    <dc:source>(2002), pp. 99-104.</dc:source>
    <dc:date>2006-10-02T14:59:11-00:00</dc:date>
    <prism:publicationYear>2002</prism:publicationYear>
    <prism:startingPage>99</prism:startingPage>
    <prism:endingPage>104</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>2002</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>persona</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/888456">
    <title>Storyboarding: an empirical determination of best practices and effective guidelines</title>
    <link>http://www.citeulike.org/user/maike/article/888456</link>
    <description>&lt;i&gt;(2006), pp. 12-21.&lt;/i&gt;</description>
    <dc:title>Storyboarding: an empirical determination of best practices and effective guidelines</dc:title>

    <dc:creator>Khai Truong</dc:creator>
    <dc:creator>Gillian Hayes</dc:creator>
    <dc:creator>Gregory Abowd</dc:creator>
    <dc:identifier>doi:10.1145/1142405.1142410</dc:identifier>
    <dc:source>(2006), pp. 12-21.</dc:source>
    <dc:date>2006-10-07T14:08:18-00:00</dc:date>
    <prism:publicationYear>2006</prism:publicationYear>
    <prism:startingPage>12</prism:startingPage>
    <prism:endingPage>21</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>2006</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/943052">
    <title>Future fantasies: a social change perspective of retailing in the 21st century</title>
    <link>http://www.citeulike.org/user/maike/article/943052</link>
    <description>&lt;i&gt;Journal of Retailing, Vol. 78, No. 1. ( 2002), pp. 77-83.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Experts expect great retailing changes in the next ten years. What do consumers expect? With increasing innovation in retail technology and the large-scale implementation of e-commerce formats, shifts in consumer behavior can be categorized as social change. Sociologists have long studied the interaction of social change and technology, focusing on society members' characteristics to help predict the future. One characteristic of enduring influence is age. In this research note, we consider consumer expectations regarding the evolution of retailing, with an emphasis on expectations of social change and the variance of such expectations by age cohort.</description>
    <dc:title>Future fantasies: a social change perspective of retailing in the 21st century</dc:title>

    <dc:creator>Stacy Wood</dc:creator>
    <dc:identifier>doi:10.1016/S0022-4359(01)00069-0</dc:identifier>
    <dc:source>Journal of Retailing, Vol. 78, No. 1. ( 2002), pp. 77-83.</dc:source>
    <dc:date>2006-11-14T15:18:52-00:00</dc:date>
    <prism:publicationYear>2002</prism:publicationYear>
    <prism:publicationName>Journal of Retailing</prism:publicationName>
    <prism:volume>78</prism:volume>
    <prism:number>1</prism:number>
    <prism:startingPage>77</prism:startingPage>
    <prism:endingPage>83</prism:endingPage>
    <prism:category>2002</prism:category>
    <prism:category>emp</prism:category>
    <prism:category>mc</prism:category>
    <prism:category>scen</prism:category>
    <prism:category>shop</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/223137">
    <title>Scenario-Based Assessment of Nonfunctional Requirements</title>
    <link>http://www.citeulike.org/user/maike/article/223137</link>
    <description>&lt;i&gt;Software Engineering, IEEE Transactions on, Vol. 31, No. 5. (2005), pp. 392-409.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;This paper describes a method and a tool for validating nonfunctional requirements in complex socio-technical systems. The System Requirements Analyzer (SRA) tool validates system reliability and operational performance requirements using scenario-based testing. Scenarios are transformed into sequences of task steps and the reliability of human agents performing tasks with computerized technology is assessed using Bayesian Belief Network (BN) models. The tool tests system performance within an envelope of environmental variations and reports the number of tests that pass a benchmark threshold. The tool diagnoses problematic areas in scenarios representing pathways through system models, assists in the identification of their causes, and supports comparison of alternative requirements specifications and system designs. It is suitable for testing socio-technical systems where operational scenarios are sequential and deterministic, in domains where designs are incrementally modified so set up costs of the BNs can be defrayed over multiple tests.</description>
    <dc:title>Scenario-Based Assessment of Nonfunctional Requirements</dc:title>

    <dc:creator>A Gregoriades</dc:creator>
    <dc:creator>A Sutcliffe</dc:creator>
    <dc:source>Software Engineering, IEEE Transactions on, Vol. 31, No. 5. (2005), pp. 392-409.</dc:source>
    <dc:date>2005-06-09T04:53:56-00:00</dc:date>
    <prism:publicationYear>2005</prism:publicationYear>
    <prism:publicationName>Software Engineering, IEEE Transactions on</prism:publicationName>
    <prism:volume>31</prism:volume>
    <prism:number>5</prism:number>
    <prism:startingPage>392</prism:startingPage>
    <prism:endingPage>409</prism:endingPage>
    <prism:category>2005</prism:category>
    <prism:category>req</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/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/maike/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:publicationYear>2003</prism:publicationYear>
    <prism:startingPage>120</prism:startingPage>
    <prism:endingPage>125</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>2003</prism:category>
    <prism:category>design</prism:category>
    <prism:category>ethno</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/1082936">
    <title>Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle</title>
    <link>http://www.citeulike.org/user/maike/article/1082936</link>
    <description>&lt;i&gt;(15 October 2004)&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;&#60;ul&#62; &#60;li&#62;Extending the scenario method beyond interface design, this important book shows developers how to design more effective systems by soliciting, analyzing, and elaborating stories from end-users &#60;li&#62;Contributions from leading industry consultants and opinion-makers present a range of scenario techniques, from the light, sketchy, and agile to the careful and systematic &#60;li&#62;Includes real-world case studies from Philips, DaimlerChrysler, and Nokia, and covers systems ranging from custom software to embedded hardware-software systems &#60;/ul&#62; &#34; Extending the scenario method beyond interface design, this important book shows developers how to design more effective systems by soliciting, analyzing, and elaborating stories from end-users&#60;br&#62; Contributions from leading industry consultants and opinion-makers present a range of scenario techniques, from the light, sketchy, and agile to the careful and systematic&#60;br&#62; Includes real-world case studies from Philips, DaimlerChrysler, and Nokia, and covers systems ranging from custom software to embedded hardware-software systems&#34;</description>
    <dc:title>Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle</dc:title>

    <dc:creator>N Maiden</dc:creator>
    <dc:creator>I Alexander</dc:creator>
    <dc:source>(15 October 2004)</dc:source>
    <dc:date>2007-02-02T06:44:38-00:00</dc:date>
    <prism:publicationYear>2004</prism:publicationYear>
    <prism:publisher>John Wiley &#38; Sons</prism:publisher>
    <prism:category>008_pdc_lv</prism:category>
    <prism:category>2004</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/1275443">
    <title>Investigating the impact of usability on software architecture through scenarios: A case study on Web systems</title>
    <link>http://www.citeulike.org/user/maike/article/1275443</link>
    <description>&lt;i&gt;Journal of Systems and Software, Vol. 79, No. 3. (March 2006), pp. 415-426.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Usability has primarily been served by separating the user interface from the remainder of the application. However, several researchers have recently determined that there is a direct relationship between architectural decisions and usability requirements. This leads us to conclude that more attention should be devoted to usability-driven architectural analysis methods. We present a case study, which involves adapting an existing software architecture analysis method (SAAM) for the purpose of deriving the interdependencies between architectural characteristics and usability requirements. More specifically, we investigate the impact on the architecture of implementing usability requirement changes. Potential design solutions that accommodate the corresponding usability mechanisms into the Web software architecture are presented, along with the rationale for applying them and the process by which they are obtained. We conclude by recommending how usability issues can be dealt with proactively during the design of the architecture, and explain the need to integrate those usability requirements into a software engineering process.</description>
    <dc:title>Investigating the impact of usability on software architecture through scenarios: A case study on Web systems</dc:title>

    <dc:creator>Tamer Rafla</dc:creator>
    <dc:creator>Pierre Robillard</dc:creator>
    <dc:creator>Michel Desmarais</dc:creator>
    <dc:source>Journal of Systems and Software, Vol. 79, No. 3. (March 2006), pp. 415-426.</dc:source>
    <dc:date>2007-05-03T21:54:02-00:00</dc:date>
    <prism:publicationYear>2006</prism:publicationYear>
    <prism:publicationName>Journal of Systems and Software</prism:publicationName>
    <prism:volume>79</prism:volume>
    <prism:number>3</prism:number>
    <prism:startingPage>415</prism:startingPage>
    <prism:endingPage>426</prism:endingPage>
    <prism:category>2006</prism:category>
    <prism:category>req</prism:category>
    <prism:category>scen</prism:category>
    <prism:category>usab</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/625341">
    <title>Requirements development in scenario-based design</title>
    <link>http://www.citeulike.org/user/maike/article/625341</link>
    <description>&lt;i&gt;Software Engineering, IEEE Transactions on, Vol. 24, No. 12. (1998), pp. 1156-1170.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;We describe and analyze the process of requirements development in scenario based design through consideration of a case study. In our project, a group of teachers and system developers initially set out to create a virtual physics laboratory. Our design work centered on the collaborative development of a series of scenarios describing current and future classroom activities. We observed classroom scenarios to assess needs and opportunities, and envisioned future scenarios to specify and analyze possible design moves. We employed claims analysis to evaluate design trade-offs implicit in these scenarios, to codify the specific advantages and disadvantages in achieving requirements. Through the course of this process, the nature of our project requirements has evolved, providing more information but also more kinds of information. We discuss the utility of managing requirements development through an evolving set of scenarios, and the generality of the scenario stages from this case study</description>
    <dc:title>Requirements development in scenario-based design</dc:title>

    <dc:creator>JM Carroll</dc:creator>
    <dc:creator>MB Rosson</dc:creator>
    <dc:creator>G Chin</dc:creator>
    <dc:creator>J Koenemann</dc:creator>
    <dc:source>Software Engineering, IEEE Transactions on, Vol. 24, No. 12. (1998), pp. 1156-1170.</dc:source>
    <dc:date>2006-05-12T16:20:44-00:00</dc:date>
    <prism:publicationYear>1998</prism:publicationYear>
    <prism:publicationName>Software Engineering, IEEE Transactions on</prism:publicationName>
    <prism:volume>24</prism:volume>
    <prism:number>12</prism:number>
    <prism:startingPage>1156</prism:startingPage>
    <prism:endingPage>1170</prism:endingPage>
    <prism:category>2003</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/989130">
    <title>Scenario-based design</title>
    <link>http://www.citeulike.org/user/maike/article/989130</link>
    <description>&lt;i&gt;(2003), pp. 1032-1050.&lt;/i&gt;</description>
    <dc:title>Scenario-based design</dc:title>

    <dc:creator>Mary Rosson</dc:creator>
    <dc:creator>John Carroll</dc:creator>
    <dc:source>(2003), pp. 1032-1050.</dc:source>
    <dc:date>2006-12-11T23:33:00-00:00</dc:date>
    <prism:publicationYear>2003</prism:publicationYear>
    <prism:startingPage>1032</prism:startingPage>
    <prism:endingPage>1050</prism:endingPage>
    <prism:publisher>Lawrence Erlbaum Associates, Inc.</prism:publisher>
    <prism:category>2003</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/222845">
    <title>Scenario-based requirements engineering</title>
    <link>http://www.citeulike.org/user/maike/article/222845</link>
    <description>&lt;i&gt;Requirements Engineering Conference, 2003. Proceedings. 11th IEEE International (2003), pp. 320-329.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;We explain the concepts and process of scenario based requirements engineering. Definitions of scenarios are reviewed, with their informal and more formal representations, and roles in the requirements process. The relationships between scenarios, specifications and prototypes is explored, and set in the perspective of human reasoning about requirements. Methods for scenario based RE are described and one method, SCRAM, is covered in more depth. We conclude with a look forward to the future of scenario based RE and research directions.</description>
    <dc:title>Scenario-based requirements engineering</dc:title>

    <dc:creator>A Sutcliffe</dc:creator>
    <dc:source>Requirements Engineering Conference, 2003. Proceedings. 11th IEEE International (2003), pp. 320-329.</dc:source>
    <dc:date>2005-06-08T19:31:01-00:00</dc:date>
    <prism:publicationYear>2003</prism:publicationYear>
    <prism:publicationName>Requirements Engineering Conference, 2003. Proceedings. 11th IEEE International</prism:publicationName>
    <prism:startingPage>320</prism:startingPage>
    <prism:endingPage>329</prism:endingPage>
    <prism:category>2003</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



<item rdf:about="http://www.citeulike.org/user/maike/article/1292104">
    <title>Transfer scenarios: grounding innovation with marginal practices</title>
    <link>http://www.citeulike.org/user/maike/article/1292104</link>
    <description>&lt;i&gt;(2007), pp. 737-746.&lt;/i&gt;</description>
    <dc:title>Transfer scenarios: grounding innovation with marginal practices</dc:title>

    <dc:creator>Sara Ljungblad</dc:creator>
    <dc:creator>Lars Holmquist</dc:creator>
    <dc:identifier>doi:10.1145/1240624.1240738</dc:identifier>
    <dc:source>(2007), pp. 737-746.</dc:source>
    <dc:date>2007-05-13T05:07:33-00:00</dc:date>
    <prism:publicationYear>2007</prism:publicationYear>
    <prism:startingPage>737</prism:startingPage>
    <prism:endingPage>746</prism:endingPage>
    <prism:publisher>ACM Press</prism:publisher>
    <prism:category>2007</prism:category>
    <prism:category>pd</prism:category>
    <prism:category>scen</prism:category>
</item>



</rdf:RDF>

