<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Software Requirements Talk</title>
  <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/rss" />
  <subtitle>Software Requirements Talk</subtitle>
  <entry>
    <title>The Inhibited Analyst</title>
    <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/the-inhibited-analyst" />
    <author>
      <name>Brandi Ortega</name>
    </author>
    <id>http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/the-inhibited-analyst</id>
    <updated>2011-11-17T16:43:43Z</updated>
    <published>2011-11-17T16:43:43Z</published>
    <summary type="html">&lt;p&gt;Requirements analysts need to be more inquisitive and know why people want things as well as what happens beforehand. This requires them to become less inhibited and keep asking questions until they and their stakeholders are satisfied with the answers.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;Listen:&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;&lt;embed height="20" width="350" flashvars="file=http://media.computer.org/sponsored/podcast/swreqtalk/srt-0009v.mp3" allowfullscreen="true" allowscriptaccess="always" bgcolor="undefined" src="http://www.computer.org/portal/cms/Computer.org/csmediacenter/mediaplayer/player.swf"&gt;&lt;/embed&gt;&lt;/p&gt;</summary>
    <dc:creator>Brandi Ortega</dc:creator>
    <dc:date>2011-11-17T16:43:43Z</dc:date>
  </entry>
  <entry>
    <title>What Time Is It, Eccles?</title>
    <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/what-time-is-it-eccles-" />
    <author>
      <name>Brandi Ortega</name>
    </author>
    <id>http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/what-time-is-it-eccles-</id>
    <updated>2011-10-28T16:21:23Z</updated>
    <published>2011-10-28T16:21:23Z</published>
    <summary type="html">&lt;p&gt;Requirements analysts need a new toolbox with both the right tools and the instructions to use them including agile development and user-centered design for techniques such as analysis of Web analytics, wire-framing, and user stories. We can also look to the creativity literature and take techniques such as constraint removal, storytelling, and other worlds.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;Listen:&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;&lt;embed width="350" height="20" flashvars="file=http://media.computer.org/sponsored/podcast/swreqtalk/srt-0008v.mp3" allowfullscreen="true" allowscriptaccess="always" bgcolor="undefined" src="http://www.computer.org/portal/cms/Computer.org/csmediacenter/mediaplayer/player.swf"&gt;&lt;/embed&gt;&lt;/p&gt;</summary>
    <dc:creator>Brandi Ortega</dc:creator>
    <dc:date>2011-10-28T16:21:23Z</dc:date>
  </entry>
  <entry>
    <title>Requirements Analysis: The Next Generation</title>
    <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/requirements-analysis:-the-next-generation" />
    <author>
      <name>Brandi Ortega</name>
    </author>
    <id>http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/requirements-analysis:-the-next-generation</id>
    <updated>2011-09-14T21:28:46Z</updated>
    <published>2011-09-14T21:28:46Z</published>
    <summary type="html">&lt;p&gt;Most requirements research and vision papers tend to focus on the near future, one research advance at a time. This podcast explores requirements practices 20 years from now, based on predicted changes to technologies, applications, and stakeholders.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;Listen:&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;&lt;embed width="350" height="20" flashvars="file=http://media.computer.org/sponsored/podcast/swreqtalk/srt-0007v.mp3" allowfullscreen="true" allowscriptaccess="always" bgcolor="undefined" src="http://www.computer.org/portal/cms/Computer.org/csmediacenter/mediaplayer/player.swf"&gt;&lt;/embed&gt;&lt;/p&gt;</summary>
    <dc:creator>Brandi Ortega</dc:creator>
    <dc:date>2011-09-14T21:28:46Z</dc:date>
  </entry>
  <entry>
    <title>Requirements and Aesthetics</title>
    <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/requirements-and-aesthetics" />
    <author>
      <name>Brandi Ortega</name>
    </author>
    <id>http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/requirements-and-aesthetics</id>
    <updated>2011-05-04T17:12:59Z</updated>
    <published>2011-04-27T20:42:46Z</published>
    <summary type="html">&lt;p&gt;Requirements people rarely talk about aesthetics. This column draws on the 10 principles of good design from Dieter Rams to examine the important roles of aesthetics in requirements practices. It proposes the use of meaning carriers to think about new types of requirements.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;Listen:&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;&lt;embed width="350" height="20" flashvars="file=http://media.computer.org/sponsored/podcast/swreqtalk/srt-0006v.mp3" allowfullscreen="true" allowscriptaccess="always" bgcolor="undefined" src="http://www.computer.org/portal/cms/Computer.org/csmediacenter/mediaplayer/player.swf"&gt;&lt;/embed&gt;&lt;/p&gt;</summary>
    <dc:creator>Brandi Ortega</dc:creator>
    <dc:date>2011-04-27T20:42:46Z</dc:date>
  </entry>
  <entry>
    <title>GORE, SORE, or What?</title>
    <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/gore-sore-or-what-" />
    <author>
      <name>Brandi Ortega</name>
    </author>
    <id>http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/gore-sore-or-what-</id>
    <updated>2010-12-20T18:20:42Z</updated>
    <published>2010-12-20T16:35:34Z</published>
    <summary type="html">&lt;h3&gt;by Ian Alexander&lt;/h3&gt;&lt;p&gt;Competing schools of thought in both research and industry advocate different approaches to requirements. Each favors one particular kind of artifact, such as scenarios, goals, priorities, and context models. But focusing on any one of these risks failing to discover critical project information that could readily be unearthed by other means. Perhaps a mix-and-match approach that combines requirement methods would be more effective.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;Listen:&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;&lt;embed width="350" height="20" src="http://www.computer.org/portal/cms/Computer.org/csmediacenter/mediaplayer/player.swf" bgcolor="undefined" allowscriptaccess="always" allowfullscreen="true" flashvars="file=http://media.computer.org/sponsored/podcast/swreqtalk/srt-0005v.mp3"&gt;&lt;/embed&gt;&lt;/p&gt;</summary>
    <dc:creator>Brandi Ortega</dc:creator>
    <dc:date>2010-12-20T16:35:34Z</dc:date>
  </entry>
  <entry>
    <title>Storyboarding Requirements</title>
    <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/storyboarding-requirements" />
    <author>
      <name>Brandi Ortega</name>
    </author>
    <id>http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/storyboarding-requirements</id>
    <updated>2010-11-15T22:29:05Z</updated>
    <published>2010-11-15T22:29:05Z</published>
    <summary type="html">&lt;p&gt;This installment of Software Requirements Talk describes a way to use storyboards to capture the interplay between human interaction and service design and so improve the quality of service design delivery.&lt;/p&gt; &lt;p&gt;&lt;strong&gt;Listen:&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;&lt;embed height="20" width="350" flashvars="file=http://media.computer.org/sponsored/podcast/swreqtalk/srt-0004v.mp3" allowfullscreen="true" allowscriptaccess="always" bgcolor="undefined" src="http://www.computer.org/portal/cms/Computer.org/csmediacenter/mediaplayer/player.swf"&gt;&lt;/embed&gt;&lt;/p&gt;</summary>
    <dc:creator>Brandi Ortega</dc:creator>
    <dc:date>2010-11-15T22:29:05Z</dc:date>
  </entry>
  <entry>
    <title>Oi! Analysts</title>
    <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/oi!-analysts" />
    <author>
      <name>Brandi Ortega</name>
    </author>
    <id>http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/oi!-analysts</id>
    <updated>2010-11-15T22:23:55Z</updated>
    <published>2010-08-09T17:35:56Z</published>
    <summary type="html">&lt;p&gt;Certification for requirements analysts requires focusing on a small, possibly unrepresentative, set of tasks that might not reflect domain knowledge and could lead to good analysts not getting certified because they don't do well on the exam.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Listen:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;embed height="20" width="350" flashvars="file=http://media.computer.org/sponsored/podcast/swreqtalk/srt-0003v.mp3" allowfullscreen="true" allowscriptaccess="always" bgcolor="undefined" src="http://www.computer.org/portal/cms/Computer.org/csmediacenter/mediaplayer/player.swf"&gt;&lt;/embed&gt;&lt;/p&gt;</summary>
    <dc:creator>Brandi Ortega</dc:creator>
    <dc:date>2010-08-09T17:35:56Z</dc:date>
  </entry>
  <entry>
    <title>Service Design, It's All in the Brand</title>
    <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/service-design-it-s-all-in-the-brand" />
    <author>
      <name>Brandi Ortega</name>
    </author>
    <id>http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/service-design-it-s-all-in-the-brand</id>
    <updated>2010-08-10T20:46:19Z</updated>
    <published>2010-08-09T17:35:09Z</published>
    <summary type="html">&lt;p&gt;This installment argues that requirements analysts will soon need to deal with service design, and describes one service design method to demonstrate the challenges that analysts will face.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Listen:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;embed height="20" width="350" flashvars="file=http://media.computer.org/sponsored/podcast/swreqtalk/srt-0002v.mp3" allowfullscreen="true" allowscriptaccess="always" bgcolor="undefined" src="http://www.computer.org/portal/cms/Computer.org/csmediacenter/mediaplayer/player.swf"&gt;&lt;/embed&gt;&lt;/p&gt;</summary>
    <dc:creator>Brandi Ortega</dc:creator>
    <dc:date>2010-08-09T17:35:09Z</dc:date>
  </entry>
  <entry>
    <title>Agile Requirements</title>
    <link rel="alternate" href="http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/agile-requirements" />
    <author>
      <name>Brandi Ortega</name>
    </author>
    <id>http://www.computer.org/portal/web/computingnow/software-requirements-talk/-/blogs/agile-requirements</id>
    <updated>2010-08-10T20:46:52Z</updated>
    <published>2010-08-09T17:33:40Z</published>
    <summary type="html">&lt;p&gt;This column looks at agile techniques in requirements processes, summarizes their successes and failures so far, and proposes that we re-consider our use of electronic documentation in requirements projects.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Listen:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;embed height="20" width="350" flashvars="file=http://media.computer.org/sponsored/podcast/swreqtalk/srt-0001v.mp3" allowfullscreen="true" allowscriptaccess="always" bgcolor="undefined" src="http://www.computer.org/portal/cms/Computer.org/csmediacenter/mediaplayer/player.swf"&gt;&lt;/embed&gt;&lt;/p&gt;</summary>
    <dc:creator>Brandi Ortega</dc:creator>
    <dc:date>2010-08-09T17:33:40Z</dc:date>
  </entry>
</feed>

