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: Providing traceability to <.pdf> documents
Topic Summary:
Created On: 12-Dec-2006 19:26
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.
 12-Dec-2006 19:26
User is offline View Users Profile Print this message


Wayne Wawrzyniak

Posts: 1
Joined: 10-Dec-2004

Hi all,

Would appreciate any information...

Here is some information so everyone gets a feeling for what I am doing. I am using Telelogic's DOORS 7.1 Requirements Management software.

Unfortunately, I have found that the DOORS software does not have Adobe <.pdf> import capability, so Telelogic changed my support case into possible "Product Enhancement"...

Below is a link to a Telelogic User Group presentation on the conversion of documents, and what was actually done to be able to provide traceability to requirements by bookmarking to an external Adobe file. It makes for very interesting reading. Basically, a <.dxl> (proprietary Telelogic scripting code) was created to allow for OLE linking to Microsoft file formats, and the "Pole Presentation" states the problem, and what was done to change the <.dxl> scripting around to provide for traceability by bookmarking and linking to Adobe files. If you read it carefully, you will fully understand my plight. You'd figure that a product enhancement would be done a long time ago to allow for the native Acrobat file format due to the popularity of the software, but be it for difficulty or legal (who knows), it was never accomplished. Here is a link to that document import discussion http://www.prod.sandia.gov/cgi-bin/techlib/access-control.pl/2002/022237.pdf

So that's where I'm at. If I can get my hands on the <.dxl> script that was created, I can provide traceability to my requirements using external link bookmarking to Adobe files. But if I need to actually get the <.pdf> document into the DOORS database, then I need to convert it using Adobe Acrobat Pro and clean it up so it imports to DOORS automatically. And for automatic import, a lot of times carriage returns, extraneous line feeds, etc. have to be taken out of the MS Word document so it goes into the DOORS database "paragraph to object". That is a brutal process in itself, which is tedious and time consuming, and it even gets worse if I have to OCR scanned <.pdf> or image documents, and then convert. That OCR process is really brutal.

I just wanted to give you an overview of what I am trying to accomplish. I appreciate everyone's help in advance.

Thanks,
- Wayne (USCG)

Report this to a Moderator Report this to a Moderator
 4-Jan-2007 16:11
User is offline View Users Profile Print this message


ron lewis

Posts: 650
Joined: 20-Sep-2004

You could get a printer driver that sends output to graphic files.

Then create a word document that contains each graphic.

Then export word document to DOORS.

Edited: 5-Jan-2007 at 12:13 by ron lewis
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.