MKS Implementer 2006 Administration Guide

Chapter 2: Understanding Implementer
24
developer must have emergency capabilities. The developer completing the emergency
development resolves the conflict and promotes the request back into production. The next
programmer and/or administrator completes the same actions.
To focus on the emergency features, this scenario includes only one quality assurance
environment.
Development Tasks
This is the typical task sequence from the start of a programming change to completion.
1 Check out the first version of a member. Developer checks out to a personal library,
project library, or shared development library.
2 Develop and test. Developer begins a programming change.
3 Check out second version for an emergency. Developer checks out a second copy for an
emergency change to a different environment. This is often an emergency check out. You
must also select a specific version of the member to start with. For emergency
development, this is probably the original production member/object. This is normally
considered concurrent development that requires specific authority, however, in this
case the emergency check out rights override the concurrent development requirement.
4 Make the emergency change. Developer codes, compiles, and tests.
5 Resolve the conflict for emergency version. This resolves all conflicts of the emergency
version of the member. Promoting a request often includes conflict resolution as
described in the next task. Usually, the user who has emergency capabilities to resolve
conflicts and complete moves has this authority.
6 Promote the emergency version to production. Developer creates the promotion request.
You normally promote this request directly into production using the Auto Submit
Through Step in the move function.
7 Complete the first change. Developer codes, compiles, and tests.
8 Resolve the conflict for first change.
Developer notifies the administrator that conflict resolution is necessary.
Administrator resolves all conflicts of the first completed version of the member.
Promoting a request often includes conflict resolution as described in the next task.
This step could include reviewing the source code of the emergency version, or even
performing a merge or compare of the version.
9 Promote the first version to production.
Developer creates the promotion request.
Developer can compile the promotion request into the work library, either as a
separate task or when creating the request.
Administrator moves the members/objects into production.