The Source Integrity Professional Edition User Guide - MKS

Once a Source Integrity
project has been created, you
have the option of creating an
associated sandbox. This
sandbox includes a directory
tree that mirrors the structure
of the master project.
Sandboxes
When the second developer completes and tests changes, they
too are checked into the master project. The buildmaster can
make a new sandbox, and do a final build incorporating both sets
of changes. The fix can then be shipped to the customer.
When you execute a Source Integrity command in a sandbox, the
action is redirected to the master project. Source Integrity can
perform almost the entire range of project commands in the sandbox,
as if it were in the master project. For example, if you check out a
sandbox member, Source Integrity physically checks out the member
from the master project, but copies the working file to the sandbox
directory.
In this way, you are assured of working with current data from the
master project, with the knowledge that your work will not interfere
with other users (or vice versa). This streamlines product
maintenance, saving time, saving money, reducing delays to ongoing
development, and increasing customer satisfaction.
Within your sandbox, you can see if new updates are available in the
master project. It is up to you to decide when and if you will pick up
these changes in your sandbox. Thus, you are protected from a “freefire
zone”, but still have the ability to coordinate with other users’
work when it is convenient for you.
User Guide 23