<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Suspect flags in Systems/Software Engineering</title>
    <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44170#M434</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Karthik,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this time I do not believe the ReqIF (Requirements Interchange Format) standard supports the concept of Suspect flags. See &lt;A class="loading" href="http://www.omg.org/spec/ReqIF/Current/" title="http://www.omg.org/spec/ReqIF/Current/"&gt;http://www.omg.org/spec/ReqIF/Current/&lt;/A&gt; for the most up to date ReqIF definition.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 28 Oct 2014 17:06:57 GMT</pubDate>
    <dc:creator>JoeBartlett</dc:creator>
    <dc:date>2014-10-28T17:06:57Z</dc:date>
    <item>
      <title>Suspect flags</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44169#M433</link>
      <description>Hello All,I have a document in Doors which has been converted to RIF via Atego Requirements Synchronizer 2.4. This RIF file has been now pushed to Integrity using RIF Utility 2.5. In the meantime the Doors requirement document has been updated; now I would have to export Doors document</description>
      <pubDate>Wed, 02 May 2018 22:49:26 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44169#M433</guid>
      <dc:creator>kkomarla</dc:creator>
      <dc:date>2018-05-02T22:49:26Z</dc:date>
    </item>
    <item>
      <title>Re: Suspect flags</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44170#M434</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Karthik,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this time I do not believe the ReqIF (Requirements Interchange Format) standard supports the concept of Suspect flags. See &lt;A class="loading" href="http://www.omg.org/spec/ReqIF/Current/" title="http://www.omg.org/spec/ReqIF/Current/"&gt;http://www.omg.org/spec/ReqIF/Current/&lt;/A&gt; for the most up to date ReqIF definition.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Oct 2014 17:06:57 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44170#M434</guid>
      <dc:creator>JoeBartlett</dc:creator>
      <dc:date>2014-10-28T17:06:57Z</dc:date>
    </item>
    <item>
      <title>Re: Suspect flags</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44171#M435</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joe,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the ReqIF definition link. I shall spend some time with the documents to understand ReqIF better. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Oct 2014 14:59:20 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44171#M435</guid>
      <dc:creator>kkomarla</dc:creator>
      <dc:date>2014-10-29T14:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: Suspect flags</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44172#M436</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Karthik,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;just to add some ideas: The suspect feature in Integrity is driven by significant changes in an item (node). The traced item (node) will become suspect when the upstream item receives this change.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To my knowledge, if you import a document again into the same (existing), and if some field values have changed, Integrity shall react with suspect flags appearing in the downstream traced items(nodes).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(e.g. if you re-import an input document with changes in it, the related requirement document nodes shall become suspect)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this what you want?&lt;/P&gt;&lt;P&gt;Volker&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Oct 2014 20:25:55 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44172#M436</guid>
      <dc:creator>VolkerEckardt</dc:creator>
      <dc:date>2014-10-29T20:25:55Z</dc:date>
    </item>
    <item>
      <title>Re: Suspect flags</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44173#M437</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Volker,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the hint, I will look into the trace relationships. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But what I am concerned about is, "A Doors document is pushed into integrity implementing RIF utility, after this a front end user modifies the Doors document now how would i know that the Doors document is updated (other than manually looking into the document or getting a notification)? Secondly, if we know that the document is updated, how would i trace what exactly has been changed." &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once i know what has been updated or changed, only then i will proceed with migration of this document i.e. from Doors to Integrity. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Karthik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Oct 2014 08:05:09 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44173#M437</guid>
      <dc:creator>kkomarla</dc:creator>
      <dc:date>2014-10-30T08:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: Suspect flags</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44174#M438</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kartik,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1/&lt;/P&gt;&lt;P&gt;what about using the Integrity History Compare Reports?&lt;/P&gt;&lt;P&gt;This report will list differences between two timestamps of the document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2/&lt;/P&gt;&lt;P&gt;to find the changed nodes, what about using the filter and select all "suspect" Trace status types? Then you see all changed nodes only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this help?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Volker&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Oct 2014 08:38:47 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44174#M438</guid>
      <dc:creator>VolkerEckardt</dc:creator>
      <dc:date>2014-10-30T08:38:47Z</dc:date>
    </item>
    <item>
      <title>Re: Suspect flags</title>
      <link>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44175#M439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The second point sure does help. I will start testing these shortly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Karthik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Oct 2014 09:51:08 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Systems-Software-Engineering/Suspect-flags/m-p/44175#M439</guid>
      <dc:creator>kkomarla</dc:creator>
      <dc:date>2014-10-30T09:51:08Z</dc:date>
    </item>
  </channel>
</rss>

