MKS Implementer 2006 Administration Guide

Chapter 5: MKS Integrity Integration
Process and Workflow
260
Managers have a graphical window into the development process, allowing them to monitor
the progress of issues and changes. The resolution of issues is accomplished through an
integrated change management process facilitated by a common software architecture shared
between MKS products.
At the core of the integration, Implementer’s release control features have a direct correlation
to change management functions in MKS Source as described in the following table.
This release control feature in Implementer... ... Correlates to this feature in MKS Source
product subproject of base product project
product/version development path
product/version/environment subproject of base environment project
product/version/release release checkpoint
The integration uses two MKS Source projects, defined as a base product project and a base
environment project, to store all Implementer source archive information.
Product Subproject in Base Product Project
A product subproject is automatically created in the MKS Source base product project
for each product when you set the Archived by MKS Source field to Y in Implementer’s
Product Maintenance panel. Product subprojects are located in the Base Product project
you reference in the MKS Source Setup panel in Implementer.
Permissions for each product subproject are inherited from the base product project.
All source members associated with the Implementer product are stored in the product’s
subproject. When you add or update a member, it is added or checked in to this
subproject. The product subproject contains all versioned contents for all members
checked in for the product, including members that are later dropped. Users should not
be given visibility to the product subproject; they can view the contents through
environment subprojects within the product’s versions.
Before creating a new version of the product in Implementer, you redefine the current
version with a development path of *VERSION. A function in Implementer allows you
to create an MKS Source development path, which assigns branched MKS Source
revisions to subsequent promotions into the archived product/version/environments.
This allows you to create a new version with a development path of *HEADREV, and
continue with promotions to the *HEADREV version assigned trunk revisions.
IMPORTANT The base projects referenced in this document are standard MKS Source
projects. They act as parent projects to various subprojects. It is not required to
register the base projects as top level projects in MKS Source.