Task: Update Asset
Modify an asset, such as its metadata or its artifacts.
Disciplines: Asset-Based Development
Purpose
To improve and refine the asset.
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    Optional:
      Outputs
        Main Description

        An asset is described with metadata and has artifacts, each of which can be modified. The nature of the modification, or update, dictates if a new asset version is required.

        It is up to the organization to establish the asset versioning policies, such as when a new asset version is required. For example, modifying a grammar issue in the metadata may be deemed by some to not require a new asset version. Whereas if the grammar issue is in one of the artifacts, then some may state that a new asset version is required.

        A general guideline to follow is to categorize asset modifications as structural and non-structural. Structural changes include modifying the following items:

        • Metadata
          • Asset version
          • Asset relationship
          • Artifact reference
        • Artifact
          • File name or path or content

        In general, these kinds of changes require a new asset version to be created. Non-structural changes are modifications to asset metadata other than those described; and do not require a new asset version.

        The organization needs to determine the tolerance level for changes before requiring a new asset version. When the new version is created then the asset review and approval activities take place.

        Steps
        Identify or Discover a Problem with an Asset

        Asset problems may be submitted as part of a change management system. Alternatively, requirements may be posted in a requirements management system, or the Asset Owner may be notified via instant messaging of a defect.

        Regardless of the source of the notification, the Asset Owner or Producer must be notified of the problem, and needs to prepare a plan to address this issue.

        Search for the Asset
        The asset with the reported issue should be located in the Repository. See Search Asset.
        Plan Asset Update Activity

        The correction or adjustment to the asset should be planned. The necessary resources to modify the asset should be estimated and secured. The expected timing of making the changes should be understood.

        An impact analysis should be conducted where current Asset Consumers are evaluated and the impact to their efforts is understood. This may require communication and planning with Asset Consumers.

        The impact analysis should also address asset relationships, including the related assets' Asset Owners or Producers, as well as other technical dependencies. The Asset Owners or Producers of related assets may need to participate in the planning depending on the nature of the problem and the nature of the asset relationship.

        The review process for the asset may need to be revised to include other reviewers and subject matter experts.

        Update the Asset

        To update the asset a developer will follow steps similar to the ones outlined below:

        1. Search for the asset in the Repository.
        2. Retrieve the asset: identify the SCM location from which to check out the asset artifacts.
        3. Modify the asset artifacts and metadata: the Asset Owner/Producer may need to conduct merges from previous changes to the artifacts made by others but which have not yet been incorporated into the published asset in the Repository.
        4. Submit the modified asset: make changes to metadata, supporting documents, and identify the SCM label or tag that should be applied to this asset version. The asset should now be ready for the review and test process.
        More Information