Component development

Teams use component development to create applications from reusable parts. Developers can focus on the bigger solution they are trying to implement, rather than solving the same technical problems again and again. Additionally, teams can make products extensible by using Rational Synergy to assemble components into many different configurations that provide unique variants.

A component can be an individual file or project. Because file versions are reusable in Rational Synergy, they can be created or built in one project and used in another. For example, the ccmscci.dll library file might be built in the ccmscci project where its source code resides, but the same file can also be included as a member in both the visual_studio_integration and rhapsody_integration projects. Each project can contain a different version of the file, depending on its needs.

Rational Synergy 7.1 supports the use of component development by allowing process rules to contain a folder or folder template for component development. Rational Synergy creates automatic and component tasks to support component development. However, these tasks are typically hidden from users because they are only used during component development.

You can create and add a folder or folder template that finds automatic and component tasks for use in your component development project. See Adding a folder or folder template for component development to a process rule for steps.


Feedback