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: Including tables in filters
Topic Summary:
Created On: 14-Oct-2003 04:20
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.
 14-Oct-2003 04:20
User is offline View Users Profile Print this message


Geoff Wilson

Posts: 9
Joined: 23-Jan-2003

We tend to do a lot of deltas against existing software, as such, much of our requirement tracking is per "item". This is modelled in DOORS as a level 1 heading and all children. This works fine in most cases, except that we have been unable to define an appropriate filter to capture all the children of the parent object in so much as tables are not included.

Is there a "nice" way of telling DOORS to include the current object, and all children including only the tables which are children of the current tree?

At the moment, we've been using "Include Current Object" along with "Show Decendants". Which gets everything except tables. It seems rather silly to have to write a DXL filter to do this ...

Note that unchecking "Hide non-matching table cells" simply gets all of the tables in the current module, which really doesn't help.

Thanks in advance,

Geoff
Report this to a Moderator Report this to a Moderator
 14-Oct-2003 17:04
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I don't know how to define a pure filter such as you described.

The follow code could be put in its own DXL script "ShowSubordinateTables" and may form the beginning of a (clumsy) solution. Run your filter, then manually ShowSubordinateTables to ADD certain tables.

The script assumes that a table is "subordinate" to that non-table object that immediately "preceeds" it; it has nothing to do with "levels". So your specs need tables preceeded by "shall be as the following table" statements.

To test the script be sure to have various display options set, such as filtering (of course), but also sorting. I suspect you'll find it only works when the other display settings are off.

- Louie
Report this to a Moderator Report this to a Moderator
 15-Oct-2003 13:13
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

Another approach. The following code gives you a filter including all the objects that are descendents of the current object, including tables. The problem is, you cannot save this as a view.



-------------------------
Tony Goodman
http://www.smartdxl.com
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.