This section describes the Rational Synergy default
workflow.
Read these topics to understand the default workflow.
Use of tasks
A task represents a problem in or enhancement to your software
application. Because a task categorizes all of the objects you are
modifying for a specific problem or enhancement, you need to complete
only the task that categorizes those objects. You do not need to check
in the objects individually. Tasks do much of the work for users.
Development process
Development projects are like containers. They can be reused
from release to release. The contents of the projects change each
time the developers perform an update.
Integration test cycle
The goal of the integration test cycle is to find problems
as early in the development cycle as possible.
System test cycle
After the development team makes significant progress towards
a stable build or a milestone, the build manager typically builds
a software installation for the Quality Assurance (QA) team to use
for system testing. The goal of system testing is to prepare the software
application for a milestone, such as a release.
Releasing the system test baseline
After the software ships, the build manager must immediately transition
the system test baseline used to build the software to the released state.
Doing so creates a starting point for future releases.
Preparing for the next release
After the build manager releases a project, it can be used
as a baseline for the next release.
Summary
This section covered the entire development cycle, from
developers completing tasks in their development projects, through
the build managers gathering and testing of tasks, to the final project
release and the establishment of a baseline for the next release.