![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Gettin AttrDef info (not value of Attribute) without opening a Module Topic Summary: What's the fastest way to get a list of Attributes (Object Attributes) within a Module Created On: 28-Jan-2008 19:00 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi All,
I've seen several threads about people wanting to get the value of an Attribute without opening the Module, and it seems doing that is a lost cause. But what if all I need is a list of attributes? It seems like this info could be found without loading the module since there's no need to harvest any values, say, obj."Test Status"...all I want to know is if the Module contains an Object-level attribute called "Test Status". Is this doable? At the moment, I have a GUI which creates a choice DBE showing all the attributes of a certain type from a specified Module. To do this, i have to read( ,false) the module so that I can then use the "for ad in mod do" loop. This can be time consuming since some modules are rather larget, so I was hoping there might be a faster way. Or at the very least, is there a way of using the exists() function to simply see if a attribute exists within a certain Module, but without opening (read() or load()) the Module? (i.e. use ModName_ or something) Any ideas? jason |
|
![]() |
|
![]() |
|
In DOORS 8.3 you can.
If you have 8.3, search for ModuleProperties in the DXL Reference manual. ModuleProperties is a new data type and consists of type definitions, attribute definitions and module attribute values. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Here's a sample script of how you can pull the attribute name and print the value of module attributes....
------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Thanks for the replies. We're still in the 8.1 days, so I guess I'll wait until we evolve to 8.3 and reimplement things then. Thanks again!
|
|
![]() |
|
![]() |
|
Aye,
We're still using 8.1, but I've been doing the evaluation of 8.3. I have at least one script that is waiting for our upgrade to 8.3 before I deploy it, because it relies on this very topic to run..... ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
The moduleProperties type is available in DOORS 8.2, but it didn't make it into the documentation!
The attached code was my first investigation into using the new type and demonstrates what you can do with it. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Didn't realize it was in 8.2 as well.
------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Hi, I'm trying to set up a Metrics collector on the number of times a requirement is modified. The easiest way seems to increment a count every time the Modification Date changes.
Which should be an easy DXL script that I could run nightly. But which DXL script is there out there that I could use, or modify. It would first have to compare between creation and Modification date. That's 1, then increment the count every time the mode date changes. Or we could just initialize the count to 1. and forget about the first change. Then I'd have to have the count for the whole module. Any ideas? I'm going to the DXl class in March but don't have that yet. ------------------------- He who would swap his freedom for the promise of security deserves neither. |
|
![]() |
|
![]() |
|
It sounds like you want to collect "volatility metrics". The catch is that the Attribute "Last Modified On" may change because a person altered another attribute. Let's say you really want to track if only "Object Text" or your own Attribute, say "IsRqmt" has changed in the past week. In this case, you'll have to have a script which rolls through the history of each object over the last week looking for Object Text or IsRqmt being changed.
Another catch is when the Module gets baselined, youll be off for a week since history info is reset at each baseline.. hope this helps! Jason |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.