In this lesson, you will look at different common asset types and evaluate the differences between them.
You learn to recognize the various types of descriptors of an asset and identify some of the common asset types in a repository
In many repositories, users can search only by the file name or by the name of the person who created the file. In Rational® Asset Manager, there are many other elements for you to define so that other users in different parts of the organization can find the asset. The following table shows the primary searchable elements of an asset. Before you submit a new asset, consider the importance in using strong, original naming and descriptive terminology. For example, define a few tags that are related to your current work that can help other users quickly evaluate how your asset is used in its original context.
Consider the following table of the different parts of an asset. Users will be able to perform a variety of searches using keywords or filters to find assets in the repository. All of the metadata areas that are listed can be searched to help users find assets. Understanding that the following parts of an asset are searched, encourage you to provide rich data for each element as you describe your asset during the submit process.
Repository administrators create custom asset types to accommodate the variety of assets that the business units in your company need.
The following chart lists the primary asset types and the differences between them. As you get accustomed to classifying your assets, you will begin to see how each type of asset contains artifacts of different MIME types. Design or model asset types contain design documents or spread sheets, whereas implementation assets contain code or entire plug-in solutions. Use this chart for reference when you submit assets; it will help you assign the correct asset type when you describe your asset.
| Asset type | Description |
|---|---|
| Component | A component is a subset of a system. It can have related asset types, such as model, implementation, or design. |
| Design | Design assets can include design documents, strategy presentations, reports, and visual design elements |
| Implementation | Implementation assets can include code, training materials, and process guidance documents. |
| Interface | Interface assets include hardware and software descriptions, because they provide details of the relationship between them. Interface assets can also include visual designs of the interface model and supporting Meeting minute assets can be applied throughout the organization. When you classify an asset as meeting minutes, also categorize the asset within other subcategories to associate the category with the correct business unit. code. |
| (Meeting) Minutes | Meeting minute assets can be applied across the organization. When you classify an asset as meeting minutes, you should categorize this asset within other sub categories to focus the category in the proper business unit. |
| Presentation | Presentation assets typically contain items, such as presentation slides, movies, diagrams, or reports. |
| Requirement | Requirement assets can be assets that are created to explain customer requirements or requests. |
| Service | A service asset includes code, service descriptions, use cases or scenarios. They can have relationships to requirement assets |
| Strategy | Strategy assets can include charts, analytical reports, research, and financial data. |
| Test | Test assets include one stand -lone, comprehensive test that is narrowly focused on a process, project, or product. |
| Test Suite | Test suite assets include a series of tests that constitute a comprehensive series of tests, or test stack, for a process, project, or product. |
| WSDL | Web Services Definition Language (WSDL) assets include the following five types of files: .wsdl, .xsd, |
Continue with the tutorial to create a new asset in the Eclipse client and categorize the asset using the sample schemas that are provided.