MKS Implementer 2006 Administration Guide

Chapter 2: Understanding Implementer
20
2 Develop and test. Developer codes, compiles, and tests programs.
3 Promote to test. Developer creates the promotion request.
Developer can compile the promotion request into the work library, 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 to test.
Tester creates the request for promotion by copying the original promotion request.
Administrator moves the members/objects into user acceptance testing.
6 User acceptance testing. End users test the change for functional consistency and
accuracy.
7 Promote to production.
Authorized user creates the request for promotion by copying the original
promotion request.
Administrator moves the members/objects into production.
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, the first QA environment.
User Acceptance testing, the second 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:
Developer checks out members/objects, performs development, and creates a
promotion request that targets quality assurance environments. Additionally
compiles the promotion request in the work library.
Tester performs the test in this 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.