IBM SC34-4499-03 manual Drivers

track of all of these changes, even when more than one user updates the same part at the same time. To make this possible, TeamConnection uses something called a work area.

A work area is a logical temporary work space that enables you to isolate your work on the parts in a release from the official versions of the parts. You can check parts out to a work area, update them, and build them without affecting the official version of the parts in the release. After you are certain that your changes work, you integrate the work area with the release (or commit the driver that the work area is a member of, if you are using the driver subprocess). The integration makes the parts from your work area the new official parts in the release.

You can do the following with work areas:

vCheck out parts from a release

vUpdate any or all of the checked-out parts

vGet the latest copies of the parts in the release, including any changes integrated by other users

vGet the latest copies of the parts in another work area

vFreeze the work area, making a snapshot of the parts as they exist at a particular instant in case you need to return to it later

vBuild the parts in the work area

vMove all parts back into the release by integrating the work area

For more information, see ªUsing work areasº on page 28.

Drivers

A driver is a collector for work areas. You create drivers associated with speci®c releases so that you can exercise greater control over which work areas are integrated into the release and commit the changes from multiple work areas simultaneously.

When a work area is added to a driver, it is called a driver member. A single work area can be a member of more than one driver. By making a work area part of a driver, you associate the parts changed in relation to that work area with the speci®ed driver.

These parts must be members of the release associated with the driver.

Drivers enable you to place the following controls over work area integrations:

vDe®ne and monitor prerequisite and corequisite work areas to ensure that mutually dependent changes are integrated in proper order.

vMonitor and resolve con¯icting changes to the same part (if you use concurrent development).

vRestrict access to driver members so that they can be changed only by users with proper authority.

Chapter 1. An introduction to TeamConnection 9