MKS Implementer 2006 Administration Guide

Chapter 2: Understanding Implementer
18
2 Create a User Profile task. Define user profiles for the following user roles:
Developer, checks out members/objects, performs development, and creates a
promotion request that targets production. Additionally compiles the promotion
request to the work library.
Administrator or project leader, creates projects and moves the promotion request to
production.
One Test Environment: Scenario 2
Overview
Each developer checks out to a personal library, a project library, or a shared development
library. The developer promotes to a quality assurance environment. Testers test in this
environment and then promote 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.
2 Develop and test. Developer codes, compiles, and tests programs.
3 Promote to test. Developer creates the promotion request.
Developer compiles the promotion request into the work library, as a separate task
or when creating the request.
Authorized user moves the members/objects into quality assurance.
4 Quality assurance testing. Tester tests the change for functional consistency and
accuracy.
5 Promote to production.
Tester creates the promotion request.
The promotion request can be compiled into the work library, as a separate task or
when creating the request.
Administrator moves the members/objects into production.