MKS Implementer 2006 Administration Guide

A PPENDIX D
Glossary
Definitions of Common Implementer Terms
D
This appendix provides a description of the many terms used in software change
management and throughout Implementer. Review this appendix to learn these terms
and definitions, and understand how they relate to Implementer.
NOTE For a description of MKS Integrity terms, see the MKS Integrity Server
2006 Administration Guide. For a description of MKS Source terms, see the
MKS Source 2006 User Guide.
action An action is used to indicate the process to perform to a member/object. The
action is specified when checking out a member/object and when creating a request for a
member/object. The following actions are valid for checking out and creating a
promotion request:
1 = Change
2 = Create
3 = Delete
8 = Regen (only valid for AllFusion 2E model objects)
9 = Recompile
administrator The administrator sets up and configures Implementer. The
administrator defines users, environments, environment capabilities. The administrator
also defines the MKS Integrity parameters required in Implementer for integration.
application path An application path refers to the standard and emergency paths set up
in Work with Projects and Work with Environments. Application paths are used in the
development cycle to define the flow of member/objects between environments. They
are also used to determine the location of source and related objects for an object, for
example, when compiling with a check out or create request action of recompile.
The two basic types of application paths are:
Project path
This term refers to the standard and emergency paths set up in Work with Projects.
A path can be defined for each project to represent the development flow of
member/objects associated with the project. This type of path is beneficial when
457