<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Alex Ivanov</title>
    <description>Alex Ivanov, Principle Systems Engineer at Raytheon Space and Airborne Systems, is a world recognized expert in bridging the gap between requirements management, system engineering and optimizing IBM Rational DOORS (with the DXL automation that it can bring). Alex is an IBM Certified Professional for: DOORS v9, DOORS Next Generation v5, Rational Quality Manager v3, Collaborative Lifecycle Management v4 (i.e. RTC, RQM, RRC) and is a four-time IBM Rational Champion (2011,2012,2013,2014). </description>
    <link>https://speakerdeck.com/doorswizard</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/doorswizard.rss"/>
    <lastBuildDate>2015-01-04 03:42:41 -0500</lastBuildDate>
    <item>
      <title>The Power of the Attribute Template Extended to Drive Metrics Collection</title>
      <description>Wouldn't it be nice if you could come up with all the things you wanted to count in your requirements specification(s) and then without having to know any custom DXL get numbers produced for each count (i.e. how many requirements do I have? how many child requirements do not trace up to a parent requirement? etc...) on a by requirement module basis? This is the reality of using the Attribute Template to drive your Metrics collection, now let me show you how.</description>
      <media:content url="https://files.speakerdeck.com/presentations/3721c8a0761b01329e143ebd37303ddc/preview_slide_0.jpg?4310666" type="image/jpeg" medium="image"/>
      <content:encoded>Wouldn't it be nice if you could come up with all the things you wanted to count in your requirements specification(s) and then without having to know any custom DXL get numbers produced for each count (i.e. how many requirements do I have? how many child requirements do not trace up to a parent requirement? etc...) on a by requirement module basis? This is the reality of using the Attribute Template to drive your Metrics collection, now let me show you how.</content:encoded>
      <pubDate>Tue, 26 Jun 2012 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/doorswizard/the-power-of-the-attribute-template-extended-to-drive-metrics-collection</link>
      <guid>https://speakerdeck.com/doorswizard/the-power-of-the-attribute-template-extended-to-drive-metrics-collection</guid>
    </item>
  </channel>
</rss>
