These major repository scenarios are performed by the asset-based development roles as they work with the Repository.
See the Role Overview.
Configuring the repository
Roles: Repository Administrator, Community Administrator, Integration Administrator
Description: Configure the repository for practitioners, administrators, and managers to use.
Pain points:
-
Difficult to visualize or see the big picture for configuring the repository
-
Difficult to share overall picture with others for buy in and approval
-
Difficult to modify repository after initial configuration and roll out changes
Search or evaluate an asset
Roles: Asset Consumer
Description: Assets are searched using keywords, classification values, asset relationships, tags, and so forth. Upon
discovery, the assets are evaluated for their applicability to the Asset Consumer's context and needs.
Pain points:
-
The effort is high to find assets that are meaningful to the problem that needs to be solved, this is often
exacerbated by inconsistent metadata.
-
It is difficult to evaluate assets in terms of their technical, legal, and quality aspects; this is often due to
inconsistent asset organization and packaging.
Retrieve and use an asset
Roles: Asset Consumer
Description: The asset is retrieved into the Asset Consumer's context and used. The asset may be extended using the
asset's variability points.
Pain points:
-
The Asset Consumer often does not know how or where to get started using an asset
-
It is difficult to know where within the Asset Consumer's workspace, the asset metadata and artifacts have been
placed
-
It is difficult for Managers to determine who is using the asset and where it is being used
-
There is an inability to plan or implement a fix or feature
-
There is lack of communication with existing Asset Consumers when an asset has been modified
-
It is difficult for Asset Consumers to get support using the asset
Create and package an asset
Roles: Asset Owner, Asset Producer
Description: An asset specification has been created and the asset is created. This includes creating and harvesting
artifacts. The supporting asset material for the Asset Consumer is prepared and the asset metadata is captured.
Pain points:
-
It is difficult to capture and describe the expected context within which the asset should be reused
-
There is inconsistent organization for assets
-
It is labor-intensive to package assets
-
Supporting material for Asset Consumers is often disregarded by Asset Owners and Asset Producers
Submit asset
Roles: Asset Owner, Asset Producer
Description: The asset is created and is now submitted into the Repository. The metadata and classification of the
asset is refined as the asset is submitted to the Repository.
Pain points:
-
Assets may be stored manually, without Repository support
-
Interested parties are not aware of new assets in the Repository
Review and approve asset
Roles: Asset Reviewer, Review Board
Description: The Review Board prepares the review, the reviewers are notified, the asset is reviewed and the votes are
cast.
Pain points:
-
Asset Consumers need verified content, which promotes trust in the reuse cycle
-
There is often lack of awareness of where the asset is in the workflow
Modify and create new asset version
Roles: Asset Owner, Asset Producer
Description: A problem or new feature for the asset is identified. The modification is planned. The asset is modified
and submitted to review and approval.
Pain points:
-
It is difficult to track multiple versions of an asset
-
The workflow to update an asset is not clearly understood
Measure asset activity
Roles: Asset Owner, Asset Producer, Community Administrator, Repository Administrator, Project Manager, Team Lead,
Sponsor
Description: The activity level of an asset and the repository is monitored. The Repository may produce these reports,
or may integrate with project management or portfolio management tools.
Pain points:
-
It is difficult to understand the business benefits of the asset program
-
Need to understand where future asset investment should be directed
-
Need to know where and how to prune the repository
|