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 with a standard path.
Quality Assurance, the first QA environment.
Host System Scenarios
Development environment, 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:
Developer checks out members/objects, performs development, creates a promotion
request that targets production, and is allowed to perform concurrent development.
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. This user also has conflict resolution capabilities.
Emergency Development: Scenario 5
Overview
This scenario allows checking out multiple versions of one member. The second check out is
for emergency purposes.
The first developer checks out to a personal library, a project library, or a shared
development library. The second developer checks out to a personal library, a project library,
or a shared development library by selecting from an existing version. To do this, the
23