MKS Implementer 2006 Administration Guide

Chapter 2: Understanding Implementer
32
Tester 1.0 performs the tests in the test environment with their own copy of the
changes.
Administrator 1.0 promotes changes into the test environment to allow the tester to
start testing a change.
Administrator 1.0 creates projects and moves the promotion request to release 1.0
production. This user also has conflict resolution capabilities.
Differences Between Delta and Non Delta Variations
The previous tasks described how to set up a delta scenario, where the new release library
contains only the objects that are different from the original release. You can also set up for
multiple releases using a non delta scenario, where both libraries contain the entire
application.
TIP The delta scenario is recommended when disk space is an overriding concern
and you have limited changes. The non delta scenario, which is easy to use, is
recommended when disk space is not a consideration and when frequent changes
are made to the database.
The following table describes the differences in setting up delta and non delta scenarios.
Delta Scenario Non Delta Scenario
Description Release 2.0 library contains only
objects that are different from
release 1.0. If some changed
programs use additional files, those
files may also need to be copied.
Release 2.0 and release 1.0 both
contain the entire application.
Related environments Requires set up. Does not require set up.
Related objects Requires set up. Does not require set up.
Library lists Requires release 1.0 libraries in
release 2.0 library list.
Should not have release 1.0
libraries in release 2.0 library list.