Each developer working on a project has a working version of the project. Developers copy their development projects from the integration testing projects of the build manager.
Normally, a developer does not check in development projects. If a developer makes and tests a change in his development project, Rational Synergy automatically checks in the individual object versions that implement the change when he checks in the task; the developer does not check in the project itself. Development projects are like containers—they can be reused from release to release. The projects’ contents change each time the developer updates.
When a developer starts work on a new task or is ready to update his project to bring in the most recent changes, he updates it. He keeps a project current by updating it when needed, and he uses the same version of a development project for every change to its member objects.
Each developer is responsible for using his development project to unit test his changes. The developer should update his project, then re-test his changes before checking in the task, to verify that his changes are compatible with other developers’ latest changes. After unit testing is complete, the developer should complete the task, thereby checking in all interdependent objects simultaneously. This ensures that all necessary objects are available to the build manager for integration testing.
By default, when a developer updates his development projects, Rational Synergy collects all of his own assigned and completed tasks for the current release, plus the latest tasks that have passed integration testing for that release.