![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Req IDs in Software Code Topic Summary: Created On: 4-Mar-2005 11:31 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Hi, We have been entertaining the idea of getting sw programmers to add the Doors Req IDs into their C code (or VHDL code) where most applicable. Is someone else doing something like this as well ? Also, assuming the do add the ID in the code, then it should be possible to select an object and start a DXL that will search through a selectable folder, for all *.c and *.h files that contain the specific ID. The DXL may even spawn the relevant software editor of choise and use its find in files function. The idea of this would obviously be to have tracability to code level and automate the process. Has anyone done something like this or are there easier ways to do this ? Maybe someone have such a DXL that do approx. this ? Thanks very much. Samuel Cronje | |
![]() |
|
Hi,
We have been entertaining the idea of getting sw programmers to add the Doors Req IDs into their C code (or VHDL code) where most applicable. Is someone else doing something like this as well ? Also, assuming the do add the ID in the code, then it should be possible to select an object and start a DXL that will search through a selectable folder, for all *.c and *.h files that contain the specific ID. The DXL may even spawn the relevant software editor of choise and use its find in files function. The idea of this would obviously be to have tracability to code level and automate the process. Has anyone done something like this or are there easier ways to do this ? Maybe someone have such a DXL that do approx. this ? Thanks very much. Samuel Cronje ------------------------- Samuel Cronje EW Systems Engineer Grintek Avitronics Centurion South Africa |
|
![]() |
|
![]() |
|
I would advise against relying on people to manually type an identifier.
My approach for this entails creating a surrogate module in doors to represent the source code. I have only used this for DXL scripts so far. I have a script that recursively scans the source code windows folder and creates objects in a doors module representing each folder and file found. Updates are automatic by running script again. I also extract function prototypes, version information, #includes and some metrics (e.g. SLOC) etc from the files. This gives me the ability to collate metrics, analyse dependencies etc all from inside doors. Once the hierarchy of source code has been built inside doors, you can do your tracing from there. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Req IDs in Software Code
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.