![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Tracking requirement changes with Session History Topic Summary: Is there a way to track past volaility of requirements through baselines using HistorySession? Created On: 13-Jun-2006 18:49 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I am trying to write a script that will look at every requirement (defined as Object Text contains "shall" and resids in section 3.2) in a module through all baselines and count the number of changes made in every 30-day window since the Module was created. The catch is that Object history is cleared at each baseline, so I either have to open up each baseline of the module and write code to check when a 30 day window spans more than 1 baseline, or else find a way to use HistorySession information. According to the DXL Reference (DOORS 7.1) I can look at the history of an entire module with a HistorySession object. What seems important to my task is that I can get the actual HistorySession number. So my question is: using the HistorySession number, can I look up all of the objects that were modified during that session number? If so, I could sumply do a "for hs in mod" loop, and then count how many requirement Objects were changed for that session. Since each HistorySession has a date associated with it, then doing this for a 30-day window would be simple! Any tips? Thanks! Jason Edited: 14-Jun-2006 at 16:08 by jason haury |
|
![]() |
|
![]() |
|
No. You need to open all the baselines and examine each to find history.
However, you could read all the HistorySessions and use their 'when' date in order to get more realistic History counts: if a user changed Object Text twice during the same session, then count that as only one 'change' (e.g. User forgot to add a comma the first time). You could also reduce the count by declaring that multiple changes in the same DAY count only as one change; you wouldn't need HistorySession for that. - Louie |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.