![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: % value display at column Topic Summary: Created On: 12-Mar-2007 13:34 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have planned to introduce a column called Progress against each requirement to update the % of progress. I have defined it as real type - but i want that % symbol to be displayed at values.
|
|
![]() |
|
![]() |
|
You could try using layout dxl in the column which should give the desired result.
if (obj."Progress" "" != "") { display obj."Progress" "" "%" } - Martin ------------------------- - Martin |
|
![]() |
|
![]() |
|
If attribute Progress is defined as real with bounds zero and 1.0, then you can display its value in a column like this:
real CurVal = obj."Progress" if (null CurVal) CurVal = 0.0 int DispVal = (CurVal * 100.0) + .5 // Round Up display DispVal "%" Edited: 29-Mar-2007 at 22:22 by Louie Landale |
|
![]() |
|
![]() |
|
Can you really measure progress to 0.1%? If not, it doesn't need to be real; interger would be fine. I would guess that project progress is realistically only measurable to the nearest 10%, in which case an enumeration would work for you and the '%' character can be part of the enumeration value.
|
|
![]() |
|
![]() |
|
Little off-topic from your response: I have been always little bit sceptical of progress measures when taken to individual requirements level. Either a requirement is implemented or not (100% or 0%) - or it has been implemented and tested or not (again 100% or 0%). This way nobody has to guess what is the current progress status for some specific requirement.
Of course on a DOORS module level / project level we might be interested in some progress expressed as a percentage meaning the portion of requirements which have been implemented. ------------------------- Pekka.Makinen@softqa.fi SoftQA Oy -http://www.softqa.fi/ |
|
![]() |
|
![]() |
|
We are currently dealing with requirements allocated to multiple design drawings. Once a requirement is 100% allocated then we figure to have an attribute DXL that polls each of the drawing's QA check boolean attribute, figuring to display a verification % complete for each requirement: if 6 or 18 drawings are QA checked then the requirement is 33% verified.
Yes this is a bit odd, we don't figure to start from each requirement ("portals below main deck have XYZ seals") and insure that it exists in all allocated drawings; we figure to take the list of requiremrents allocated to a drawing and making sure that drawing satisfies all its requirements. The problem with our approach is that we may get an aggregate of "50%" complete on our requirements verification when in fact 90% of the drawings are complete. Not sure that the powers-that-be quite understand that. - Louie |
|
![]() |
Telelogic DOORS
» General Discussion
»
% value display at column
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.