MKS Implementer 2006 Administration Guide

Implementer and MKS Integrity Integration
The following illustrates how the integration between Implementer and MKS Integrity
works:
1 You create an issue in MKS Integrity. For example, the issue requests a bug fix for a
software installation problem.
2 The developer performs a check out within Implementer that automatically creates an
Implementer change package. Likewise, developers can automatically create a change
package from the Workbench, by assigning an issue to a lock in the Lock Detail panel, or
by assigning an additional issue in the Multiple Issues panel. The change package is
assigned an ID and is in an open state.
3 Once the changes or additions necessary to satisfy the issue are complete, the developer
promotes the members.
4 The issue moves to the state in the workflow defined for the environment. For example,
the issue is moved from the Test state to the QA1 state.
Sample Workflow
You can define this feature to any MKS Integrity state that is defined within the environment
workflow. For the purpose of this document however, the setup steps and examples illustrate
the generation of Implementer requests when an issue reaches a state of “Ready for QA”,
based on the following workflow:
Submitted
In Development
work is in progress
work is in initial unit test state
Ready for QA (manually set)
work has passed initial unit test and is considered ready for promotion into QA
environments
an MKS Integrity user manually sets an issue to this state when the corresponding
objects have passed initial unit testing and are ready for promotion to QA
environments
In QA1
objects have successfully promoted into the first set of QA environments
Promoting Implementer Requests From MKS Integrity
You can create and submit promotion requests from within Implementer or from within
MKS Integrity. When promotion activities are performed from Implementer, it is standard
Implementer promotion processing.
201