So I have a user(s) wanting a spreadsheet of information. I've made a lot of headway but need some brain power help. The information is to be broken down into months, be specific to a module, and will consist of counts of 1) All requirements in module for that month, 2) All modify actions on requirements for that month, 3) All deletions of requirements for that month, and 4) All additions of new requirements for that month.
Most of this I can get from module history (I think) by looping through and keying off types like modifyObject, deleteObject, addObject and using the associated absno to look up objects. So what I'm thinking (by running test programs to help my understanding, and with much hellp from our DOORS community) is that to accurately count objects that are requirements for any given month in the life of an object I'll have to start with the oldest baseline and start a running sum sort of thing for requirements counts. Someone please point me to a more graceful solution?
Also noticed that some history records (e.g. a purgeObject type) have absno of -1. What does -1 signify? Is there anyway to extract the object number that was actually purged? I'm thinking if an object (that happened to be a requirement) gets purged it introduces an unfixable broke. Is there a way to 'read' information about purged objects from History records?
Hopefully at least some of this makes sense. Any help/constructive comments are, as always, greatly appreciated.