Referencing components

A component can be associated with a task. A task enables the consumers of the component to specify which component version to use. Typically, each version of a component is associated with a separate task.

The person who publishes the component might create a task and associate it with the appropriate files or projects. It is also possible for the component consumer to create a task and associate it with the component files he or she needs. A given component can be associated with several tasks.

The benefit of having the consumer create the task is that he or she can unit test the new version of the component, make any additional changes needed, and associate them with the same task. This keeps together all the logical changes of upgrading to the new component version, and the rest of the team is not affected by the new component version. (A given component version can be associated with multiple tasks: one for the team who developed it, and potentially one for each team that uses it.)

Rational Synergy also enables you to group tasks into folders. This means you can build folders that group sets of compatible component versions that have been certified for use together. Such a folder can be shared by different consumer applications that want to reuse those exact sets of components.


Feedback