MKS Implementer 2006 Administration Guide

Setup Tasks
The setup tasks required for this scenario are as follows:
1 Create an Environment task. Define the following environments:
Production, one production environment.
Quality Assurance, one QA environment.
Development, one development environment for all developers, or specific
environments per developer or project.
2 Create a User Profile task. Define user profiles for the following user roles:
Host System Scenarios
Developer checks out members/objects, performs development, and creates a
promotion request that targets quality assurance environments. The developer
compiles the promotion request in the work library.
Tester performs the tests in the test environment with their own copy of the changes.
Administrator promotes changes into the QA environment to allow the tester to start
testing a change.
Administrator or project leader creates projects and moves the promotion request to
production.
Multiple Test Environments: Scenario 3
Overview
Each developer checks out to a personal library, a project library, or a shared development
library. The developer completes the necessary changes and checks in to a quality assurance
environment. The testers in this environment perform the necessary testing, and then
promote from quality assurance to another test environment for user acceptance. This is
accomplished by copying the request that initially promoted the changes into the quality
assurance environment. After user acceptance testing, you promote the change to
production.
Development Tasks
This is the typical task sequence from the start of a programming change to completion.
1 Check out. Developer checks out to a personal library, project library, or shared
development library.
19