<?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: What do you really need?</title>
	<atom:link href="http://www.dancingmango.com/blog/2009/10/12/what-do-you-really-need/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dancingmango.com/blog/2009/10/12/what-do-you-really-need/</link>
	<description>For more than a decade Marc has been a passionate advocate of placing the customer at the heart of business, working with clients in finance, retail, government and entertainment sectors, helping them craft compelling cross channel customer experiences.  Marc champions lean and agile approaches for making customer driven innovation happen.  He brings design thinking and creativity to clients, engaging across the organisation with a focus on delivery as well as ideas.  He is currently writing a book on Agile Experience Design to be published this Autumn.</description>
	<lastBuildDate>Sun, 25 Sep 2011 23:33:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James Christie</title>
		<link>http://www.dancingmango.com/blog/2009/10/12/what-do-you-really-need/comment-page-1/#comment-132927</link>
		<dc:creator>James Christie</dc:creator>
		<pubDate>Tue, 13 Oct 2009 10:58:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.dancingmango.com/blog/?p=754#comment-132927</guid>
		<description>Thanks. Did you look up my article? The question of usability was fairly peripheral, but I think the intersection between security and usability testing is an interesting topic that doesn&#039;t seem to have received as much attention as it deserves. Personas and usability techniques should be among the tools that functional and security testers call on when they&#039;re considering how applications can be abused. I wasn&#039;t familiar with Extreme Characters, but I tracked down the paper I think you meant. 
http://homepage.mac.com/j.p.djajadiningrat/publications/2000DjajDISInte.pdf. It was very interesting.

Of course using these Extreme Characters would be rather different from what I was thinking of. That paper&#039;s about product design. However, the interesting point is that such characters are needed because of the limitations of stock, stereotypical personas that have just bland, &quot;good&quot; characteristics and who will behave in neat, predictable ways. And if they&#039;re going to be predictable, why bother with personas at all? Surely you have to think a bit more deeply than that about your users and what motivates them.

A big problem for testers is that their rushed functional testing, which looks at what the application is supposed to be doing, is hopelessly superficial compared to the deep understanding that real users will acquire over time of what the application actually can do. It&#039;s impossible for testers to acquire that deep knowledge in a limited time, but if they use well-judged personas, unleash their imagination and start looking at the application in a different and more cynical way then they can expose serious weaknesses.  

