MKS Implementer 2006 Administration Guide

Appendix C: Converting DesignTracker Data to MKS Integrity
436
Conversion Considerations
DRs that are currently linked to SRs in DesignTracker will not have a relationship
automatically added between the new issues in MKS Integrity—this requires a manual
change. In addition, because the following data (if used) is not applicable to MKS Integrity, it
does not convert:
DR and SR approval related information
process control information, for example, field display and validation controls, and
Implementer state controls
release management information
ProjectMaster information
SupportCenter attached calls
Organizational Activities
The organizational activities required to perform the data conversion include the following:
1 Pilot the integration.
a) In Implementer, run the system conversion that allows DesignTracker and
MKS Integrity to co-exist.
b) Configure MKS Integrity, which includes:
Types, workflow, fields, and field values. The workflow must allow any state
transition to any other state. In addition, no mandatory fields can be specified
in the workflow. The fields cannot have editability rules; remove any existing
editability rules. You can modify this open workflow to be more restrictive
once the conversion has finished.
Enroll users.
c) Configure Implementer to use MKS Integrity.
d) Map your existing data to MKS Integrity by completing the conversion properties
file.
e) Run the Convert DT to MKS Integrity (ICVTDT) command to convert a sampling of
DRs (for testing purposes, these DRs can be copied from other DRs).
f) Verify the setup by using the Implementer and MKS Integrity functions to check out
and promote back to production.
g) Document all Implementer and MKS Integrity set up steps.
h) Apply the set up changes to the production copies if piloting the conversion in
separate installations.