Organizations use repository usage models to structure and maintain work processes. How organizations adopt and use these models depends on the level of formality and granularity that an organization wants in workflow and process refinement, the maturity of an organization, the people and departments involved, and how funding is allocated. The following examples illustrate the models that you can use with Rational Asset Manager.
In the knowledge management model, users work with IBM Rational Method Composer and Rational Asset Manager to organize best practices and processes and associate assets to complete process flow. Some organizations supplement the assets from this usage model to embed training videos in Rational Asset Manager asset descriptions, further integrating the process definitions with the asset references.
In the business intelligence model, users work with external modeling and reporting tools to report asset activity, trends, and financial impact.
In the service-oriented architecture (SOA) services model, users govern service development, builds, and publishing activities from Rational Asset Manager to a service registry. Users classify assets with SOA-based category schemas so that service assets align with business needs and can be classified with similar services. In addition, users can use the SOA services model to make build-time assets be approved definitive library assets and to align build-time assets with runtime service interfaces.
In the broker model, users govern assets in and across related communities. For example, one community contains assets that define the specifications of a large project, while a related community manages the solution development, and a third community implements the specifications and submits a solution. To reduce the impact of outsourcing, organizations can use the broker model with software development teams and distributed teams.
In the asset planning model, users plan the updates for and creation of assets that align with specific line item-driven requirements. Users create assets that contain entire products, solutions, or features. Users classify assets with a timeline and associate assets with the requirements that are defined in a requirements management tool. An important part of the asset planning model is the review and approval processes that the schedule controls.
In the impact analysis and traceability model, users rely on asset relationships to analyze the impact of the assets over time. For example, an asset relationship might be the relationship between development assets and the infrastructure assets that they depend on. When users understand the impact of a change to an asset, such as the creation of a version or the retirement of an asset, they might better analyze business trends and the effects of changes on company resources.
In the reuse with change management model, users work with IBM Rational ClearCase®, IBM Rational ClearQuest®, IBM Rational Team Concert, or other SCM systems to reuse existing artifacts to build and share new assets.