I have created two formal modules in doors and created some links. In my first module the requirements are in table. when i link the requirements from table i am not able to do the traceability using Analysis Wizard . Could anyone help me on this issue please.
SudarshanRao 270001WGJU33 Posts
Re: Doors Table In and out Links2013-11-19T08:20:08ZThis is the accepted answer. This is the accepted answer.
Tables cannot have columns like other non-table objects to show any attributes/DXL Columns. So you can't really show the traceability column for table cells. So you could consider showing traceability column in the other end of the link, I hope that's not a table too...
llandale 270001QM9N648 Posts
Re: Doors Table In and out Links2013-11-19T18:38:17ZThis is the accepted answer. This is the accepted answer.
- SudarshanRao 270001WGJU
Yes. But you can create a layout ..err.. no, an attrDXL to display the linked information. You can then create a new view and command that the Attr-DXL be the default display attribute for the table. So you would not see the normal "Object Text" requirement but rather the information in the attr-DXL. Seems to me such an odd attr-DXL might was well display the local Object Text and the away linked object info, then you get your cake and eat it too; until you figure out displaying all that info in the narrow table cells is hopeless.
Such an attr-DXL will probably need to be sensitive to whether the object is in a cell:
- if (cell(obj)) //
- then it is a table cell
- else it is a normal object
There are a couple other options vis-a-vis these "default table attributes" but I've actually never used any of them.
DOORS tables byte.
Digressing, something I'm very good at: Add a new column after each real column and delete the new column. Create an attr-DXL that displays local Object Text if the object is undeleted, but when the object is deleted then it displays the away linked information of the "previous" undeleted requirement. Then you can toggle your link information by viewing deleted objects. Not "VooDoo" but indeed "DooDoo"!