![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Doors Tables Traceability Topic Summary: Traceability Created On: 20-Feb-2007 12:37 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Re Hazel Woodcock's response. "It's probably not a very helpful comment at this stage, but you have found one of the reasons why using tables is a bad idea. " As a message to the originator of this thread, please don't look upon this as a deficiency of the DOORS tool - tables have always been a nightmare for specifications whether you're using DOORS or just MS Word. Presenting traceability is only one of many problems. Having said that - DOORS does at least allow you to choose which object attibutes you can see in the table cells - with a bit of DXL wizadry this can be exploited. The default attribute being displayed is the cells Object Text attribute. My suggestion would be to run the Analysis Wizard to generate a layout DXL trace column, convert this layout DXL column to an attribute DXL (Use Tools > Support Tools > Convert Layout DXL to Attribute DXL ), then make this attribute DXL visible in the table cells. By modifying the code in the attribute DXL, you can display other data as well such as the current Object Text of the cell, current verification method, whatever. Just remember that you will need to refresh the module for the attribute DXL to update (Press F5). So through one attribute DXL, you can get it to grab information from links and other attributes and display this all together within each cell. The only hitch is how well\nice this will look in a table cell, so a bit of thought about formatting of the displayed info will be needed. | |
![]() |
|
![]() I've been working with VM's from tables to Objects for two or three weeks. I'm having problems creating traceability. i follow all the instructions in the manual, i read a lot of the forum messages, but no of those answer my problem. I need to create a Traceablility Column for tables, not objects, tables. |
|
![]() |
|
![]() |
|
If you want to link to a table and show resulting link to table:
Select View->Show->Table Cells to uncheck the Table Cells Resulting view will show >>Table which will let you see column associated with that row entry and create a link. |
|
![]() |
|
![]() |
|
Thanks for the tip, but that's not what I'm looking for. I'm trying to create an out-link column traceability, to verify that every link in every cell of the table that i created is directed to the corret object. This table has aproximitly 2500 links and it's harder to go one by one, that just check them in the out-link column. Nothing work to trace, not the wizard, not the trace, not anything. i've been working with DOORS only one month and i can't find another tool to make this possible.
Thanks any way. |
|
![]() |
|
![]() |
|
You have to write a script and output information -- possible in a csv file for post processing in excel.
|
|
![]() |
|
![]() |
|
It's probably not a very helpful comment at this stage, but you have found one of the reasons why using tables is a bad idea.
If you have the option, my suggestion would be to convert the table into something else. Do you really want links to every cell? Is a row the thing you are trying to reference? My suggestions are (depending on your table) -Use embedded OLE objects -Convert to a hierarchy -Convert to attributes I think the pain will only get worse if you persist with tables, what you are trying to do is view a third dimension. If you must keep the table then how about creating a dxl attribute with the information you need and display that in the table cell. That allows you to do the checking you want to. Hazel |
|
![]() |
|
![]() |
|
Hazel:
Thanks for your recomendations. I had the tables in OLE and i had to convert them into Doors tables. This link is of Verification Matrix purposes. what i want to do is make my life more easier, thing that it's not happenning right now, but i will appreciate, as i'm new in this DOORS, i don't have, right now enough capabilities to create a script in DXL if you can post a script that can guide me into this journey. What i know about DXL is only the basics. Thanks. |
|
![]() |
|
![]() |
|
Re Hazel Woodcock's response.
"It's probably not a very helpful comment at this stage, but you have found one of the reasons why using tables is a bad idea. " As a message to the originator of this thread, please don't look upon this as a deficiency of the DOORS tool - tables have always been a nightmare for specifications whether you're using DOORS or just MS Word. Presenting traceability is only one of many problems. Having said that - DOORS does at least allow you to choose which object attibutes you can see in the table cells - with a bit of DXL wizadry this can be exploited. The default attribute being displayed is the cells Object Text attribute. My suggestion would be to run the Analysis Wizard to generate a layout DXL trace column, convert this layout DXL column to an attribute DXL (Use Tools > Support Tools > Convert Layout DXL to Attribute DXL ), then make this attribute DXL visible in the table cells. By modifying the code in the attribute DXL, you can display other data as well such as the current Object Text of the cell, current verification method, whatever. Just remember that you will need to refresh the module for the attribute DXL to update (Press F5). So through one attribute DXL, you can get it to grab information from links and other attributes and display this all together within each cell. The only hitch is how well\nice this will look in a table cell, so a bit of thought about formatting of the displayed info will be needed. ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
Mr. Miller:
You really answer my extreme doubt about Tracing tables. I'm not really sure if i'm going to make it, 'cause of my basic knowledge about DXL, but you really make my day. Thanks A LOT. |
|
![]() |
|
![]() |
|
I ended up writing my own traceability and impact analysis tools in dxl to handle this problem. They are not as robust as the DOORS solution - they only go one level through links - but I am able to deal with DOORS type tables.
|
|
![]() |
|
![]() |
|
Can you share the look of your tables with that script?
Can you share the script? I really need something like that to trace more than 3 thousand links. I already know the where each link go, but i need to make sure that there correct and i dont want to go one by one clicking the link. Thanks |
|
![]() |
Telelogic DOORS
» General Discussion
»
Doors Tables Traceability
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.