MKS Implementer 2006 Administration Guide

Chapter 2: Understanding Implementer
28
3 Promote the member/object to quality assurance.
Developer or administrator creates the promotion request.
Developer can compile the promotion request into the work library, either as a
separate task or when creating the request.
Administrator moves the members/objects into quality assurance.
4 Quality assurance testing. Tester tests the change for functional consistency and
accuracy.
5 Promote the member/object to Mods production.
Tester copies the original promotion request and changes the target environment (or
environment group) to the Mods environment.
Administrator moves the members/objects into modified production.
Setup Tasks
The setup tasks required for this scenario are as follows:
1 Create an Environment task. Define the following environments:
Base Production, one production environment for the base version of the application.
If all files are in a single library, define that library as the file library for this
environment, as well as for the modified production environment.
Mods Production, one production environment for the modifications of a particular
application. Set up the related environments with modified production above the
base production environment to allow automatic selection of the correct version
during check out. If all files are in a single library, define that library as the file
library for this environment, as well as for the modified production environment.
Quality Assurance, one QA environment for each release of a particular application.
Development environment, one development environment for all developers for each
release, or specific environments per developer or project.
NOTE Related environments are always connected to the modification environment,
never to the base environment.
2 Create a User Profile task. Define user profiles for the following user roles:
Developer checks out members/objects, performs development, creates a promotion
request targeting quality assurance, and is allowed to perform concurrent
development. The developer compiles the promotion request in the work library.
This user only has authority to check out from the modified production
environments and promote to the quality assurance environments being supported.
Tester performs the tests in the test environment with his own copy of the changes.