Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Req IDs in Software Code
Topic Summary:
Created On: 4-Mar-2005 11:31
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Samuel Cronje, on Friday, March 11, 2005 4:49 PM

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
 4-Mar-2005 11:31
User is offline View Users Profile Print this message


Samuel Cronje

Posts: 7
Joined: 19-Nov-2003

Answer 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

-------------------------
Samuel Cronje
EW Systems Engineer
Grintek Avitronics
Centurion
South Africa
Report this to a Moderator Report this to a Moderator
 4-Mar-2005 13:21
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

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
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 0 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 0 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.