Appendix A

Installing DataHub for MagicRQ Users

If you have installed a MagicRQ version that is earlier than 16.6, except 16.0 sp1 and greater, you need to first
remove it from (i) MagicDraw and (ii) DOORS prior to installing DataHub by following the instructions right below.
(i) To remove MagicRQ Plugin from MagicDraw:
1. 1

1. 2
1. 3

Open MagicDraw.

Click Help > Resource/Plugin Manager.

Select MagicRQ and click the Remove button.

(ii) To remove MagicRQ Plugin from DOORS:

1. 4
Remove the DOORS\lib\dxl\config\formalPopupFiles\magicrq.dxl and
DOORS\lib\dxl\addins\MagicRQ files.
If MagicRQ 16.6 or one of its earlier versions has already been
installed, DataHub will remove it while installing DataHub Plugin.

NOTE:

Once it has been removed, you can follow the installation instructions in section 1.4.1 Installing Cameo
DataHub to install DataHub.

Migrating Relations for MagicRQ User

You can migrate previous MagicRQ relations to the current version of DataHub (this feature is only available in
MagicDraw). You can also migrate DataHub relations from an earlier version of DataHub (versions 2.0 - 4.0 or
versions 4.1 - 17.0.5) to DataHub 18.1 (see section 3.3.2 ).
To migrate relations from MagicRQ:

1.5 Click Tools > Requirements > DataHub > Migrate.... The Cameo DataHub Migration dialog will
open (ameo DataHub Migration Dialog).

1.6

1. 7

Cameo DataHub Migration Dialog

Click the ... button to select a MagicRQ XML file.

1. 8
Click Next to review the migration details, and then click Finish to start
migrating the MagicRQ relations to DataHub 18.0.

1.9
Migration

From MagicRQ 2.0 to DataHub

Migration Rules
Rules

The MagicRQ hyperlinks between requirements and

elements will become Trace. Before migrating relations
you need to:
1. 10 open each participating tool.
1. 11 start the Drivers and Data Source of each
participating project so that they are ready to use (see
section 3.3.3.2 Managing Drivers and Data Sources
above).

From MagicRQ 14.0 and

greater to DataHub

1. 12 Non-Sync Associations will become Trace.

1. 13 Non-Sync Associations with Suspect status
will become Trace with Suspect status.
1. 14 Orphan status cannot be migrated.
1. 15 Sync Associations will change to Data Sync
Manual.
1. 16 Sync Associations with Suspect status will
change to Data Sync Manual with Synchronized
status.
1. 17 Orphan status cannot be migrated.