Unfortunately the documentation heavy approach that software testers have traditionally placed too much emphasis on proving the application can do what it&#039;s meant to and haven&#039;t allowed testers time to use their imagination to discover whether it can do thing  it really shouldn&#039;t.</description>
		<content:encoded><![CDATA[<p>Thanks. Did you look up my article? The question of usability was fairly peripheral, but I think the intersection between security and usability testing is an interesting topic that doesn&#8217;t seem to have received as much attention as it deserves. Personas and usability techniques should be among the tools that functional and security testers call on when they&#8217;re considering how applications can be abused. I wasn&#8217;t familiar with Extreme Characters, but I tracked down the paper I think you meant.<br />
<a href="http://homepage.mac.com/j.p.djajadiningrat/publications/2000DjajDISInte.pdf" rel="nofollow">http://homepage.mac.com/j.p.djajadiningrat/publications/2000DjajDISInte.pdf</a>. It was very interesting.</p>
<p>Of course using these Extreme Characters would be rather different from what I was thinking of. That paper&#8217;s about product design. However, the interesting point is that such characters are needed because of the limitations of stock, stereotypical personas that have just bland, &#8220;good&#8221; characteristics and who will behave in neat, predictable ways. And if they&#8217;re going to be predictable, why bother with personas at all? Surely you have to think a bit more deeply than that about your users and what motivates them.</p>
<p>A big problem for testers is that their rushed functional testing, which looks at what the application is supposed to be doing, is hopelessly superficial compared to the deep understanding that real users will acquire over time of what the application actually can do. It&#8217;s impossible for testers to acquire that deep knowledge in a limited time, but if they use well-judged personas, unleash their imagination and start looking at the application in a different and more cynical way then they can expose serious weaknesses.  </p>
<p>Unfortunately the documentation heavy approach that software testers have traditionally placed too much emphasis on proving the application can do what it&#8217;s meant to and haven&#8217;t allowed testers time to use their imagination to discover whether it can do thing  it really shouldn&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marc</title>
		<link>http://www.dancingmango.com/blog/2009/10/12/what-do-you-really-need/comment-page-1/#comment-132864</link>
		<dc:creator>marc</dc:creator>
		<pubDate>Mon, 12 Oct 2009 15:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.dancingmango.com/blog/?p=754#comment-132864</guid>
		<description>I like the article!

&#039;Bad guy personas&#039;... Are you familiar with Extreme Characters?  There&#039;s a paper out there where the authors introduced a drug dealer and the pope and new personas in the product development processes to see how their needs could be addressed</description>
		<content:encoded><![CDATA[<p>I like the article!</p>
<p>&#8216;Bad guy personas&#8217;&#8230; Are you familiar with Extreme Characters?  There&#8217;s a paper out there where the authors introduced a drug dealer and the pope and new personas in the product development processes to see how their needs could be addressed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Christie</title>
		<link>http://www.dancingmango.com/blog/2009/10/12/what-do-you-really-need/comment-page-1/#comment-132859</link>
		<dc:creator>James Christie</dc:creator>
		<pubDate>Mon, 12 Oct 2009 13:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.dancingmango.com/blog/?p=754#comment-132859</guid>
		<description>This struck a chord with me. I&#039;ve worked as a computer auditor, and I&#039;m very interested in usability issues. Something that has troubled me when I&#039;ve reviewed applications is the way existing functionality has been carried forward without serious scrutiny. I suppose my particular concern has been the corollary of yours. I&#039;m interested in how the functionality can be exploited, and what the latent, unintended functionality might be. Ideally I&#039;d like a form of usability testing involving bad guy personas trying to exploit the application, but that;&#039;s getting onto another subject.

I recently wrote this in an article in Testing Experience magazine discussing flaws in an insurance application that had been exploited by fraudulent users.

&lt;i&gt;&quot;The control weaknesses related to an abuse of the authorization process, and a failure of the application to deal appropriately with third party claims payments, which were extremely vulnerable to fraud. These weaknesses would have been present in the original manual process, but the users and developers had not taken the opportunities that a new computer application had offered to introduce more sophisticated controls.

No-one had been negligent or even careless in the design of the application and the surrounding procedures. The trouble was that the requirements had focused on the positive functions of the application, and on replicating the functionality of the previous application, which in turn had been based on the original manual process. There had not been sufficient analysis of how the application could be exploited.&quot;&lt;/i&gt;</description>
		<content:encoded><![CDATA[<p>This struck a chord with me. I&#8217;ve worked as a computer auditor, and I&#8217;m very interested in usability issues. Something that has troubled me when I&#8217;ve reviewed applications is the way existing functionality has been carried forward without serious scrutiny. I suppose my particular concern has been the corollary of yours. I&#8217;m interested in how the functionality can be exploited, and what the latent, unintended functionality might be. Ideally I&#8217;d like a form of usability testing involving bad guy personas trying to exploit the application, but that;&#8217;s getting onto another subject.</p>
<p>I recently wrote this in an article in Testing Experience magazine discussing flaws in an insurance application that had been exploited by fraudulent users.</p>
<p><i>&#8220;The control weaknesses related to an abuse of the authorization process, and a failure of the application to deal appropriately with third party claims payments, which were extremely vulnerable to fraud. These weaknesses would have been present in the original manual process, but the users and developers had not taken the opportunities that a new computer application had offered to introduce more sophisticated controls.</p>
<p>No-one had been negligent or even careless in the design of the application and the surrounding procedures. The trouble was that the requirements had focused on the positive functions of the application, and on replicating the functionality of the previous application, which in turn had been based on the original manual process. There had not been sufficient analysis of how the application could be exploited.&#8221;</i></p>
]]></content:encoded>
	</item>
</channel>
</rss>

