<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet href="/Data/Templates/Bright Light (Stretched)/RssDisplay.xslt" type="text/xsl"?>
<rss version="2.0">
  <channel>
    <title>Testability.com - News</title>
    <link>http://articles.testability.com</link>
    <description />
    <language>en-gb</language>
    <copyright>Testability.com</copyright>
    <generator>Developer Fusion RSS Feed Generator v1.0</generator>
    <webMaster>dhartop@dsiintl.com</webMaster>
    <lastBuildDate>Mon, 05 Jan 2009 16:24:39 GMT</lastBuildDate>
    <ttl>20</ttl>
    <item>
      <title>Designing for Health;  A Methodology for Integrated Diagnostics/Prognostics </title>
      <link>/Articles/9/1/Designing_for_Health__A_Methodology_for_Integrated_DiagnosticsPrognostics_.aspx</link>
      <description>&lt;a target='_blank' href="http://articles.testability.com/Data/ArticleImages/Slide1LG.jpg"&gt;&lt;IMG src="http://articles.testability.com/Data/ArticleImages/Slide1SM.jpg"&gt;&lt;/a&gt;</description>
      <author>Testability.com Author</author>
      <pubDate>Wed, 23 Apr 2008 00:00:00 GMT</pubDate>
      <subject />
    </item>
    <item>
      <title>The Birth of Design for Testability</title>
      <link>/Articles/4/1/The_Birth_of_Design_for_Testability.aspx</link>
      <description>&lt;P class=MsoNormal style="mso-pagination: none"&gt;&lt;SPAN lang=en-US style="language: en-US; mso-ansi-language: en-US"&gt;Slowly, over the last four decades, industry has gradually begun to give Design for Testability the attention it truly deserves. This concept was originally pioneered by Ralph De Paul, Jr. in the mid 1960’s based on diagnostic ideas that he had developed in the 1950’s.&amp;nbsp;&lt;SPAN lang=en-US style="language: en-US; mso-ansi-language: en-US"&gt;During its first two decades, Design for Testability remained largely an “outsider” discipline, accepted only by a relatively small group of industry experts, until the idea finally began to take hold in the mid 1980’s.&lt;/SPAN&gt;&lt;SPAN lang=en-US style="language: en-US"&gt;&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;SPAN lang=en-US style="language: en-US"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;</description>
      <author>Testability.com Author</author>
      <pubDate>Tue, 22 Apr 2008 00:00:00 GMT</pubDate>
      <subject />
    </item>
    <item>
      <title>Independent Systems Engineering vs. Programmatic Systems Engineering</title>
      <link>/Articles/5/1/Independent_Systems_Engineering_vs_Programmatic_Systems_Engineering.aspx</link>
      <description>&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"&gt;&lt;SPAN lang=EN style="FONT-SIZE: 11pt; FONT-FAMILY: Arial; mso-ansi-language: EN"&gt;The awarding of DoD Programs has continued to evolve over the recent decades toward a culture that exploits the concept of “Teaming” on the development of complex products or systems for many major programs. This concept appears to allow contractors to&amp;nbsp;leverage each Team member’s particular strengths in their respective areas of expertise into a unified partnering environment. To facilitate this objective, the partnering environment must agree upon a mutual acceptable means and mechanism to integrate these individual products together into the developing of a superior end-product.&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;</description>
      <author>Testability.com Author</author>
      <pubDate>Tue, 22 Apr 2008 00:00:00 GMT</pubDate>
      <subject />
    </item>
    <item>
      <title>Optimizing Test Strategies</title>
      <link>/Articles/2/1/Optimizing_Test_Strategies.aspx</link>
      <description>&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;Optimizing test strategies can be a long journey. A successful journey requires knowing what roads to try and how to measure progress along the way.&lt;/SPAN&gt;</description>
      <author>Testability.com Author</author>
      <pubDate>Tue, 06 Jul 2004 00:00:00 GMT</pubDate>
      <subject />
    </item>
    <item>
      <title>Testability on the Shuttle Program</title>
      <link>/Articles/3/1/Testability_on_the_Shuttle_Program.aspx</link>
      <description>&lt;FONT face=Arial size=2&gt;Story by Darrel Fritts on some of the tasks and lessons learned from&amp;nbsp;diagnostics, testability and dependency modeling on the Shuttle program.&lt;/FONT&gt;</description>
      <author>Darrel Fritts</author>
      <pubDate>Tue, 29 Jun 2004 00:00:00 GMT</pubDate>
      <subject />
    </item>
  </channel>
</rss>