![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Creating Reports Topic Summary: Reports Created On: 16-May-2007 15:02 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I was ask to create a volativity report on what requirements changed and/or deleted. Anyone have any idea on how to compile that kind of information from DOORS. I've been looking at the History property and exported a lot of info to a word document but it doesn't seem useable.
thanks |
|
![]() |
|
![]() |
|
Search on this forum for term "Metrics" and you will get some scripts.
Edited: 16-May-2007 at 17:00 by ron lewis |
|
![]() |
|
![]() |
|
thanks but I'm so new to doors I'm not sure how to modify scripts but if you give me an example of a report I'll do the hard way, but I need a starting point.
Karen |
|
![]() |
|
![]() |
|
Before you start scripting - check out what standard DOORS can do.
Set-up a filter and save it as a View. Start by setting up a filter using the Last modified attribute after a date you enter as the criteria. Use the compare baseline functionality. To see objects that have been soft deleted, ensure show deletions is enabled from View->Show->Deletions. Check out the Suspect Links functionality. See the DOORS help for more info on this functionality. If you then need a repeatable High Quality report exported from DOORS - have a look at DocExpress/Word ( try v4, not the earlier versions) or WEXP. If your requirement isn't satisfied, then consider coding - see the DXL Manual under history. Some pointers are:- Module m=current Object o=null History h=null for o in m do { for h in o do { print h.author "\t" h.date "\t" h.type "\n" if (h.type == modifyObject) { string oldVal = (string h.oldValue) string newVal = (string h.newValue) print "\tattribute " h.attrName " from '" oldVal "' to '" newVal "'\n" } } } If you want it to export to Word use a Layout DXL column abd use the void display(string) or void displayRich(string) perms - see DXL Manual for further info, as I'm working from memory. The bool Isdeleted(Object) perm may also prove useful. Hopr this is of some help. Regards, Ewen Miller QinetiQ |
|
![]() |
|
![]() |
|
|
|
![]() |
|
![]() |
|
The scripts I pointed to will work if you create attributes in the formal modules.
Beside for the module attributes listed there are also object attributes needed of: "Allocation" "Clarity" Script will run with out any values entered in. "Allocation" & "Clarity" In the Module attributes you will have to initialize the module attributes -- I would suspect you can figure that part out. Also you have to put the xls sheet to whereever you point to in one of the module attributes. The module attributes are listed in the top part of the script -- they are: SFD_DOORS_Report_Path as string, default is C:\DoorsReports\ SFD_METRIC_LastRowUpdated as integer, default is 1. SFD_Metric_LastUpdated as date, default is 1 Jan 1970 also an unlisted module attribute of Customer_Spec_Name other than this -- if I recall the script will work. The hardest part is creating/initializing the attributes Don't know if script provides valid results -- The plot of values may not be initially of value but sheet 1 will have the results that will be plotted. Edited: 17-May-2007 at 15:58 by ron lewis |
|
![]() |
|
![]() |
|
Karen:
There seems to be endless ways to count metrics so I would first define what constitutes a new and deleted requirement within your organization and go from there. ------------------------- pete.kowalski(at)motorola.com |
|
![]() |
|
![]() |
|
thank you for this code. Do you have a simple example of what a violitivity reports looks like. Also, I saved this information to a csv file and what type of analysis do you do on it.
|
|
![]() |
|
![]() |
|
Karen, refer to what Pete Kowalski said in previous message.
The questions you ask would be better directed to the management that requested the report. If you don't know excel -- best bet would be to find an expert on site or get a consultant that do excel wizardly. As an alternative grep does wonders on csv files. |
|
![]() |
|
![]() |
|
that suggestion would make sense normally but we all new to this project and not sure what the format of things should be and that is the reason I am using this forum because I don't have the resources here at my home site......
|
|
![]() |
|
![]() |
|
Based on what you said -- It appears your home site isn't providing adequate support.
However -- you wanted a example of a volatility report. Don't have one since not working that subject at the moment. If you provide your email, I will send you an example of random data entered into SFD_Metrics.XLS which show what was import to that particular program. |
|
![]() |
|
![]() |
|
Karen.Pulliam@L-3Com.com is my email |
|
![]() |
|
![]() |
|
I suggest that you need to count requirements rather than objects, and also need the total number of requirements.
Reasons:- Usually the metric of interest is usually how stable the project is. The more requirements changing the less stable and hence greater risk.
Objects will include explanations and supporting data, which indicate a figure for DOORS useage.
I'd suggest :-
The report (from excel) includes a chart of the numbers so you can see the change.
Keep it simple, you should be able to produce the whole thing in less than 1/2 hour.
Get the managers to define what they intend to use it for, then you can provide useful information. If they don't know you should save the project time and effort by not producing it.
(Apologies if any of that is teaching you to suck eggs.)
|
|
![]() |
Telelogic DOORS
» General Discussion
»
Creating Reports
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.