![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Providing traceability to <.pdf> documents Topic Summary: Created On: 12-Dec-2006 19:26 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi all, 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.pdfSo 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. |
|
![]() |
|
![]() |
|
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 |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.