Tasks and objects

A task represents a logical change that needs to be made in your software application. A task groups all the software modifications that need to be made to complete the change. It includes a description of the change and the name of the person responsible for completing it.

An object is a collection of data, such as a file or directory. Examples of objects are source files, makefiles, test results, directories, and documents. For tracking purposes, every revision of an object is referred to as an object version. Each object version has a set of properties (for example, name, owner, create time) to further define it.

For example, a user reports a bug in your GUI of your application. The GUI group leader assigns the bug to a developer named Jane. Jane is assigned a task called Fix scrolling in Snap dialog box. Each time Jane uses Rational Synergy to check out an object that fixes the scrolling problem in the Snap dialog box, the object becomes associated with the task.

For an illustration of these concepts, see the figure .

The task and objects have a relationship. Objects that are grouped by a task are said to be associated with the task. All objects required to fix a specific problem stay together in a logical grouping, described by the task name. The object versions on the right side of the figure are associated with the task Fix scrolling in Snap dialog box. They contain the code changes necessary to complete this task. The number at the top of each object represents the version of the object.

The task name, in this case, Fix scrolling in Snap dialog box, is referred to as its synopsis. Additionally, when you create a task, Rational Synergy assigns it a number. Besides the number and synopsis, a task contains other information about the change, for example, the name of the resolver. When a task is assigned to a developer, the resolver is automatically set to the name of the developer. You can also set the following properties when you create a task:


Feedback