This table illustrates how the Rational Asset Manager repository integrates with source control management systems.
| Software Control Management (Team Concert, ClearCase, UCM, CVS) | Rational Asset Manager repository | |
|---|---|---|
| Primary roles | Developers | Business analysts, developers, architects, managers |
| Content level | Files | Assets – an asset can contain multiple related artifacts (files) and associated metadata |
| Change rate | Frequent; work in progress | Rare; hardened reusable components |
| Collaboration | For artifact creation and parallel development | For review and reuse of assets through discussion forums, emails, notification, RSS feeds |
| Taxonomy | N/A | Asset types and relationships; customers can add additional classification |
| Search | File based | Metadata based search, custom metadata attributes |
| Metrics | N/A | Track asset usage, feedback, and popularity |
| Review and approval | Change management | Review boards, customizable review process |
| Asset types, relationships and impact analysis | None | Recognize asset types and relationships. Help with end-to-end traceability including production deployment |
| Versioning | Done at source files level | Done at asset level; an asset can contain multiple files |
| Client access | Eclipse | Eclipse and Web |
Code that has been published as an asset can be easily found and reused, thereby saving development time. The following example illustrates a scenario where an asset is defined, developed, built, reviewed, approved, and reused.
By reusing the code that Developer A has already written, Developer B saves time. By using the command-line API in Rational Asset Manager to build the logging Java archive file from the source asset, Developer B ensures that he will always be using the most recent version of the asset from Developer A.