![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Exporting/Importing from Word to DOORS Topic Summary: Exporting/Importing from Word to DOORS Created On: 3-Apr-2006 15:14 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We are looking for a way to implement an update to a module of existing requirements when exporting/importing from MSWord to DOORS. |
|
![]() |
|
![]() |
|
This is a very common requirement and one that Telelogic have yet to address.
I have implemented an "Update from Word" utility, but I am not at liberty to post it because it is owned by my employer. I can however tell you the steps required to do it. My approach was as follows: 1. A menu option runs some DXL to launch Word and run the "Export to DOORS" macro. The word document gets imported into a scratch module. 2. Use DXL to compare your existing module with the scratch module containing the updates. I used some DXL wrapped around the module compare utility shipped with DOORS which links matched objects together. 3. Review the differences between the modules using red-lined markup in a layout DXL column. 4. A little more DXL and another attributre allow you to accept or reject each change. 5. Then copy the changes across to update the module. This method required quite a bit of DXL to implement, so it is only worth doing if updating from Word is going to be a regular occurrence. Comparing the two modules is tricky because you cannot use object identifiers and you need to do string comparisons. Also, the compare function gets very confused if there are a lot of differences between the modules. Sorry I cannot be of more help. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
To date my solution (also not optimal) has been to identify the changes in word, and then manually enter the changes.
a) if they are just typo's then edit the text directly
b) if it is a requirement change/ or new text, then paste in the new text. (whether you change the requirement id is down to your local procedures)
c) If there are large sections of new text, put the new stuff in its own document, and export-Append it to the module, and move it about in DOORS to the correct place.
|
|
![]() |
|
![]() |
|
The built in 'compare modules' wizard will do part of this for you.
Import the new version into a clean module. Run the wizard from the newer module. This will give you redline markup and then you need to either manually make the changes, or write some dxl. As Tony says, the amount of effort you want to spend on dxl depends how often you are going to do this. Hazel |
|
![]() |
Telelogic DOORS
» General Discussion
»
Exporting/Importing from Word to DOORS
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.