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.

Chapter 2: Understanding <strong>Implementer</strong><br />

30<br />

Changes to Release 2.0<br />

1 Check out the member/object from Production 2.0 environment. Developer for release<br />

2.0 selects the member/object from a list of all items in release 2.0 production and/or<br />

release 1.0 production. Check out automatically determines to copy the version from<br />

release 2.0 or release 1.0 production for new development.<br />

2 Develop and test Release 2.0. Developer begins the programming changes and tests the<br />

member/object in his development environment for release 2.0.<br />

3 Promote the member/object to quality assurance 2.0.<br />

Developer or administrator creates the promotion request.<br />

Developer can compile the promotion request into the work library, either as a<br />

separate task or when creating the request.<br />

Administrator moves the members/objects into quality assurance 2.0.<br />

4 Quality assurance testing release 2.0. Tester tests the change for functional consistency<br />

and accuracy.<br />

5 Promote the member/object to Production 2.0.<br />

Tester copies the original promotion request and changes the target environment (or<br />

environment group) to Production 2.0.<br />

Administrator moves the members/object into Production 2.0.<br />

Changes to Release 1.0<br />

1 Check out the member/object from Production 1.0 environment. Developer for release<br />

1.0 selects the member/object from a list of all items in release 1.0 production.<br />

2 Develop and test Release 1.0. Developer begins the programming change and tests the<br />

member/object in his development environment for release 1.0.<br />

3 Promote the member/object to quality assurance 1.0.<br />

Developer or administrator creates the promotion request.<br />

Developer can compile the promotion request into the work library, either as a<br />

separate task or when creating the request.<br />

Administrator moves the members/objects into quality assurance 1.0.<br />

4 Quality assurance testing release 1.0. Tester tests the change for functional consistency<br />

and accuracy.<br />

5 Promote the member/object to Production 1.0.<br />

Tester copies the original promotion request and changes the target environment (or<br />

environment group) to Production 1.0.<br />

Administrator moves the members/objects into Production 1.0.

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

Saved successfully!

Ooh no, something went wrong!