02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Setup Tasks<br />

The setup tasks required for this scenario are as follows:<br />

Host System Scenarios<br />

1 Create an Environment task. Define the following environments for Release 2.0:<br />

Production 2.0, one production environment for release 2.0 of a particular<br />

application. Define related environments and place production 2.0 above<br />

production 1.0 to allow the automatic selection of the correct version during check<br />

out.<br />

Quality Assurance 2.0, one QA environment for release 2.0 of a particular application.<br />

Development environment 2.0, one development environment for all developers for<br />

each release, or specific environments per developer or project.<br />

Define the following environments for Release 1.0:<br />

Production 1.0, one production environment for release 1.0 of a particular<br />

application.<br />

Quality Assurance 1.0, one QA environment for release 1.0 of a particular application.<br />

Development environment 1.0, one development environment for all developers for<br />

each release, or specific environments per developer or project.<br />

2 Create a User Profile task.<br />

Define user profiles for the following user roles for Release 2.0.<br />

Developer 2.0 checks out members/objects, performs development, creates a<br />

promotion request targeting release 2.0 quality assurance, and is allowed to perform<br />

concurrent development. The developer compiles the promotion request in the<br />

work library. This user only has authority to check out or promote to the most<br />

current release supported.<br />

Tester 2.0 performs the tests in the test environment with their own copy of the<br />

changes.<br />

Administrator 2.0 promotes changes into the test environment to allow the tester to<br />

start testing a change.<br />

Administrator 2.0 creates projects and moves the promotion request to release 2.0<br />

production. This user also has conflict resolution capabilities.<br />

Define user profiles for the following user roles for Release 1.0.<br />

Developer 1.0 checks out members/objects, performs development, creates a<br />

promotion request targeting release 1.0 quality assurance, and is allowed to perform<br />

concurrent development. The developer compiles the promotion request in the<br />

work library. This user only has authority to check out or promote to releases other<br />

than the new one in development.<br />

31

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!