Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Suspect Links Commands?
Topic Summary:
Created On: 4-Aug-2004 20:19
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 4-Aug-2004 20:19
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Haven't used v7 much. Are there DXL commands that let us count and manipulate Suspect Links? Cannot find any in the Manual help.
Report this to a Moderator Report this to a Moderator
 5-Aug-2004 14:20
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I don't think there are any commands. But I did some investigating and wrote up the following for a colleague.

When you initialize or clear the Suspect Links for a module a new link-attribute is created in the relevant link-modules called "Suspicion Cleared Forwards". This date attribute of the link houses the time the suspicion was cleared or initialized. I am confident that the encrypted layout DXL created by the Analysis wizard compares this value with the changed date of the other object.

A DXL that wants to simply count the number of Suspect Links for an object may look something like the following:

for lnk in obj ->"*" do
{ oOther = object at the other end of the link
if oOther is invalid (deleted, not in a requirement spec, whatever)
continue
datLnkSuspect = dateOf(intOf(lnk."Suspicion Cleared Forwards"))
datObjModified = dateOf(intOf(oOther."Last Modified On"))
if (datLnkSuspect < datObjModified)
then this is a Suspect Link.
}

To avoid program aborts when the link attribute doesn't exist, you may need to use:
datTemp = probeAttr_(lnk, "Suspicion Cleared Forwards") // returns null if the attr doesn't exist
datLinkSuspect = dateOf(intOf(datTemp))

The silly looking "dateOf(intOf(" sequence is to turn a DAY date (04 August 2004) into a SECOND date (08/04/04 14:25:55). On second thought, using integers instead of the two date variables and getting rid of the "dateOf(" would be marginally better.

Notice that you CAN, therefore, set or reset the Suspect Link value with the command:
lnk."Suspicion Cleared Forwards" = today() or "1980 Jan 01". That will require the object's module to be open exclusive, not the link module.

I did NOT investigate any special "Object Text" only issues with Suspect Links. That may involve looking through the History of an object and finding the last history entry that modified Object Text, and extracting
the date from that.

- Louie
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.