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: Converting layoiut DXL column to DXL attribute
Topic Summary:
Created On: 9-Jul-2003 19:51
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.
 9-Jul-2003 19:51
User is offline View Users Profile Print this message


Ahsan Syed

Posts: 5
Joined: 18-Sep-2002

Hi,

I want to know your thoughts on the idea of converting the layout DXL columns to DXL attributes for improving performance.

The reason being that the traceability views for our module are extremely slow and becoming almost useless. Any one faced similar issues and how did you handle it?

Thanks in advance

Edited: 9-Jul-2003 at 19:53 by Ahsan Syed
Report this to a Moderator Report this to a Moderator
 10-Jul-2003 02:46
User is offline View Users Profile Print this message


Paul Miller

Posts: 376
Joined: 2-Oct-2002

Hi Ahsan,

Just a word of caution about any perceived performance enhancements by converting to DXL Attribute. The beauty of DXL layout is that it is offering information in almost real-time ie: every time you perform an action that requires the screen to be refreshed (ie edit, scroll, select another view, whatever), the DXL layout scripts also refresh and display the latest info.

DXL attribute is a one shot version of DXL Layout, ie: it refeshes only once when a module is opened and from there on you have to manually refresh via the Tools>Refresh DXL Layout function. Also, because it's an attribute, the displayed information is also being stored and this has to be retrieved and displayed which has an impact on performance. If you do use DXL Attribute, I would recommend that you deselect all of the attribute behavioural properties ie: "Inherit, "Affect Change Bars", "Affect Change Dates" and particularly "Generate History". If "Generate History" is selected and the data that a DXL Attribute script is displaying is changing a lot, the module history file is going to get very large and you'll find that the module will take longer and longer to open between baselines.

So it's bit of a trade-off, you're DXL layout scripts maybe slow but going to DXL Attribute could introduce other performance or nuisance related problems.




-------------------------
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
Report this to a Moderator Report this to a Moderator
 10-Jul-2003 15:30
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

I use DXL attributes a lot, for exactly the same reason. Screen refresh is extremely slow when you are displaying several depths of trace from a large module.

Paul is right to point out the trade-offs with this approach, but if you make sure that history etc is all swithed off there should be no problems.


-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 19-Sep-2003 22:23
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

On a side note, you can have ONE DXL that can work in either Layout or Attribute mode. The body calculates the string Results, then calls the attached function "fShowResultsDXL", which is sensitive to whether its a Layout or AttrDXL.

Recall that AttrDXL gets recalculated [1] when you open the module [2] on "Refresh" demand [3] when the result is null and you modify the display (just like Layout). The "default AttrDXL" variable in the function is typically set to a space " " to prevent constant recalculation.

- Louie
Report this to a Moderator Report this to a Moderator
 17-Dec-2003 04:02
User is offline View Users Profile Print this message


Bob Sherman

Posts: 6
Joined: 22-Oct-2002

My users emphatically agree that traceviews in latest versions (6/7) are disfunctionally slow. So, we too have been thinking about creating an utility to automate the building DXL attributes. Have you created or found anything yet?
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.