User Guide - MKS

What Is a Project Member?
What Is a Project Member?
You must manage all development objects. This lets you maintain a
complete change history as objects pass through the development cycle.
The administrator is responsible for including these pre-existing objects in
a project to establish their place in the overall development plan. New
objects are then added as your developers create them.
An object under Source Integrity control has three main components:
working file where you make your changes (always in a sandbox)
member history file where your history of changes is stored
revision number identifying (per project or variant) which version of
the object is relevant for a given point in time
In a project, a project member is a specific revision of a development object.
When you check out a project member, it is a specific revision of the object
that is copied to a working file, where you can work with it. When you
finish making changes and check the working file back into the history,
Source Integrity creates a new revision in the object’s archive.
At this point, you have the option of updating the project to use the new
revision of the object. In this way, the project stays current with the most
recent changes to its members.
The project has its own history, and so does each individual member.
17