MKS Implementer 2006 Administration Guide

Chapter 2: Understanding Implementer
14
ProjectMaster projects (requires using ProjectMaster for project management)
You create Implementer projects in Implementer. If using DesignTracker, you can create
projects from the Work with Entity List Members panel by using F20=Create IM Project
(creates one project or group of projects for each design request). Implementer projects allow
for project paths (similar to environment paths) that control the development flow of
members/objects associated with a project. The project path can be defined on a project-byproject
basis. For details, see “Project-based Application Paths” on page 142.
When DesignTracker is not used, for example, when using MKS Integrity, you must
determine a method of naming your projects and determine when to create them. For
example, you might create a project for every fix or minor change needed, or create a single
project for fixes this month or this year, or a continuous project for all fixes. You may already
have a system in place for logging user requests that match Implementer project references.
Archiving serves two main purposes: The main purpose is to recover original source and/or
objects when the promoted source and/or objects do not function appropriately in
production. Secondly, it provides access to the initial source of a specific program to review
before promoting the current changes.
You should determine the value of being able to rollback a change, and the ability to view
historical versions of source. MKS recommends you archive production environments but
not archiving test environments.
If you have remote systems, you can archive on the remote system or the local system.
However, archiving on the remote allows you to rollback more quickly because it does not
require redistributing the objects to the remote system.
Scenario Summaries
The following tables list each scenario with a description of the important characteristics of
each scenario. This information is helpful to understand why a specific scenario might be
useful. The detailed description for each scenario includes:
illustration of the development cycle
brief scenario description
description of development steps
setup tasks for the scenario