MKS Implementer 2006 Administration Guide

Chapter 5: MKS Integrity Integration
248
The need for this decision—beyond having control of the overall scope of your conversion
project—is that with co-existence you can designate on a user basis which issue tracking
system a user works with. It allows you to have groups of users still using DesignTracker
while other users use MKS Integrity. This approach is beneficial to larger organizations with
many end users, as it allows you to train and migrate groups of individuals rather than all
users at once. For information on setting the issue management system for a user, see
page 253.
To simplify working with two issue management systems, while co-existence is active you
configure each issue management system to manage a different range of numbers, where
issues and DRs each have a specific number range that is unique to each type, and numbers
outside of the specified ranges are not allowed. DRs always have the lowest numbers and
MKS Integrity issues have the higher numbers.
Everyone is able to view all IDs and some basic information, but the check out and promotion
functions require users to only use the issue management system they are set up for. This
methodology allows DesignTracker to use numbers up to the last allowed DR number you
specify. Information on setting the last DR number begins on page 250.
You achieve a successful conversion when all Implementer user profiles that perform check
out or promotion functions are set to use MKS Integrity for issue management. Although, it
may be desirable to keep a few users with a second user profile set to use DesignTracker so
they can fully navigate the DesignTracker audit trail.
Once the conversion finishes, the DesignTracker transactions can remain online and visible to
the select DesignTracker users for historical purposes. There is no need to disable coexistence
after you finish the conversion.
IMPORTANT MKS recommends you convert to a pilot copy of MKS Integrity to verify
the results before going “live” with converted data. MKS also recommends you
perform a backup of the DesignTracker database by saving the Implementer library
prior to running this conversion program.
Promotion Considerations With Co-existence
The following promotion-related considerations apply to working in the co-existent mode:
All issues for a single promotion request must be in the same issue management system.
In other words, you cannot assign both DRs and issues to the same promotion request.
If using concurrent development, do not allow the same member to have locks
associated with a DR and issue in the same environment, as this will make it non
promotable.
The user that submits a move request must use the same issue management system as
the user who created the request. For example, on a request that contains DRs, both the
requestor and the user submitting the move must be set up to use DesignTracker. On a
request that contains issues, the respective users must be set up to use MKS Integrity.