In this task the asset artifacts are created and/or harvested. The asset is created according to the Asset
Specification. Packaging the asset includes preparing documentation and supporting material to provide easy
comprehension of the asset. The asset's metadata, such as name, description, and anticipated context is prepared.
Finally the asset is submitted to the Repository.
Major considerations in creating assets:
-
Understand the recurring problem and proposed solution; the Asset Specification addresses this.
-
Understand and develop for the intended Asset Consumer, including the following:
-
-
Identifying how it is expected the Asset Consumer will discover the asset (this affects both classification
of the asset as well as the packaging material that is prepared).
-
The anticipated context(s) the Asset Consumer will be in (such as a development context, or a runtime
context, or a business context), as well as the skill set of the Asset Consumer.
-
Understand who will fund, maintain and support the asset
-
Understand the asset versioning strategy
The Asset Specification will identify a possible asset type. Each asset is of a single type, and can be classified
multiple times. For example, you can take an asset such as a stock quote service. You can determine the asset
type is Service, and you may classify the stock quote service as a "non-commercial" service, and as a "domestic"
service, providing quotes for only domestic traded stocks.
Looking at several of the steps of creating assets, they have direct impact on the consumability of the asset, for
instance:
-
Creating or harvesting artifacts: impacts the usability of the asset
-
Packaging the asset: impacts the comprehension of the asset
-
Categorizing the asset: impacts the searching and discoverability of the asset
This point cannot be emphasized enough. The steps of creating an asset should be focused on the Asset Consumer, for
both their ease of use and for the downstream maintenance.
|